# IP.LS — IP Lookup Service (remote · ip.ls)

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

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `ip.ls`: 66/100 (this document), [markdown](https://verifymcp.io/servers/ls-ip-ipls-ip-lookup-service/ip.md), [page](https://verifymcp.io/servers/ls-ip-ipls-ip-lookup-service/ip)

## Channel facts

- Endpoint: `https://ip.ls/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.4.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-29.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 45/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 743 tokens (~92/item across 8 items; 6 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http ls-ip-ipls-ip-lookup-service 'https://ip.ls/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ls-ip-ipls-ip-lookup-service": {
      "url": "https://ip.ls/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ls-ip-ipls-ip-lookup-service": {
      "type": "http",
      "url": "https://ip.ls/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ls-ip-ipls-ip-lookup-service]
url = "https://ip.ls/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ls-ip-ipls-ip-lookup-service": {
      "type": "remote",
      "url": "https://ip.ls/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ls-ip-ipls-ip-lookup-service --url 'https://ip.ls/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ls-ip-ipls-ip-lookup-service:
    url: "https://ip.ls/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ls-ip-ipls-ip-lookup-service": {
      "Transport": "http",
      "Url": "https://ip.ls/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ls-ip-ipls-ip-lookup-service -t streamable-http -u 'https://ip.ls/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-29 (score 66, 0)

- [security] Tool “ip_summary” rewrote its description, which is the text the model reads
- [functional regression] Tool coverage: 100% → 86%
- [functional improvement] Schema quality: fail → pass
- [cosmetic] “ip_summary” reworded the description of “ips”
- [cosmetic] “ip_summary” reworded the description of “prefix6”
- [cosmetic] “ip_summary” reworded the description of “top”

### 2026-09-28 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 66, +1)

- [functional improvement] Schema quality: 127 → 113
- [functional] New resource “analyzing-web-logs-with-ipls/SKILL.md”

### 2026-09-25 (score 65, +1)

- [functional regression] Schema quality: pass → fail
- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server
- [functional] Server version: 1.3.0 → 1.4.0
- [functional] New tool “ip_summary”

### 2026-09-24 (score 64, +7)

- [security improvement] Authorization: unverified → partial
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] 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

### 2026-09-23 (score 57)

First indexed and scored.

## MCP tools (6)

### `ip_lookup` (~162 tokens)

IP / domain geolocation 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.

Input parameters:

- `ip` (string|array, required): 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"].

### `ip_resolved` (~97 tokens)

Resolve a domain to its IPs, with geolocation

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.

Input parameters:

- `host` (string, required): Domain or IP address to resolve, e.g. example.com or baidu.com

### `ip_self` (~151 tokens)

Look up my own public IP

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.

### `headers` (~47 tokens)

Show request headers as the server sees them

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.

### `ua` (~18 tokens)

Show the caller's User-Agent

Return the User-Agent string of the current HTTP client.

### `ip_summary` (~204 tokens)

Summarize a batch of IPs (country / continent / ASN / network)

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).

Input parameters:

- `ips` (required)
- `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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ls-ip-ipls-ip-lookup-service/ip#diagnostics

## Score history

- 2026-09-29: 66
- 2026-09-28: 66
- 2026-09-27: 66
- 2026-09-26: 65
- 2026-09-25: 65
- 2026-09-24: 64
- 2026-09-23: 57

## Common questions

### 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.

## Links

- Remote endpoint: https://ip.ls/mcp
- Changelog RSS feed: https://verifymcp.io/servers/ls-ip-ipls-ip-lookup-service/ip.xml
- Changelog JSON feed: https://verifymcp.io/servers/ls-ip-ipls-ip-lookup-service/ip.json
- HTML version of this page: https://verifymcp.io/servers/ls-ip-ipls-ip-lookup-service/ip