fair_registry_boundaries — FAIR Appraisers MCP Resource
fair_registry_boundaries
is one of 4 resources on the
FAIR Appraisers
MCP server. Connect the server and your client can attach it as context.
by client
How to attach fair_registry_boundaries from your client
- Claude Code FAIR Appraisers Resource/fair_registry_boundaries run in your project directory
- Claude Desktop FAIR Appraisers Resource/fair_registry_boundaries ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor FAIR Appraisers Resource/fair_registry_boundaries ~/.cursor/mcp.json
- VS Code FAIR Appraisers Resource/fair_registry_boundaries .vscode/mcp.json
- Zed FAIR Appraisers Resource/fair_registry_boundaries ~/.config/zed/settings.json
- Windsurf FAIR Appraisers Resource/fair_registry_boundaries ~/.codeium/windsurf/mcp_config.json
- Cline FAIR Appraisers Resource/fair_registry_boundaries ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI FAIR Appraisers Resource/fair_registry_boundaries ~/.gemini/settings.json
- Grok FAIR Appraisers Resource/fair_registry_boundaries .mcp.json (in your project root)
- ChatGPT FAIR Appraisers Resource/fair_registry_boundaries Settings → Connectors → Advanced → Developer mode
- Claude.ai FAIR Appraisers Resource/fair_registry_boundaries Settings → Connectors → Add custom connector
- LangChain FAIR Appraisers Resource/fair_registry_boundaries pip install langchain-mcp-adapters
Other resources on this server
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.