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