CorpusFetch
com.corpusfetch/corpusfetchVersion 1.0.7O(1) routing, semantic search, and quality-filtered demand-driven experiences over 800+ records.
Status
Responds456 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 13:52 UTC
- Latency
- 456 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://mcp.corpusfetch.com/mcpResponds456 msNo sign-in
Claude Code
claude mcp add --transport http corpusfetch https://mcp.corpusfetch.com/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: corpusfetch
Remote MCP server URL: https://mcp.corpusfetch.com/mcpCursor
{
"mcpServers": {
"corpusfetch": {
"url": "https://mcp.corpusfetch.com/mcp"
}
}
}VS Code
code --add-mcp '{"name":"corpusfetch","type":"http","url":"https://mcp.corpusfetch.com/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
6 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
corpusfetch_fetch_recordFetch the full resolved experience record. Format `md` (~1,500 tokens, includes reasoning) or `py` (~300 tokens, zero-prose executable invariants). | Not declared | Not declared | Not declared | Not declared |
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. | Not declared | Not declared | Not declared | Not declared |
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 have a symptom description but not an exact exception name. | Not declared | Not declared | Not declared | Not declared |
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. | Not declared | Not declared | Not declared | Not declared |
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. | Not declared | Not declared | Not declared | Not declared |
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, or observability. Do not use for general programming questions—only for boundary decisions and failure modes that have been empirically recorded. | Not declared | Not declared | Not declared | Not declared |
Details
- Registry status
- Active
- Published
- Nov 11, 2026
- Updated
- Nov 11, 2026
- Repository
- Not given
- Categories (suggested)
- Search and webSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared