mcp-registry/com.searchfragments/search-fragments · v0.2.6
As of 2026-10-24 13:31 UTC, the Searchfragments Search Fragments MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 4 minutes.
For queries a model can't confidently place: resolves or declines. Built to decline, not guess.
Claude Code
claude mcp add --transport http searchfragments-search-fragments-mcp-ser https://searchfragments.com/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"searchfragments-search-fragments-mcp-ser": {
"type": "http",
"url": "https://searchfragments.com/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
In the last 30 days: 0 tool(s) removed and 2 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.searchfragments/search-fragments"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.searchfragments/search-fragments"}) over MCP.
submit_resolution_feedback ~462 tokensresolve_fragment ~252 tokensverify_claim ~244 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.searchfragments%2Fsearch-fragments?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.searchfragments%2Fsearch-fragments?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.searchfragments%2Fsearch-fragments.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.searchfragments%2Fsearch-fragments.svg :target: https://glimind.com/server/mcp-registry%2Fcom.searchfragments%2Fsearch-fragments?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:8a67731b878f330c…, first seen 2026-10-20, included at leaf 31945 of 59,044. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable other servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-24 13:31 UTC, the Searchfragments Search Fragments MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 4 minutes.
Searchfragments Search Fragments MCP server advertises 3 tools, including resolve_fragment, submit_resolution_feedback, verify_claim.
Point your MCP client at this streamable-http endpoint: https://searchfragments.com/api/mcp
Glimind scanned all 3 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.