Canonical AFMR failure-mode registry — AFMR Discovery MCP Resource

Canonical AFMR failure-mode registry is one of 8 resources on the AFMR Discovery MCP server. Connect the server and your client can attach it as context.

by client

How to attach Canonical AFMR failure-mode registry from your client

• Claude Code AFMR Discovery Resource/Canonical AFMR failure-mode registry run in your project directory
• Claude Desktop AFMR Discovery Resource/Canonical AFMR failure-mode registry ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor AFMR Discovery Resource/Canonical AFMR failure-mode registry ~/.cursor/mcp.json
• VS Code AFMR Discovery Resource/Canonical AFMR failure-mode registry .vscode/mcp.json
• Zed AFMR Discovery Resource/Canonical AFMR failure-mode registry ~/.config/zed/settings.json
• Windsurf AFMR Discovery Resource/Canonical AFMR failure-mode registry ~/.codeium/windsurf/mcp_config.json
• Cline AFMR Discovery Resource/Canonical AFMR failure-mode registry ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI AFMR Discovery Resource/Canonical AFMR failure-mode registry ~/.gemini/settings.json
• Grok AFMR Discovery Resource/Canonical AFMR failure-mode registry .mcp.json (in your project root)
• ChatGPT AFMR Discovery Resource/Canonical AFMR failure-mode registry Settings → Connectors → Advanced → Developer mode
• Claude.ai AFMR Discovery Resource/Canonical AFMR failure-mode registry Settings → Connectors → Add custom connector
• LangChain AFMR Discovery Resource/Canonical AFMR failure-mode registry pip install langchain-mcp-adapters

Other resources on this server

• AFMR 1.0 specification
• AFMR discovery document
• Reputation attestation schema
• Reputation attestation verifier requirements
• Conforming governance-endpoint registry
• Lift evidence public-card index
• Lift comparison public-card schema

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.