List your agent

AFMR: Agent Failure Mode Registry, and the Kaal Corpus claim layer

MCP server● onlineInstallablev1.1.0

Screen agent, DAO, and reputation designs against 32 named failure modes with checkable conditions

What you can do with it

Share of each task's required capabilities it covers

Prefer a ready-made agent?

An MCP server is a connector for your own assistant. These finished products do the job for you: fact-check a document.
All AI agents to fact-check a document, ranked →

Similar tools

Listed for the same task: fact-check a document

Reviews

No review yet. Used AFMR: Agent Failure Mode Registry, and the Kaal Corpus claim layer? Be the first to help others choose.

What it does

AFMR: Agent Failure Mode Registry, and the Kaal Corpus claim layer is an MCP server, a connector that lets an AI assistant use it as a tool. It is installed locally as a package and runs on your machine.

From the publisher's description, Electra Index matched it to one capability: document understanding. That makes it a candidate for tasks such as fact-check a document or analyze financial documents.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)NO
Local installYES
Version1.1.0
PackagesMCP bundle
PriceNot in the registry
First seen26 Sept 2026
Last checked7h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 53m ago (live check)

Hosted endpoints

  • https://corpus.openstanding.org/mcp streamable-http
  • https://openstanding.org/corpus/mcp streamable-http

In Claude Code: claude mcp add --transport http kaal-corpus-verifiable-claim-layer https://corpus.openstanding.org/mcp

Install package

  • MCP BUNDLE https://github.com/wulfkaal/wulfkaal.github.io/releases/download/mcpb-v1.1.0/kaal-corpus.mcpb v1.1.0 · runs locally (stdio)

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "kaal-corpus-verifiable-claim-layer": {
      "url": "https://corpus.openstanding.org/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 53m ago

ONLINE AFMR: Agent Failure Mode Registry, and the Kaal Corpus claim layer answered an MCP connection on 17 Nov 2026 and introduced itself as Kaal Corpus 1.28.1 (MCP protocol 2025-06-18).

18 tools offered to AI assistants

  • 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.
  • 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.
  • 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.
  • 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.
  • 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_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.
  • 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.
  • 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
  • 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 searc
  • 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_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.
  • get_position · Resolve one public position by a full id such as 'kaal:position:2026-08-08-023' or by its date-sequence suffix.
Show 6 more
  • positions_on_topic · Return public positions carrying an explicit topic tag. This follows the published topic shard and does not infer semantic relationships.
  • 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 f
  • 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.
  • get_research_claim · Resolve one TrustCarry Protocol v0.3 research claim 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.
  • get_research_observation · Resolve one TrustCarry Protocol v0.3 internal software observation by full identifier or three-digit sequence.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Install packagehttps://github.com/wulfkaal/wulfkaal.github.io/releases/download/mcpb-v1.1.0/kaal-corpus.mcpbDECLAREDSRC-001 Official MCP Registry7h ago
Remote access (hosted)noDECLAREDSRC-001 Official MCP Registry7h ago
Version1.1.0DECLAREDSRC-001 Official MCP Registry7h ago
Hosted endpointhttps://corpus.openstanding.org/mcp, https://openstanding.org/corpus/mcpDECLAREDSRC-001 Official MCP Registry19h ago
Package registriesmcpbDECLAREDSRC-001 Official MCP Registry7h ago
Local install (package)yesDECLAREDSRC-001 Official MCP Registry7h ago
Websitehttps://wulfkaal.github.io/DECLAREDSRC-001 Official MCP Registry7h ago
Repositoryhttps://github.com/wulfkaal/wulfkaal.github.ioDECLAREDSRC-001 Official MCP Registry7h ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry7h ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry7h ago

Change history

  • CHANGED16 Nov 2026
    remote access: yes → no
  • VERSION16 Nov 2026
    1.0.1 → 1.1.0

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you publish AFMR: Agent Failure Mode Registry, and the Kaal Corpus claim layer? Get it seen by people choosing a tool

For publishers · optional

Launch Spotlight: 60 days of clearly labelled Sponsored visibility on the use-case pages where AFMR: Agent Failure Mode Registry, and the Kaal Corpus claim layer already appears, plus the weekly Pulse. No click in 60 days? The next 60 days are free.

See where it would appearLaunch offer $14.99 once instead of $69.99 · All plans

Sponsored placements never change a score or a rank.

Are you the publisher of AFMR: Agent Failure Mode Registry, and the Kaal Corpus claim layer?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/kaal-corpus-verifiable-claim-layer?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/kaal-corpus-verifiable-claim-layer/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about AFMR: Agent Failure Mode Registry, and the Kaal Corpus claim layer

How do I connect AFMR: Agent Failure Mode Registry, and the Kaal Corpus claim layer?

Use the hosted endpoint https://corpus.openstanding.org/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does AFMR: Agent Failure Mode Registry, and the Kaal Corpus claim layer offer?

When Electra Index connected on 17 Nov 2026, it listed 18 tools: search_papers, get_paper, papers_by_year, corpus_overview, search_posts, verify_document, how_to_cite, search_claims and more. The full list is in "Live check" above.

Is AFMR: Agent Failure Mode Registry, and the Kaal Corpus claim layer online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 53m ago.

What can I use AFMR: Agent Failure Mode Registry, and the Kaal Corpus claim layer for?

Based on its description, it is most relevant to: fact-check a document, analyze financial documents, analyze patents, answer questions from internal documents.