mcpbeat

AFMR Discovery MCP Server

ai.afmr/discovery
answering

AFMR Discovery is answering right now. Last checked 13 min ago. It exposes 4 tools.

Read AFMR failure modes and discover scoped attestation and lift-evidence contracts.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
1029 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add discovery --transport http https://afmr.ai/api/rpc
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "discovery": {
      "url": "https://afmr.ai/api/rpc"
    }
  }
}
~/.codex/config.toml
[mcp_servers.discovery]
url = "https://afmr.ai/api/rpc"
.cursor/mcp.json
{
  "mcpServers": {
    "discovery": {
      "url": "https://afmr.ai/api/rpc"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "discovery": {
      "url": "https://afmr.ai/api/rpc"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

discover
discover_afmr
Return canonical AFMR specifications, registries, schemas, endpoints, and scope boundaries.
lift
get_lift_evidence_contract
Return the stable configuration-scoped public-card schema and empty public index; no results are asserted.
lookup
lookup_failure_mode
Find exact AFMR 1.0 failure-mode records by permanent ID or bounded text query.
reputation
get_reputation_attestation_contract
Return the portable attestation, trust-profile, verifier-result, endpoint-registry, and lifecycle contracts.

Endpoints

URLTransportStateLatencyChecked
https://afmr.ai/api/rpc streamable-http answering 1377 ms 13 min ago

AFMR Discovery — questions

Answers built from our own checks of this server.

What can AFMR Discovery do?
It exposes 4 tools, read directly from the server on our last check. Among them: discover_afmr, get_lift_evidence_contract, get_reputation_attestation_contract, lookup_failure_mode. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is AFMR Discovery working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 1029 ms. The bar chart above shows every period we have measured.
How do I connect AFMR Discovery?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does AFMR Discovery need an API key?
No. AFMR Discovery completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is AFMR Discovery?
It answers our handshake in 1029 ms on average, which is faster than 4% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.