screen_sanctions — agentum entity resolver MCP Tool
screen_sanctions
(screen sanctions) is one of 6 tools on the
agentum entity resolver
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call screen_sanctions from your client
- Claude Code agentum entity resolver screen_sanctions run in your project directory
- Claude Desktop agentum entity resolver screen_sanctions ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor agentum entity resolver screen_sanctions ~/.cursor/mcp.json
- VS Code agentum entity resolver screen_sanctions .vscode/mcp.json
- Zed agentum entity resolver screen_sanctions ~/.config/zed/settings.json
- Windsurf agentum entity resolver screen_sanctions ~/.codeium/windsurf/mcp_config.json
- Cline agentum entity resolver screen_sanctions ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI agentum entity resolver screen_sanctions ~/.gemini/settings.json
- Grok agentum entity resolver screen_sanctions .mcp.json (in your project root)
- ChatGPT agentum entity resolver screen_sanctions Settings → Connectors → Advanced → Developer mode
- Claude.ai agentum entity resolver screen_sanctions Settings → Connectors → Add custom connector
- LangChain agentum entity resolver screen_sanctions pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agentum-entity-resolver https://agentum.asimplek.cloud/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 5 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.