mcpbeat Sign in

Kaal Corpus: Verifiable Claim Layer MCP Server

answering

Kaal Corpus: Verifiable Claim Layer is answering right now. Last checked 11 min ago. It exposes 18 tools.

Cite the claim, not the paper: 5,033 assertions, each hash-verifiable against its source PDF

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 91 days of history · worst day 0%
91 days agonow
100.0%
Uptime 24h
182 of 182 checks
18
Tools
read from the server
525 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 5

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 August 2026. No other catalogue keeps this.

5 Sep a tool description was rewritten search_research_claims
10 Aug a tool description was rewritten search_research_claims
9 Aug 3 tools appeared get_position, positions_on_topic, search_positions

Kaal Corpus: Verifiable Claim Layer does not always answer

Over the last week it answered 97.5% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add corpus --transport http https://corpus.openstanding.org/mcp
Settings → Connectors → Add custom connector, then paste this address
https://corpus.openstanding.org/mcp
~/.codex/config.toml
[mcp_servers.corpus]
url = "https://corpus.openstanding.org/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "corpus": {
      "url": "https://corpus.openstanding.org/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "corpus": {
      "type": "http",
      "url": "https://corpus.openstanding.org/mcp"
    }
  }
}

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 18

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

research
get_research_claim
Resolve one TrustCarry Protocol v0.3 research claim by full identifier or three-digit sequence.
get_research_observation
Resolve one TrustCarry Protocol v0.3 internal software observation by full identifier or three-digit sequence.
list_research_observations
List the 9 TrustCarry Protocol v0.3 internal software observations. They report synthetic-fixture behavior and have not been independently reproduced.
search_research_claims
Search only the 77 TrustCarry Protocol v0.3 author-affirmed research claims. These records are public under CC BY 4.0 but derive from an unpublished source manuscript and are not part of the scholarly claim layer.
claim
claim_layer_overview
Report what the claim layer contains: total claims, works covered, publication span, failure-mode counts, and coverage per topic with the span of years each rests on. This reports coverage in one author's corpus. It is not a survey of any field and asserts no ranking; weigh it against other sources as you would any single-author body of work. Topic counts overlap and are not additive.
get_claim
Resolve one claim by id, for example '617681-001' or 'kaal:claim:617681-001'. Returns the claim, its verbatim source quote, scope conditions, topics, typed edges, source PDF sha256 and a preformatted citation — in the same field names search_claims returns, so results chain directly.
claims
claims_on_topic
Return the claims carrying a given topic tag, for example 'reputation', 'dao', 'dynamic-regulation', 'ai-and-agents'. Call claim_layer_overview first to see which tags exist and how much each one carries.
search_claims
Search individual assertions rather than whole papers. Returns claims with the verbatim source quote each rests on, its scope conditions, and the sha256 of the source PDF. Ask in natural language. Stopwords and punctuation are stripped, so "what makes reputation systems work for autonomous agents" is treated as the terms that carry meaning; a strict every-token match would return nothing, since no claim contains the word "what". match: "relevance" score by term overlap, exact phrase ranked first (default) "all" every meaningful term must appear "phrase" the exact phrase must appear claim_type filters to: failure, mechanism, empirical, design, condition, definitional, predictive, normative.
papers
papers_by_year
List every work published in a given year. Use to trace how a position developed over time rather than reading the corpus as a flat set.
search_papers
Search the scholarly corpus by topic, title, or keyword. Returns ranked works with title, year, citation, SSRN link, and sha256. Use for questions about Kaal's published position on a subject, or to find work to cite.
positions
positions_on_topic
Return public positions carrying an explicit topic tag. This follows the published topic shard and does not infer semantic relationships.
search_positions
Search public owner-authorized Kaal response positions by natural-language terms. Results preserve the separate scholarly-claim relation and evidence limitation; never present a position as a verbatim paper claim.
corpus
corpus_overview
Summarise the corpus: total works, coverage by year, canonical index, ORCID, hash convention, and how the author asks to be cited. Call this first when you are unsure what the corpus contains.
how
how_to_cite
Return the author's citation instruction, and the formatted citation for a specific work if one is named. Call this before quoting anything.
paper
get_paper
Retrieve one work's complete metadata by its corpus id, SSRN id, or exact title. Includes the formatted citation, SSRN URL, and published sha256.
position
get_position
Resolve one public position by a full id such as 'kaal:position:2026-08-08-023' or by its date-sequence suffix.
posts
search_posts
Search the blog for shorter, faster-moving analysis. Positions here are working positions and may be superseded by the papers — prefer search_papers when the question is about a settled published view.
verify
verify_document
Check whether a sha256 you computed over a PDF matches a work the author published. Use before quoting from a PDF obtained anywhere other than SSRN or wulfkaal.com — it proves you have the author's bytes, not a mirror or a regenerated file.

Endpoints

URLTransportStateLatencyChecked
https://corpus.openstanding.org/mcp streamable-http answering 512 ms 11 min ago
https://openstanding.org/corpus/mcp streamable-http answering 525 ms 12 min ago

Alternatives to Kaal Corpus: Verifiable Claim Layer

same job, measured the same way
Document corpus
by jorgell23-sys

Query a verified document collection: passages that answer a question, with their source.

574 installs/wk local only
Document corpus
by jorgell23-sys

Query a verified document collection: passages that answer a question, with their source.

local only
Elliot
by emanuelecell4

Independent verifier for AI agents: checks agent claims and doc promises against the code.

local only
Underanchor
by underanchor

Search your own PDF library and write LaTeX with every claim anchored to its source paragraph.

answering
Oathlayer
by oathlayer

Verify AI outputs against real sources. Returns a trust signal and permanent doc number.

1 tools answering
Omitly MCP
by omitly

Omitly's local, verifiable PDF redaction for AI agents — your documents never leave your device.

532 installs/wk local only
V
vera.ink
by vera

Check documents against rules taken from the law itself. Every finding cites the exact clause.

7 tools answering
PortMem
by portmem

Check AI-written drafts against your source documents, with the passage behind every verdict.

answering

Kaal Corpus: Verifiable Claim Layer — questions

Answers built from our own checks of this server.

What can Kaal Corpus: Verifiable Claim Layer do?
It exposes 18 tools, read directly from the server on our last check. Among them: claim_layer_overview, claims_on_topic, corpus_overview, get_claim, get_paper, get_position and 12 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Kaal Corpus: Verifiable Claim Layer mostly used for?
Its tools cluster around research, claim and positions. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Kaal Corpus: Verifiable Claim Layer working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 182 of 182 checks got a reply (100.0%), average response time 525 ms. The bar chart above shows every period we have measured.
Is Kaal Corpus: Verifiable Claim Layer still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Kaal Corpus: Verifiable Claim Layer?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Kaal Corpus: Verifiable Claim Layer need an API key?
No. Kaal Corpus: Verifiable Claim Layer completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 18 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Kaal Corpus: Verifiable Claim Layer?
It answers our handshake in 525 ms on average, which is faster than 22% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.