Home / MCP registry index / io.github.wulfkaal/corpus

Kaal Corpus: Verifiable Claim Layer

io.github.wulfkaal/corpus in the official MCP registry. Endpoint https://corpus.openstanding.org/mcp. Source: github.com/wulfkaal/wulfkaal.github.io.

The registry describes it as: Cite the claim, not the paper: 5,033 assertions, each hash-verifiable against its source PDF

We read its 18 tools on 2026-10-30. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http corpus https://corpus.openstanding.org/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "corpus": {
      "url": "https://corpus.openstanding.org/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"corpus","type":"http","url":"https://corpus.openstanding.org/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

search_papers get_paper papers_by_year corpus_overview search_posts verify_document how_to_cite search_claims get_claim claims_on_topic search_positions get_position positions_on_topic claim_layer_overview search_research_claims get_research_claim list_research_observations get_research_observation

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-wulfkaal-corpus/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-wulfkaal-corpus)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Documents and PDF MCP servers