screen_name — GCC Sanctions & Terror-List Screener MCP Tool
screen_name
(screen name) is one of 5 tools on the
GCC Sanctions & Terror-List Screener
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call screen_name from your client
- Claude Code GCC Sanctions & Terror-List Screener screen_name run in your project directory
- Claude Desktop GCC Sanctions & Terror-List Screener screen_name ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor GCC Sanctions & Terror-List Screener screen_name ~/.cursor/mcp.json
- VS Code GCC Sanctions & Terror-List Screener screen_name .vscode/mcp.json
- Zed GCC Sanctions & Terror-List Screener screen_name ~/.config/zed/settings.json
- Windsurf GCC Sanctions & Terror-List Screener screen_name ~/.codeium/windsurf/mcp_config.json
- Cline GCC Sanctions & Terror-List Screener screen_name ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI GCC Sanctions & Terror-List Screener screen_name ~/.gemini/settings.json
- Grok GCC Sanctions & Terror-List Screener screen_name .mcp.json (in your project root)
- ChatGPT GCC Sanctions & Terror-List Screener screen_name Settings → Connectors → Advanced → Developer mode
- Claude.ai GCC Sanctions & Terror-List Screener screen_name Settings → Connectors → Add custom connector
- LangChain GCC Sanctions & Terror-List Screener screen_name pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http sanctions-screener https://screen.noahsarch.tech/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 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.