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