Reputation attestation verifier requirements — AFMR Discovery MCP Resource

Reputation attestation verifier requirements 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 Reputation attestation verifier requirements from your client

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

Other resources on this server

• Canonical AFMR failure-mode registry
• AFMR 1.0 specification
• AFMR discovery document
• Reputation attestation schema
• 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.