
Search Fragments MCP server
Which MCP servers are Search Fragments's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-25
- Registry namecom.searchfragments/search-fragmentsverified in the MCP registry
The registry name sits under searchfragments.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-25
- Tools3
- Server calls itselfsearch-fragments-mcp
- Server version0.2.6
- Protocol version2025-11-25
On 2026-10-25 the server answered initialize and tools/list without a sign-in. First answer in 255 ms.
- Its tools do every use case we checked: resolve half-remembered film, song, or book queries; decline unresolvable queries instead of fabricating answers.
Once connected
- For "resolve half-remembered film, song, or book queries", the likely first call is resolve_fragment.
- For "decline unresolvable queries instead of fabricating answers", the likely first call is resolve_fragment.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP score90 of 100answers 100 · does the job 100 · definitions 100 · context 100 · use 0 · connects 100
- What an agent can do with it2 of 2 use cases
- Answered100% of days11 of 11 daily checks
- Median first answer282 ms
- Space in an agent's context≈ 1,105 tokensthe definitions of all its tools (3), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results3 of 3 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
What an agent can do with it
- can do · resolve half-remembered film, song, or book queries
- not sure · return ranked shortlists of sources to confirm by eye
- can do · decline unresolvable queries instead of fabricating answers
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
resolve_fragmentPieces together the name of a film, TV or radio show, song, book, game, quote, person, place, event or research study from the fragments a user remembers: a scene, a line, a face, roughly when. Pass every fragment in the user's own words…
submit_resolution_feedbackAfter the user reacts to a resolve_fragment result, call this with its resolution_id. accepted: it is what they meant. partial: it helped but is not quite it. rejected: it is not what they meant. If they recognised an item in the…
verify_claimChecks whether current web sources support a specific factual assertion. Takes a claim as a natural-language statement; returns a verdict with cited evidence and stated limits. Verdict set: - "supported" — multiple independent sources…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"search-fragments": {
"type": "http",
"url": "https://searchfragments.com/api/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http searchfragments https://searchfragments.com/api/mcpclaude.ai, ChatGPT and other clients: add https://searchfragments.com/api/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.