mcpbeat Sign in

IP.LS — IP Lookup Service MCP Server

by ip Your server? Claim it
answering

IP.LS — IP Lookup Service is answering right now. Last checked 6 min ago. It exposes 6 tools.

Keyless IP geolocation, ASN/ISP, timezone and DNS records for any IP or domain, plus your own IP.

Uptime history 46 days of history · worst day 99%
46 days agonow
100.0%
Uptime 24h
92 of 92 checks
6
Tools
read from the server
672 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 4

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 25 September 2026. No other catalogue keeps this.

28 Sep a tool description was rewritten ip_summary
28 Sep a tool changed the parameters it asks for ip_summary
25 Sep a tool appeared ip_summary
25 Sep a tool changed version

Nothing serious here today

Today is the operative word: we check IP.LS — IP Lookup Service every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

run in your terminal
claude mcp add ipls-ip-lookup-service --transport http https://ip.ls/mcp
Settings → Connectors → Add custom connector, then paste this address
https://ip.ls/mcp
~/.codex/config.toml
[mcp_servers.ipls-ip-lookup-service]
url = "https://ip.ls/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "ipls-ip-lookup-service": {
      "url": "https://ip.ls/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "ipls-ip-lookup-service": {
      "type": "http",
      "url": "https://ip.ls/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

headers
headers
Return all HTTP request headers as seen by the IP.LS server (including X-Real-IP / X-Forwarded-For injected by the frontend proxy). Useful for debugging proxies and client identity.
lookup
ip_lookup
Look up geolocation, ISP and network info for any IPv4/IPv6 address or hostname, or an array of them for batch lookup. Returns ip, city, region, country, coordinates, ASN/ISP, timezone and continent (full name, e.g. North America); when a domain is queried, an extra `domain` field echoes it. Data source: DB-IP Lite (CC BY 4.0). Anycast IPs are approximate.
resolved
ip_resolved
Resolve a domain to all its A and AAAA records (deduplicated, up to 6) and return geolocation for each address. Returns an array of { ip, protocol, domain, city, region, country, coordinates, ASN/ISP, ... }. For a bare IP, returns a single-element array.
self
ip_self
Get geolocation and network info about the caller's own public IP, plus the protocol stack (IPv4/IPv6) of the current connection. On dual-stack machines the stack is chosen by the client and may differ from `curl ip.ls`, which picks a random stack; use curl -4/-6 locally to get the other stack, or — for clients that cannot pick a stack (browser, PowerShell, most HTTP libraries) — the single-stack hostnames https://4.ip.ls / https://6.ip.ls (DNS selects the stack; an unreachable 6.ip.ls means no usable IPv6). Data comes from a server-side GeoIP lookup on the caller's real IP.
summary
ip_summary
Summarize a large batch of IPs into distributions by country, continent, ASN/operator and network prefix, each bucket with a sample of addresses. Use instead of ip_lookup once the input is in the hundreds or thousands — ip_lookup returns every row, which no context window holds. Up to 5000 addresses or 100 hostnames. Counts are per occurrence; nothing is dropped silently (failed → `errors`, no database record → `no_data`, unlisted buckets → `tail`), the same input set always returns the same numbers, and the result is facts only — no datacenter/residential classification, no verdict. DB-IP Lite (CC BY 4.0).
ua
ua
Return the User-Agent string of the current HTTP client.

Endpoints

URLTransportStateLatencyChecked
https://ip.ls/mcp streamable-http answering 520 ms 6 min ago

Alternatives to IP.LS — IP Lookup Service

same job, measured the same way
Ipdata MCP
by mrfentmen

ipdata.co IP intelligence: geolocation, ASN, company, threat and timezone lookups.

88 installs/wk local only
Ip2location Geolocation
by mcparmory

Look up IP address location and geolocation data with country, city, timezone, and ISP details

217 installs/wk local only
IP Geolocation MCP by UnClick
by malamutemayhem

IP address geolocation and batch lookup with country, city, region, ISP, and timezone. By UnClick.

46 installs/wk local only
GeoIP
by olsols4

IP geolocation: country, continent, ASN and ISP lookup

answering
Geolocate Me
by guleki

Give any AI assistant real-time access to your phone's GPS and location history.

answering
wwhois.ru domain tools
by wwhois

WHOIS/RDAP lookup, IP geolocation and Punycode conversion. 1400+ TLDs incl. IDN. No API key.

3 tools answering
Location and Timezone MCP Server by RoxyAPI
by roxyapi

City geocoding and timezone resolution for birth data, for AI agents, one API key.

3 tools answering
Geolocation DB MCP
by mrfentmen

Geolocation for an IP address from Geolocation DB. No key required.

60 installs/wk local only

IP.LS — IP Lookup Service — questions

Answers built from our own checks of this server.

What can IP.LS — IP Lookup Service do?
It exposes 6 tools, read directly from the server on our last check. Among them: headers, ip_lookup, ip_resolved, ip_self, ip_summary, ua. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is IP.LS — IP Lookup Service working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 672 ms. The bar chart above shows every period we have measured.
How do I connect IP.LS — IP Lookup Service?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does IP.LS — IP Lookup Service need an API key?
No. IP.LS — IP Lookup Service completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is IP.LS — IP Lookup Service?
It answers our handshake in 672 ms on average, which is faster than 14% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.