GitHub MCP RegistryListed
Search Fragments
The gate before your agent answers: a verdict on whether a half-remembered thing can be reached.
First seen 14 Oct 2026. Evidence as of 13 Nov 2026.
3
Tools
From an anonymous probe
1
Source listings
Each with its own history
13
Recorded changes
Since first seen
Tools
| Tool | Description | Behaviour |
|---|---|---|
| resolve_fragment | Returns a verdict first, so your agent knows whether to answer, keep looking or say it can't place it: ORIGIN_OF_TRUTH (found, evidence checked, with sources), PARTIAL_ORIGIN (leads to follow, not an answer) or NOT_REACHABLE (SF's search reached nothing; not a claim the thing can't be found). Pieces 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, even uncertain ones. It searches many sources and fits them together. A shortlist or an honest "can't place it" is still useful. Use it when your own search couldn't place it. Not for known titles, trivia, recommendations or checking claims (use verify_claim). When the user says whether this helped, report it with submit_resolution_feedback. | Changes data |
| submit_resolution_feedback | After 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 shortlist or leads, send picked_rank (1 = first item) or picked_url; if nothing fitted, send none_fitted: true. corrected_target and new_clue are optional and are stored as feedback only; they never change graph facts. | Changes data |
| verify_claim | Checks 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 directly confirm the specific claimed detail - "partially_supported" — sources confirm the entity and domain; specific detail is pointed to but not directly stated - "insufficient_evidence" — sources don't address the specific claim; fires freely, including when the entity is well-known but the specific detail is undocumented - "unsupported" — a credible source explicitly contradicts the claim All verdicts are DECIDE-BY-EYE. A "supported" verdict means current web sources confirm it — not that it is true. Evidence may be incomplete, biased, or outdated. The stated_limits field is always present and identifies what the evidence cannot confirm. Good input shape (specific, checkable assertions): - "Werner Herzog dragged a full-size steamship over a hill during the filming of Fitzcarraldo" - "Glenn Gould stopped giving live concerts in 1964" - "The Backrooms photograph originated on 4chan" Checks one specific factual statement. Not for identifying half-remembered works. Not this shape: - "there's a documentary about a filmmaker dragging a boat over a mountain" - "a musician famous for stopping performing" | Changes data |
Change history
- Description changed (GitHub registry)
- resolve_fragment: input schema changed
- resolve_fragment: description changed (+"Returns a verdict first, so your agent knows whether to answer, keep looking or say it can't place it: ORIGIN_OF_TRUTH (found, evidence checked, with sources), PARTIAL_ORIGIN (leads to follow, not an answer) or NOT_REACHABLE (SF's search reached nothing; not a claim the thing can't be found).")
- server instructions changed (+"Search Fragments is the gate before your agent answers. resolve_fragment:" +"something (a" +"book,")
- resolve_fragment: input schema changed
- verify_claim: input schema changed
- verify_claim: description changed (+"—" +"—" +"—")
- resolve_fragment: input schema changed
- server instructions changed (+"—" +"—" +"—")
- submit_resolution_feedback: input schema changed (+none_fitted, +picked_rank, +picked_url)
- submit_resolution_feedback: description changed (+"After the user reacts to" +"result, call" +"with its resolution_id. accepted: it")
- resolve_fragment: description changed (+"When the user says whether this helped, report it with submit_resolution_feedback.")
- Listed (GitHub registry)
| Source | Listing | First seen | Last seen | Versions |
|---|---|---|---|---|
| GitHub MCP Registry | com.searchfragments/search-fragments | 14 Oct 2026 | 13 Nov 2026 | 2 |