Playbooks · Coding
Give Claude Desktop an IP lookup via MCP
Written November 10, 2026
A language model cannot look up an IP address from memory: it holds no current IP-to-city database, cannot read an ASN from a bare address, and has no way to know whether an address was flagged yesterday. An MCP server fixes that by giving the model a tool that queries a live service. Three such servers plug into Claude Desktop — including one for ipstack, which does have an MCP server, through APILayer.
ipstack, through APILayer
ipstack's own page points to the APILayer MCP server: run npx @apilayer/mcp-server, or connect to the remote endpoint https://mcp.apilayer.com/mcp. It works with Claude Desktop, Cursor, VS Code Copilot, Windsurf and Cline, and covers all three lookup shapes — a single IP, a visitor check, and bulk batches of up to 50 addresses. It uses your existing ipstack access key through one environment variable. The remote configuration looks like this:
{
"mcpServers": {
"apilayer": {
"url": "https://mcp.apilayer.com/mcp",
"headers": {
"Authorization": "Bearer ${env:APILAYER_MCP_TOKEN}"
}
}
}
}
Each lookup returns location, ISP, timezone and threat signals as JSON — the same fields a direct API call returns.
IPinfo's official server
IPinfo launched its official MCP server on April 7, 2026, at https://mcp.ipinfo.io/. Paste your IPinfo access token on that page, then either press "Install in Claude Desktop" or copy the configuration into Claude Desktop by hand, and restart the app. The server supports paid and lite tier API access at the same time. If you already pay for IPinfo, this is the shortest path: one token, one install button, and the lookup runs on the service you already use.
IPIPAI, no key needed
IPIPAI's MCP server, at https://ipipai.com/mcp, exposes eleven tools and needs no API key for normal interactive use. The configuration for Claude Desktop or Claude Code is a URL, not a local command:
{
"mcpServers": {
"ipipai": {
"type": "http",
"url": "https://ipipai.com/mcp"
}
}
}
The eleven tools are lookup_ip (location, ISP, ASN, IP type and risk score in one call), lookup_ip_location (country and city only), check_ip_reputation (proxy/VPN flags, Tor exit status, blacklist and hosting classification), rate_ip_node (a 0–100 score and letter grade for VPS and proxy nodes), check_service_access, lookup_domain_whois, lookup_mac_vendor, resolve_dns, ping_host, trace_route and check_website_availability. After restarting the client, ask it to list its MCP tools: if the eleven appear, the connection works.
Which one to pick
Pick by the account you already have. An ipstack key means the APILayer server. An IPinfo token means the official IPinfo server. No key at all, and you just want to try a lookup from inside Claude Desktop, means IPIPAI — it is the only one of the three that runs without a key. Once connected, ask for a tool call explicitly ("use the lookup_ip tool on this address, then explain the risk score") rather than asking the model where an IP is: a plain question still invites a guess.
Limits
- City-level geolocation is usually right, not always exact. Treat it as a confidence range, not a pinpoint, and do not build a decision on a single lookup.
- Every IP you send to a remote MCP server leaves your machine and reaches the service. Do not send customer IPs to a third-party endpoint unless your policy allows it.
- The ipstack route runs through APILayer's server, not an ipstack-branded one, and it needs a key. The IPinfo route needs a token. Only IPIPAI runs key-free for interactive use.
Related playbooks
- Agent-desktop drives apps via the access tree
- Manage Airbyte pipelines through its MCP server
- Apify MCP Server 0.21.8 hardens the bridge
- AWS MCP server let deny lists silently fail
Sources
- Real-Time IP Lookup API — ipstack
- Using the official IPinfo MCP server in Claude Desktop — IPinfo Community
- IP Geolocation MCP Server: Give Claude and Cursor Real IP Data — IPIPAI Blog
Back to: Coding playbooks hub · Also: MCPhantom: agents install dead MCP servers · Check every package name your agent invents