check_breach — RelayShield Scam Checks MCP Tool Read-only
check_breach
(check breach) is one of 4 tools on the
RelayShield Scam Checks
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_breach from your client
- Claude Code RelayShield Scam Checks check_breach run in your project directory
- Claude Desktop RelayShield Scam Checks check_breach ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor RelayShield Scam Checks check_breach ~/.cursor/mcp.json
- VS Code RelayShield Scam Checks check_breach .vscode/mcp.json
- Zed RelayShield Scam Checks check_breach ~/.config/zed/settings.json
- Windsurf RelayShield Scam Checks check_breach ~/.codeium/windsurf/mcp_config.json
- Cline RelayShield Scam Checks check_breach ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI RelayShield Scam Checks check_breach ~/.gemini/settings.json
- Grok RelayShield Scam Checks check_breach .mcp.json (in your project root)
- ChatGPT RelayShield Scam Checks check_breach Settings → Connectors → Advanced → Developer mode
- Claude.ai RelayShield Scam Checks check_breach Settings → Connectors → Add custom connector
- LangChain RelayShield Scam Checks check_breach pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http relayshield-free-mcp https://relayshieldadmin-relayshield-free-mcp.hf.space/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 30 September 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.