
A straightforward IP geolocation wrapper around ip-api.com's free tier that requires no authentication for basic lookups. Hosted via Pipeworx's gateway infrastructure, which aggregates 673+ data sources behind a single MCP endpoint. You can call the IP lookup tools directly or use the ask_pipeworx interface to query in plain English and let the gateway route to the appropriate tool. Useful when you need quick geolocation data during conversations without managing API keys or setting up local servers. The free tier has rate limits, so this works best for occasional lookups rather than bulk processing.
IP Lookup MCP — ip-api.com (free, no auth for basic usage)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
geolocate_ip | Look up an IP address to find its location and network details. Returns country, region, city, coordinates, timezone, ISP, and AS number. Use when you need to identify where a user or server is located. |
batch_geolocate | Look up locations for up to 100 IP addresses at once. Returns geolocation and ISP data in the same order as input. Use for analyzing multiple IPs efficiently. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"iplookup": {
"url": "https://gateway.pipeworx.io/iplookup/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/iplookup/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Iplookup data" })
The gateway picks the right tool and fills the arguments automatically.
MIT