Search arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.
Nothing to run from here
Kaal Corpus: Verifiable Claim Layer is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
18
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Cite the claim, not the paper: 5,033 assertions, each hash-verifiable against its source PDF
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http kaal-corpus-verifiable-claim-layer-mcp https://corpus.openstanding.org/mcp
# 2 — ask your agent for something these tools do
# search_papers, get_paper, papers_by_year and 15 more
Kaal Corpus: Verifiable Claim Layer costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
WUAll 1 server
wulfkaal1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http kaal-corpus-verifiable-claim-layer-mcp https://corpus.openstanding.org/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
18 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
| limit | integer | no | — |
Retrieve one work's complete metadata by its corpus id, SSRN id, or exact title. Includes the formatted citation, SSRN URL, and published sha256.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| paper_id | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| year | integer | yes | — |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sha256 | string | yes | — |
Return the author's citation instruction, and the formatted citation for a specific work if one is named. Call this before quoting anything.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| paper_id | string | no | — |
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 ret
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
| limit | integer | no | — |
| claim_type | string | no | — |
| failure_modes_only | boolean | no | — |
| match | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| claim_id | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | — |
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
| limit | integer | no | — |
Resolve one public position by a full id such as 'kaal:position:2026-08-08-023' or by its date-sequence suffix.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| position_id | string | yes | — |
Return public positions carrying an explicit topic tag. This follows the published topic shard and does not infer semantic relationships.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | — |
| limit | integer | no | — |
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 a
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
| limit | integer | no | — |
Resolve one TrustCarry Protocol v0.3 research claim by full identifier or three-digit sequence.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| claim_id | string | yes | — |
List the 9 TrustCarry Protocol v0.3 internal software observations. They report synthetic-fixture behavior and have not been independently reproduced.
No parameter schema on file.
Resolve one TrustCarry Protocol v0.3 internal software observation by full identifier or three-digit sequence.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| observation_id | string | yes | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Kaal Corpus: Verifiable Claim Layer or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.1.
1.0.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Kaal Corpus: Verifiable Claim Layer can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.