WorldIP Now Speaks MCP: IP Intelligence Inside Your AI Assistant
If you have ever pasted an IP address into a chat window and asked "whose is this?", you know the answer usually involves opening three tabs. We have just removed those tabs. WorldIP.io now runs a Model Context Protocol (MCP) server, so an AI assistant can query our dataset directly, mid-conversation, and answer with real data instead of a guess.
What MCP actually is
MCP is an open standard for connecting AI assistants to external tools and data. Rather than an assistant recalling something it may have half-memorised during training — which for IP data ages badly, because address space is reassigned constantly — it calls a live service and gets the current answer. Our server exposes WorldIP as one of those services.
Two tools, live today
lookup_ip returns the full profile for any public IPv4 address: the owning organisation, ASN, country, region and city where we have it, CIDR range, reverse DNS (PTR), and forward-confirmed DNS.
whats_my_ip returns the caller's own public address and its profile — handy for the surprisingly common "what am I connecting from, and does that look right?" question.
Connecting to it
The endpoint is https://worldip.io/mcp, speaking JSON-RPC 2.0 over HTTP POST. It needs no API key and no account. Point your MCP-capable client at that URL and the tools appear. Free use is rate-limited per IP, which is plenty for interactive work; if you are building something that needs more, talk to us.
The same data over plain curl
Not everything is an assistant, so the keyless JSON API remains the simplest way in. Request any address as a path and you get JSON back:
curl https://worldip.io/8.8.8.8
No key, no signup, no SDK — owner and organisation, ASN, country, geolocation where available, reverse and forward DNS, and the CIDR range. It is the same core data the site itself renders.
A note on what "where available" means
We would rather be precise than flattering: city-level geolocation exists for a fraction of the address space, and for anycast addresses like public resolvers a country-level answer is the honest one. Where we do not have a confident city, we say nothing rather than invent a plausible-looking pin. That principle runs through the whole dataset.
What is coming
Several things are in flight. We are expanding what the API returns and adding depth to the routing and reputation signals behind it. And the larger project now underway is IPv6 — dedicated scanning infrastructure and a v6 dataset built the same way as our v4 one, first-party and continuously refreshed, rather than licensed in. More on that soon.
Questions, or something you want the MCP server to be able to answer? Tell us — the tool list is deliberately short right now, and we would rather grow it based on what people actually ask for.
