Index / MCP servers / AFMR: Agent Failure Mode Registry, and the Kaal Corpus claim layer

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

AFMR: Agent Failure Mode Registry, and the Kaal Corpus claim layer is a remote MCP server that gives an AI agent 18 tools, among them claim_layer_overview, claims_on_topic, corpus_overview. It answers at https://registry.modelcontextprotocol.io/v0/servers?search=io.github.wulfkaal/corpus over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 7 of 7 times since 11 September 2026; the last check, on 12 November 2026, succeeded.

Status
Answering
Tools
18
Reliability
7 of 7 checks
Response time
463 ms
Transport
streamable HTTP
Last checked
12 November 2026

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

Description as the publisher wrote it.

The 18 tools AFMR: Agent Failure Mode Registry, and the Kaal Corpus claim layer offers

ToolWhat it does
claim_layer_overviewReport 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
claims_on_topicReturn 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.
Inputs: topic, limit
corpus_overviewSummarise 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_claimResolve 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
Inputs: claim_id
get_paperRetrieve one work's complete metadata by its corpus id, SSRN id, or exact title. Includes the formatted citation, SSRN URL, and published sha256.
Inputs: paper_id
get_positionResolve one public position by a full id such as 'kaal:position:2026-08-08-023' or by its date-sequence suffix.
Inputs: position_id
get_research_claimResolve one TrustCarry Protocol v0.3 research claim by full identifier or three-digit sequence.
Inputs: claim_id
get_research_observationResolve one TrustCarry Protocol v0.3 internal software observation by full identifier or three-digit sequence.
Inputs: observation_id
how_to_citeReturn the author's citation instruction, and the formatted citation for a specific work if one is named. Call this before quoting anything.
Inputs: paper_id
list_research_observationsList the 9 TrustCarry Protocol v0.3 internal software observations. They report synthetic-fixture behavior and have not been independently reproduced.
papers_by_yearList 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.
Inputs: year
positions_on_topicReturn public positions carrying an explicit topic tag. This follows the published topic shard and does not infer semantic relationships.
Inputs: topic, limit
search_claimsSearch 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
Inputs: query, limit, claim_type, failure_modes_only, match
search_papersSearch 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.
Inputs: query, limit
search_positionsSearch 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.
Inputs: query, limit
search_postsSearch 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.
Inputs: query, limit
search_research_claimsSearch 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.
Inputs: query, limit
verify_documentCheck 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.
Inputs: sha256

Add AFMR: Agent Failure Mode Registry, and the Kaal Corpus claim layer to your AI client

Every block below points at https://registry.modelcontextprotocol.io/v0/servers?search=io.github.wulfkaal/corpus. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http afmr-agent-failure-mode-registry https://registry.modelcontextprotocol.io/v0/servers?search=io.github.wulfkaal/corpus
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "afmr-agent-failure-mode-registry": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://registry.modelcontextprotocol.io/v0/servers?search=io.github.wulfkaal/corpus"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "afmr-agent-failure-mode-registry": {
      "url": "https://registry.modelcontextprotocol.io/v0/servers?search=io.github.wulfkaal/corpus"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "afmr-agent-failure-mode-registry": {
      "type": "http",
      "url": "https://registry.modelcontextprotocol.io/v0/servers?search=io.github.wulfkaal/corpus"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "afmr-agent-failure-mode-registry": {
      "url": "https://registry.modelcontextprotocol.io/v0/servers?search=io.github.wulfkaal/corpus"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "afmr-agent-failure-mode-registry": {
      "serverUrl": "https://registry.modelcontextprotocol.io/v0/servers?search=io.github.wulfkaal/corpus"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "afmr-agent-failure-mode-registry": {
      "url": "https://registry.modelcontextprotocol.io/v0/servers?search=io.github.wulfkaal/corpus"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: AFMR: Agent Failure Mode Registry, and the Kaal Corpus claim layer
version: 0.0.1
schema: v1
mcpServers:
  - name: AFMR: Agent Failure Mode Registry, and the Kaal Corpus claim layer
    type: streamable-http
    url: https://registry.modelcontextprotocol.io/v0/servers?search=io.github.wulfkaal/corpus
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "afmr-agent-failure-mode-registry": {
      "httpUrl": "https://registry.modelcontextprotocol.io/v0/servers?search=io.github.wulfkaal/corpus"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "afmr-agent-failure-mode-registry": {
      "type": "http",
      "url": "https://registry.modelcontextprotocol.io/v0/servers?search=io.github.wulfkaal/corpus"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "afmr-agent-failure-mode-registry": {
      "url": "https://registry.modelcontextprotocol.io/v0/servers?search=io.github.wulfkaal/corpus"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fregistry.modelcontextprotocol.io%2Fv0%2Fservers%3Fsearch%3Dio.github.wulfkaal%2Fcorpus&type=streamable_http&id=afmr-agent-failure-mode-registry&name=AFMR%3A%20Agent%20Failure%20Mode%20Registry%2C%20and%20the%20Kaal%20Corpus%20claim%20layer

Is AFMR: Agent Failure Mode Registry, and the Kaal Corpus claim layer up right now?

It answered our last check on 12 November 2026 in 463 ms. Over 7 checks since 11 September 2026 it answered 7. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to AFMR: Agent Failure Mode Registry, and the Kaal Corpus claim layer

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

How many tools does AFMR: Agent Failure Mode Registry, and the Kaal Corpus claim layer have?

18, as returned by the server's own tools/list on 22 September 2026: claim_layer_overview, claims_on_topic, corpus_overview, get_claim, get_paper, get_position, get_research_claim, get_research_observation, and 10 more.

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

It answered our last check on 12 November 2026 in 463 ms. Over 7 checks since 11 September 2026 it answered 7.

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

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://registry.modelcontextprotocol.io/v0/servers?search=io.github.wulfkaal/corpus. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does AFMR: Agent Failure Mode Registry, and the Kaal Corpus claim layer need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.github.wulfkaal. Endpoint host: registry.modelcontextprotocol.io. ARD identifier: urn:air:io.github.wulfkaal:mcp:corpus. First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.