check_mcp_keys — TamingDNS MCP Tool Read-only
check_mcp_keys
(check mcp keys) is one of 19 tools on the
TamingDNS
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_mcp_keys from your client
- Claude Code TamingDNS check_mcp_keys run in your project directory
- Claude Desktop TamingDNS check_mcp_keys ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TamingDNS check_mcp_keys ~/.cursor/mcp.json
- VS Code TamingDNS check_mcp_keys .vscode/mcp.json
- Zed TamingDNS check_mcp_keys ~/.config/zed/settings.json
- Windsurf TamingDNS check_mcp_keys ~/.codeium/windsurf/mcp_config.json
- Cline TamingDNS check_mcp_keys ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TamingDNS check_mcp_keys ~/.gemini/settings.json
- Grok TamingDNS check_mcp_keys .mcp.json (in your project root)
- ChatGPT TamingDNS check_mcp_keys Settings → Connectors → Advanced → Developer mode
- Claude.ai TamingDNS check_mcp_keys Settings → Connectors → Add custom connector
- LangChain TamingDNS check_mcp_keys pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://tamingdns.com/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.