Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Kaal Corpus: Verifiable Claim Layer

REMOTE · OPENSTANDING.ORG · 3 COMPONENTS · SCANNED SEP 20

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

0 this week 83 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security69
Transport & Reachability100
Schema Quality & AI Usability85
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1582 tokens (~79/item across 20 items; 18 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Kaal Corpus: Verifiable Claim Layer MCP server?

Kaal Corpus: Verifiable Claim Layer is a hosted endpoint at https://openstanding.org/corpus/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · openstanding.org

# add to Claude Code
claude mcp add --transport http wulfkaal-corpus 'https://openstanding.org/corpus/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "wulfkaal-corpus": {
      "url": "https://openstanding.org/corpus/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "wulfkaal-corpus": {
      "type": "http",
      "url": "https://openstanding.org/corpus/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.wulfkaal-corpus]
url = "https://openstanding.org/corpus/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wulfkaal-corpus": {
      "type": "remote",
      "url": "https://openstanding.org/corpus/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add wulfkaal-corpus --url 'https://openstanding.org/corpus/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  wulfkaal-corpus:
    url: "https://openstanding.org/corpus/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "wulfkaal-corpus": {
      "Transport": "http",
      "Url": "https://openstanding.org/corpus/mcp"
    }
  }
}
# add to Vellum
assistant mcp add wulfkaal-corpus -t streamable-http -u 'https://openstanding.org/corpus/mcp'
// mcp.json
{
  "mcpServers": {
    "wulfkaal-corpus": {
      "type": "http",
      "url": "https://openstanding.org/corpus/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 6 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “search_research_claims” rewrote its description, which is the text the model reads security
  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 +1
    • Stability: 0.97 → pass security
  • 23 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 10 Aug 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 1379 → 1590 functional
    • Schema quality: good → excellent functional
    • New tool “positions_on_topic” functional
    • New tool “get_position” functional
    • New tool “search_positions” functional
  • 7 Aug 26 0
    • The server no longer declares the “experimental” capability functional
  • 2 Aug 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 96 → 81 functional
    • First check of Schema quality: 100 functional
    • Schema quality: excellent → good functional
    • New resource “trustcarry_research_observations_index” functional
    • New resource “trustcarry_research_claims_index” functional
    • New tool “search_research_claims” functional
    • New tool “list_research_observations” functional
    • New tool “get_research_observation” functional
    • New tool “get_research_claim” functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://openstanding.org/corpus/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=openstanding.org CN=WE1,O=Google Trust Services,C=US 20 Sept 2026 19 Dec 2026 ECDSA 256 ECDSA-SHA256 bc900bdc0bf07c530e437ba87e1de6bf
SANs: openstanding.org, *.openstanding.org
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of openstanding.org. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
org. present 26974 8 Verified
openstanding.org. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'none'; style-src 'unsafe-inline'; img-src data:; frame-ancestors 'none'; base-uri 'none'; form-action 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://openstanding.org/corpus/mcp Verified 200
http (plaintext) http://openstanding.org/corpus/mcp Inconclusive 406
MCP tools · 18 exposed · ~1,244 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
claim_layer_overview ~95

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes

No examples provided.

claims_on_topic ~73

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.

NameTypeReqDescription
limitinteger
topicstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

corpus_overview ~55

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes

No examples provided.

get_claim ~93

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.

NameTypeReqDescription
claim_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

get_paper ~52

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

NameTypeReqDescription
paper_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

get_position ~51

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

NameTypeReqDescription
position_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

get_research_claim ~39

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

NameTypeReqDescription
claim_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

get_research_observation ~41

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

NameTypeReqDescription
observation_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

how_to_cite ~45

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

NameTypeReqDescription
paper_idstring
NameTypeReqDescription
resultstringyes

No examples provided.

list_research_observations ~43

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

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes

No examples provided.

papers_by_year ~46

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.

NameTypeReqDescription
yearintegeryes
NameTypeReqDescription
resultstringyes

No examples provided.

positions_on_topic ~47

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

NameTypeReqDescription
limitinteger
topicstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

search_claims ~208

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.

NameTypeReqDescription
claim_typestring
failure_modes_onlyboolean
limitinteger
matchstring
querystringyes
NameTypeReqDescription
resultstringyes

No examples provided.

search_papers ~77

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.

NameTypeReqDescription
limitinteger
querystringyes
NameTypeReqDescription
resultstringyes

No examples provided.

search_positions ~63

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.

NameTypeReqDescription
limitinteger
querystringyes
NameTypeReqDescription
resultstringyes

No examples provided.

search_posts ~64

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.

NameTypeReqDescription
limitinteger
querystringyes
NameTypeReqDescription
resultstringyes

No examples provided.

search_research_claims ~78

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.

NameTypeReqDescription
limitinteger
querystringyes
NameTypeReqDescription
resultstringyes

No examples provided.

verify_document ~74

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.

NameTypeReqDescription
sha256stringyes
NameTypeReqDescription
resultstringyes

No examples provided.

Common questions

What is the Kaal Corpus: Verifiable Claim Layer MCP server?

Kaal Corpus: Verifiable Claim Layer is an MCP server listed in the public MCP registry as io.github.wulfkaal/corpus. Cite the claim, not the paper: 5,033 assertions, each hash-verifiable against its source PDF. This page covers its hosted endpoint (https://openstanding.org/corpus/mcp).

Is the Kaal Corpus: Verifiable Claim Layer MCP server safe to use?

Kaal Corpus: Verifiable Claim Layer scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Kaal Corpus: Verifiable Claim Layer MCP server expose?

Kaal Corpus: Verifiable Claim Layer exposes 18 tools: search_papers, get_paper, papers_by_year, corpus_overview, search_posts, and 13 more. Their descriptions and schemas cost roughly 1,244 tokens of context every time the server is loaded.

Does the Kaal Corpus: Verifiable Claim Layer MCP server require authentication?

No. We connected to Kaal Corpus: Verifiable Claim Layer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Kaal Corpus: Verifiable Claim Layer MCP server still maintained?

Kaal Corpus: Verifiable Claim Layer is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.