Skip to content

AFMR MCP server

Which servers in the official MCP registry are AFMR's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-13

← Back to AFMR

Whose server it is
  • Registry nameai.afmr/discoveryverified in the MCP registry

The registry name sits under afmr.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-13
  • Stateanswerschecked 2026-10-13
  • Tools4
  • Server calls itselfai.afmr/discovery
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-13 the server answered initialize and tools/list without a sign-in. First answer in 19 ms.

Tools it offers4 tools · read 2026-10-13
  • discover_afmr

    Return canonical AFMR specifications, registries, schemas, endpoints, and scope boundaries.

  • lookup_failure_mode

    Find exact AFMR 1.0 failure-mode records by permanent ID or bounded text query.

  • get_reputation_attestation_contract

    Return the portable attestation, trust-profile, verifier-result, endpoint-registry, and lifecycle contracts.

  • get_lift_evidence_contract

    Return the stable configuration-scoped public-card schema and empty public index; no results are asserted.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "discovery": {
      "type": "http",
      "url": "https://afmr.ai/mcp"
    }
  }
}

OpenAPI spec

21 paths, read 2026-10-13. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.