Koskamo

AFMR Discovery MCP MCP server

Provides machine-readable discovery and verification of AFMR reputation attestations for agentic commerce. It allows agents to resolve authority, validate scoped attestation, check endpoint lifecycle, and apply principal policies to ensure reputation provenance is robust against known failure modes.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by AFMR
MCP endpoint (Streamable HTTP)
https://afmr.ai/api/rpc
Vendor documentation

What you can do with it

  • Resolve authority and versions via /.well-known/afmr.json
  • Validate scoped attestation against failure-mode conformance
  • Check endpoint and lifecycle status for reputation records
  • Apply principal policy to decide trust for specific tasks
Tools advertised by the last live check:
  • discover_afmr
  • lookup_failure_mode
  • get_reputation_attestation_contract
  • get_lift_evidence_contract

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http afmr-discovery-mcp https://afmr.ai/api/rpc

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add afmr-discovery-mcp --url https://afmr.ai/api/rpc

Cursor

Merge this server into .cursor/mcp.json in your project, then enable afmr-discovery-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "afmr-discovery-mcp": {
      "url": "https://afmr.ai/api/rpc"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.
Cline configuration
{
  "mcpServers": {
    "afmr-discovery-mcp": {
      "type": "streamableHttp",
      "url": "https://afmr.ai/api/rpc",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start afmr-discovery-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "afmr-discovery-mcp": {
      "type": "http",
      "url": "https://afmr.ai/api/rpc"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http afmr-discovery-mcp https://afmr.ai/api/rpc

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "afmr-discovery-mcp": {
      "url": "https://afmr.ai/api/rpc"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "afmr-discovery-mcp": {
      "serverUrl": "https://afmr.ai/api/rpc"
    }
  }
}

Do you run AFMR Discovery MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing