Koskamo

CorpusFetch MCP

An MCP server providing O(1) symptom routing and warrant-first fetch capabilities over 622 concluded records. It enables agents to look up exceptions or symptoms, fetch precondition warrants, and retrieve record bodies in Markdown or Python formats for contract and instance analysis.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

CorpusFetch MCP logo, by CorpusFetchVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-01Operated by CorpusFetch
MCP endpoint (Streamable HTTP)
https://mcp.corpusfetch.com/mcp
Vendor documentation

What you can do with it

  • Lookup candidate addresses for specific exception classes
  • Lookup candidate addresses for specific runtime symptoms
  • Fetch warrant preconditions for record access
  • Retrieve concluded record bodies in Markdown or Python

Source and maintenance

Vendor evidenceRegistry 0.1.0
mcp-registry: com.corpusfetch/corpusfetch@0.1.0Project website

Protocol and capabilities

Server
corpusfetch-mcp 0.1.0
MCP protocol
2025-06-18
Tools
4 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {}
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

CorpusFetch MCP server. Use lookup tools to resolve a symptom or exception to candidate record addresses, then fetch the warrant before the record.

Tools

4 advertised

corpusfetch_fetch_record
Advertised by the server during the last successful anonymous check.

Fetch the body of a CorpusFetch record. Format 'md' (default, ~1500 tokens) or 'py' (zero-prose stdlib slice, ~300 tokens). Prefer warrant-first: call corpusfetch_fetch_warrant before this.

corpusfetch_fetch_record input schema
{
  "type": "object",
  "title": "FetchRecordParams",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Slug of the record"
    },
    "format": {
      "type": [
        "string",
        "null"
      ],
      "default": null,
      "description": "Format: \"md\" (default, ~1500 tokens) or \"py\" (~300 tokens)"
    }
  }
}
corpusfetch_fetch_warrant
Advertised by the server during the last successful anonymous check.

Fetch the ~220-token warrant (precondition seal) for a CorpusFetch record. Fetch this before the .md record. If the seal fails, do not fetch the record.

corpusfetch_fetch_warrant input schema
{
  "type": "object",
  "title": "FetchWarrantParams",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Slug of the record (the URL path segment after /c/ and before .md)"
    }
  }
}
corpusfetch_lookup_exception
Advertised by the server during the last successful anonymous check.

Route a Python exception class to candidate record addresses in the CorpusFetch pillar. Returns warrant_url, py_url, md_url, and fetch_when for each candidate. Fetch the warrant first (~220 tokens); if its seal fails, do not fetch the .md.

corpusfetch_lookup_exception input schema
{
  "type": "object",
  "title": "LookupExceptionParams",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "exception_class"
  ],
  "properties": {
    "exception_class": {
      "type": "string",
      "description": "Python exception class, e.g. KeyError, TimeoutError, ValueError"
    }
  }
}
corpusfetch_lookup_symptom
Advertised by the server during the last successful anonymous check.

Route a runtime symptom to candidate record addresses in the CorpusFetch pillar. Returns warrant_url, py_url, md_url, and fetch_when for each candidate. Fetch the warrant first (~220 tokens); if its seal fails, do not fetch the .md.

corpusfetch_lookup_symptom input schema
{
  "type": "object",
  "title": "LookupSymptomParams",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "symptom"
  ],
  "properties": {
    "symptom": {
      "type": "string",
      "description": "Runtime symptom key, e.g. UNICODE_HOMOGLYPH_OR_MOJIBAKE, or a DOMAIN_* key"
    }
  }
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
288 ms
95th percentile latency
288 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 288 ms · metadata changed · 4 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http corpusfetch-mcp https://mcp.corpusfetch.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add corpusfetch-mcp --url https://mcp.corpusfetch.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable corpusfetch-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "corpusfetch-mcp": {
      "url": "https://mcp.corpusfetch.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "corpusfetch-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.corpusfetch.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start corpusfetch-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "corpusfetch-mcp": {
      "type": "http",
      "url": "https://mcp.corpusfetch.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http corpusfetch-mcp https://mcp.corpusfetch.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "corpusfetch-mcp": {
      "url": "https://mcp.corpusfetch.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "corpusfetch-mcp": {
      "serverUrl": "https://mcp.corpusfetch.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like CorpusFetch MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 1,026

Do you run CorpusFetch MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing