Skip to content

CorpusFetch MCP server

com.corpusfetch/corpusfetchcorpusfetch.comstreamable-httpv1.0.7Scanned

O(1) routing, semantic search, and quality-filtered demand-driven experiences over 800+ records.

6 tools: 1 change things and 5 only read.

Tools: 0 delete, 0 irreversible, 1 write, 5 read.
  • Reads private data · 1
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the CorpusFetch MCP server can do

The CorpusFetch MCP server is published by corpusfetch.com, a domain the MCP Registry verified. It has 6 tools. It can create or change data (1 tool: corpusfetch_request_experience), but cannot delete data. 5 tools only read.

1 tool reads private data (corpusfetch_search); 1 tool brings in text other people can write (corpusfetch_search).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 4 times since Anlyon Radar first saw them.

Last scanned Nov 11, 2026, version 1.0.7.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 1Claude Code: ask
  • corpusfetch_request_experienceRequest a new operational experience when `corpusfetch_search` returns no match.No findings

    Why it is in this group

    • The name "corpusfetch_request_experience" says "request": a word for a change.
    Description, as the server wrote it
    Request 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.
Only reads 5Show 5 read-only tools
  • corpusfetch_fetch_recordFetch the full resolved experience record.No findings

    Why it is in this group

    • The name "corpusfetch_fetch_record" says "fetch": a word for reading.
    Description, as the server wrote it
    Fetch 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.No findings

    Why it is in this group

    • The name "corpusfetch_fetch_warrant" says "fetch": a word for reading.
    Description, as the server wrote it
    Fetch 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).No findings

    Why it is in this group

    • The name "corpusfetch_lookup_exception" says "lookup": a word for reading.
    Description, as the server wrote it
    Look 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.
  • corpusfetch_lookup_symptomLook up operational experience for a specific runtime symptom or boundary failure (e.g., UNICODE_HOMOGLYPH_OR_MOJIBAKE).No findings

    Why it is in this group

    • The name "corpusfetch_lookup_symptom" says "lookup": a word for reading.
    Description, as the server wrote it
    Look 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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 16, 2026, 14:21 UTC, unchanged since Nov 9, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.corpusfetch.com/.well-known/oauth-protected-resource/mcp
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.corpusfetch.com/mcp: tools/list returned 6 tools to an anonymous client, including corpusfetch_request_experience (write)

    What this check looks for

Posture changes

  1. Nov 9, 2026
    • Tools that change things, listed without credentials: 0 to 1

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools6 changed.~6 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 0 -> 1.View diff
    • Tools that change things, listed without credentials: 0 to 1
  3. Tools1 added.+1 addedView diff
  4. Tools1 added.+1 addedView diff
  5. Tools4 changed.~4 changedView diff

Install

Pinned to version 1.0.7. Values in angle brackets are yours to fill in.

claude mcp add --transport http corpusfetch https://mcp.corpusfetch.com/mcp
claude mcp add --transport http corpusfetch https://mcp.corpusfetch.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__corpusfetch__corpusfetch_fetch_record",
      "mcp__corpusfetch__corpusfetch_fetch_warrant",
      "mcp__corpusfetch__corpusfetch_lookup_exception",
      "mcp__corpusfetch__corpusfetch_lookup_symptom",
      "mcp__corpusfetch__corpusfetch_search"
    ],
    "ask": [
      "mcp__corpusfetch__corpusfetch_request_experience"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as corpusfetch. Review it before you use it.

Capability tags behind 1 rule
  • mcp__corpusfetch__corpusfetch_search private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.corpusfetch/corpusfetch/verify?hash=3aa00bc999270f587c76eb7ddcc42eb2b56833ff399919650e1b5d480a098c35" | jq -e '.changed == false'

Pinned hash 3aa00bc99927, from Nov 11, 2026, 15:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.corpusfetch/corpusfetch/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.corpusfetch/corpusfetch
[![Anlyon Radar](https://radar.anlyon.com/badge/com.corpusfetch/corpusfetch.svg)](https://radar.anlyon.com/servers/com.corpusfetch/corpusfetch)

Source: MCP Registry. Synced Nov 11, 2026, 15:17 UTC.

CorpusFetch MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the CorpusFetch MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the CorpusFetch MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the CorpusFetch MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the CorpusFetch MCP server have?

6 tools: 1 write, 5 read. corpusfetch_request_experience, corpusfetch_fetch_record, corpusfetch_fetch_warrant, corpusfetch_lookup_exception, corpusfetch_lookup_symptom and corpusfetch_search.

Does the CorpusFetch MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the CorpusFetch MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the CorpusFetch MCP server changed its tools?

Yes, 4 times since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.