O(1) routing, semantic search, and quality-filtered demand-driven experiences over 800+ records.
Connect Remote server
claude mcp add --transport http corpusfetch https://mcp.corpusfetch.com/mcp
{
"mcpServers": {
"corpusfetch": {
"url": "https://mcp.corpusfetch.com/mcp"
}
}
}
{
"servers": {
"corpusfetch": {
"type": "http",
"url": "https://mcp.corpusfetch.com/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://mcp.corpusfetch.com/mcp
Tools 6 found in our last check
corpusfetch_fetch_recordFetch the full resolved experience record. Format `md` (~1,500 tokens, includes reasoning) or `py` (~300 tokens, zero-prose executable invariants).
corpusfetch_fetch_warrantFetch the compact ~220-token precondition seal for a resolved record. Always call this before `corpusfetch_fetch_record`—check the seal first; if it fails, the record does not apply to your current state.
corpusfetch_lookup_exceptionLook up operational experience for an exact Python exception class (e.g., KeyError, TimeoutError, ConnectionError). Use when you encounter an unexpected runtime error and need an empirically verified boundary decision rather than a guess. Prefer `corpusfetch_search` when you hav…
corpusfetch_lookup_symptomLook up operational experience for a specific runtime symptom or boundary failure (e.g., UNICODE_HOMOGLYPH_OR_MOJIBAKE). Use when facing an ambiguous failure state or unbounded reasoning loop. Prefer `corpusfetch_search` if you only have a loose description.
corpusfetch_request_experienceRequest a new operational experience when `corpusfetch_search` returns no match. The corpus will generate and publish a record for your specific error or symptom within minutes. Use this instead of guessing when the problem is novel and no existing record applies.
corpusfetch_searchSearch operational records for distributed systems failures, AI agent protocol issues, MCP/A2A problems, database anomalies, concurrency bugs, and runtime errors. Use when the user's problem involves infrastructure, agent-to-agent coordination, authentication, memory management,…
Details
| Endpoint | https://mcp.corpusfetch.com/mcp (Streamable HTTP) |
| First published | 11 Nov 2026 |
| Last updated | 11 Nov 2026 |
| Registry name | com.corpusfetch/corpusfetch |
More search and web servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
