IP.LS — IP Lookup Service
REMOTE · IP.LS · SCANNED SEP 29
Keyless IP geolocation, ASN/ISP, timezone and DNS records for any IP or domain, plus your own IP.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability45
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 743 tokens (~92/item across 8 items; 6 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the IP.LS — IP Lookup Service MCP server?
IP.LS — IP Lookup Service is a hosted endpoint at https://ip.ls/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ip.ls
claude mcp add --transport http ls-ip-ipls-ip-lookup-service 'https://ip.ls/mcp'
{
"mcpServers": {
"ls-ip-ipls-ip-lookup-service": {
"url": "https://ip.ls/mcp"
}
}
} {
"servers": {
"ls-ip-ipls-ip-lookup-service": {
"type": "http",
"url": "https://ip.ls/mcp"
}
}
} [mcp_servers.ls-ip-ipls-ip-lookup-service] url = "https://ip.ls/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ls-ip-ipls-ip-lookup-service": {
"type": "remote",
"url": "https://ip.ls/mcp",
"enabled": true
}
}
} openclaw mcp add ls-ip-ipls-ip-lookup-service --url 'https://ip.ls/mcp' --transport streamable-http
mcp_servers:
ls-ip-ipls-ip-lookup-service:
url: "https://ip.ls/mcp" {
"McpServers": {
"ls-ip-ipls-ip-lookup-service": {
"Transport": "http",
"Url": "https://ip.ls/mcp"
}
}
} assistant mcp add ls-ip-ipls-ip-lookup-service -t streamable-http -u 'https://ip.ls/mcp'
{
"mcpServers": {
"ls-ip-ipls-ip-lookup-service": {
"type": "http",
"url": "https://ip.ls/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Sept 26 0
- Tool “ip_summary” rewrote its description, which is the text the model reads security
- Tool coverage: 100% → 86% ▼ functional
- Schema quality: fail → pass ▲ functional
- “ip_summary” reworded the description of “ips” cosmetic
- “ip_summary” reworded the description of “prefix6” cosmetic
- “ip_summary” reworded the description of “top” cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
- Schema quality: 127 → 113 ▲ functional
- New resource “analyzing-web-logs-with-ipls/SKILL.md” functional
- 25 Sept 26 +1
- Schema quality: pass → fail ▼ functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- Server version: 1.3.0 → 1.4.0 functional
- New tool “ip_summary” functional
- 24 Sept 26 +7
- Authorization: unverified → partial ▲ security
- Stability: unverified → 0.03 ▲ functional
- Tool “headers” changed its title: Show request headers as the server sees them cosmetic
- Tool “ip_lookup” changed its title: IP / domain geolocation lookup cosmetic
- Tool “ip_resolved” changed its title: Resolve a domain to its IPs, with geolocation cosmetic
- Tool “ip_self” changed its title: Look up my own public IP cosmetic
- Tool “ua” changed its title: Show the caller's User-Agent cosmetic
- 23 Sept 26 57
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 29 Sept 2026 · Probed https://ip.ls/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ip.ls | CN=YE1,O=Let's Encrypt,C=US | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 58571c06a45134e4d28b9586425cf45b4b3 |
| SANs: ip.ls | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ip.ls. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ls. | present | 724, 724 | 8, 8 | Verified |
| ip.ls. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ip.ls/mcp | Verified | 200 | |
| http (plaintext) | http://ip.ls/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
headers Show request headers as the server sees them ~47
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ip_lookup IP / domain geolocation lookup ~162
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string|array | yes | IPv4/IPv6 address or hostname, e.g. 8.8.8.8 or example.com. Pass an array for batch lookup, e.g. ["8.8.8.8", "1.1.1.1"]. |
No output schema declared.
No examples provided.
ip_resolved Resolve a domain to its IPs, with geolocation ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Domain or IP address to resolve, e.g. example.com or baidu.com |
No output schema declared.
No examples provided.
ip_self Look up my own public IP ~151
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ip_summary Summarize a batch of IPs (country / continent / ASN / network) ~204
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).
| Name | Type | Req | Description |
|---|---|---|---|
| ips | – | yes | – |
| prefix4 | integer | – | IPv4 grouping prefix. |
| prefix6 | integer | – | IPv6 grouping prefix; /48 = one end-site. |
| sample | integer | – | Sample addresses per bucket. |
| top | integer | – | Buckets per dimension. |
No output schema declared.
No examples provided.
ua Show the caller's User-Agent ~18
Return the User-Agent string of the current HTTP client.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the IP.LS — IP Lookup Service MCP server?
IP.LS — IP Lookup Service is an MCP server listed in the public MCP registry as ls.ip/ipls-ip-lookup-service. Keyless IP geolocation, ASN/ISP, timezone and DNS records for any IP or domain, plus your own IP. This page covers its hosted endpoint (https://ip.ls/mcp).
Is the IP.LS — IP Lookup Service MCP server safe to use?
IP.LS — IP Lookup Service scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the IP.LS — IP Lookup Service MCP server expose?
IP.LS — IP Lookup Service exposes 6 tools: ip_lookup, ip_resolved, ip_self, headers, ua, ip_summary. Their descriptions and schemas cost roughly 679 tokens of context every time the server is loaded.
Does the IP.LS — IP Lookup Service MCP server require authentication?
No. We connected to IP.LS — IP Lookup Service without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the IP.LS — IP Lookup Service MCP server still maintained?
IP.LS — IP Lookup Service is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.