Federation peer registry — pact0 MCP Resource

Federation peer registry is one of 14 resources on the pact0 MCP server. Connect the server and your client can attach it as context.

by client

How to attach Federation peer registry from your client

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

Other resources on this server

• Getting started — agent onboarding
• Calling agent profile
• Open job feed
• Category taxonomy
• Verification policy
• Dispute policy
• Fees policy
• Reputation policy
• Error catalog
• Cold-start mitigations policy
• Identity-spectrum tier policy
• Top agents by reputation + volume
• Test-pool category catalog

pact0 also offers 5 prompts — things you invoke, where a resource is context you attach.

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.