Kaal Corpus: Verifiable Claim Layer MCP server

• claim_layer_overviewFree

  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.

• claims_on_topicFree

  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.

• corpus_overviewFree

  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.

• get_claimFree

  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.

• get_paperFree

  Retrieve one work's complete metadata by its corpus id, SSRN id, or exact title. Includes the formatted citation, SSRN URL, and published sha256.

• get_positionFree

  Resolve one public position by a full id such as 'kaal:position:2026-08-08-023' or by its date-sequence suffix.

• get_research_claimFree

  Resolve one TrustCarry Protocol v0.3 research claim by full identifier or three-digit sequence.

• get_research_observationFree

  Resolve one TrustCarry Protocol v0.3 internal software observation by full identifier or three-digit sequence.

• how_to_citeFree

  Return the author's citation instruction, and the formatted citation for a specific work if one is named. Call this before quoting anything.

• list_research_observationsFree

  List the 9 TrustCarry Protocol v0.3 internal software observations. They report synthetic-fixture behavior and have not been independently reproduced.

• papers_by_yearFree

  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.

• positions_on_topicFree

  Return public positions carrying an explicit topic tag. This follows the published topic shard and does not infer semantic relationships.

• search_claimsFree

  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.

• search_papersFree

  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.

• search_positionsFree

  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.

• search_postsFree

  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.

• search_research_claimsFree

  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.

• verify_documentFree

  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.

• –Code scanpackage could not be scannedn/a
• Live reliabilityremote reachable in 1030ms20/20
• Tool poisoning18 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenancelast push 3 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Safety score

91/100

higher than 85% of 48,255 servers

Tools

18

the typical server has 7

Tools that change things

0%

typical: 0%. Fewer write tools means less an agent can break

Uptime

96%

of our recent checks; the typical remote server answers 100%

Response time

494 ms

faster than 30% of 30,031 servers

Kaal Corpus: Verifiable Claim Layer: common questions

Is Kaal Corpus: Verifiable Claim Layer MCP server safe?

Yes, by our scan: it is graded A (91/100). Read the Kaal Corpus: Verifiable Claim Layer safety report

How do I install Kaal Corpus: Verifiable Claim Layer?

It runs remotely at corpus.openstanding.org. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Kaal Corpus: Verifiable Claim Layer need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Kaal Corpus: Verifiable Claim Layer maintained?

The last commit was 13 days ago (2026-10-22). The latest release is v1.0.1.

Is Kaal Corpus: Verifiable Claim Layer up?

96% of our last 28 checks got an answer. We check remote servers about four times a day.

How does Kaal Corpus: Verifiable Claim Layer compare with other MCP servers?

safety score 91/100 (higher than 85% of 48,255 servers); tools 18 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.