# Zovo IP Lookup (remote · ip-lookup.zovo.one)

Who owns an IP address?

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `ip-lookup.zovo.one`: 74/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-ip-lookup/ip-lookup.md), [page](https://verifymcp.io/servers/theluckystrike-ip-lookup/ip-lookup)

## Channel facts

- Endpoint: `https://ip-lookup.zovo.one/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-10-23.

- **Endpoint Security**: 80/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 is enforced; there's no plaintext access path.
  - 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**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 563 tokens (~187/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Zovo IP Lookup MCP server?

Zovo IP Lookup is a hosted endpoint at https://ip-lookup.zovo.one/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 theluckystrike-ip-lookup 'https://ip-lookup.zovo.one/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-ip-lookup": {
      "url": "https://ip-lookup.zovo.one/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-ip-lookup": {
      "type": "http",
      "url": "https://ip-lookup.zovo.one/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-ip-lookup]
url = "https://ip-lookup.zovo.one/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add theluckystrike-ip-lookup --url 'https://ip-lookup.zovo.one/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-ip-lookup:
    url: "https://ip-lookup.zovo.one/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-ip-lookup": {
      "Transport": "http",
      "Url": "https://ip-lookup.zovo.one/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-ip-lookup -t streamable-http -u 'https://ip-lookup.zovo.one/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-ip-lookup": {
      "type": "http",
      "url": "https://ip-lookup.zovo.one/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-10-23 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-22 (score 74)

First indexed and scored.

## MCP tools (2)

### `lookup_ip` (~238 tokens)

Look up IP address owners

Use this when the user wants an ip lookup, asks who owns this ip, needs the ip address owner or the whois ip details, wants the ip abuse contact, or needs an ip range lookup: it reads the five regional internet registries through RDAP and the reverse DNS (PTR) name, for one to twenty IPv4 or IPv6 addresses or CIDR ranges, and returns a CSV download for the batch. Limits: registry data shows the network holder and its country, not a street address or a person's location; some registries publish no abuse email; reverse DNS exists only when the network sets it. Do not use for an ip locator that claims a precise location, for looking up a domain name (that is a domain lookup), or for scanning a host.

Input parameters:

- `ips` (string, required): One to twenty IPv4 or IPv6 addresses or CIDR ranges, separated by commas, spaces, or new lines. Example: 8.8.8.8, 1.1.1.1, 2606:4700:4700::1111, 192.168.1.1/24.

Output parameters:

- `addresses` (array)
- `columns` (array)
- `count` (number)
- `downloads` (object)
- `error_count` (number)
- `notes` (string)
- `preview_limit` (number)
- `preview_note` (string)
- `public_count` (number)
- `sources` (array)

### `reverse_dns_lookup` (~202 tokens)

Reverse DNS lookup

Use this when the user wants a reverse dns lookup, an ip address lookup for PTR names, or a quick ip lookup of hostnames: it queries DNS-over-HTTPS for the in-addr.arpa or ip6.arpa name of one to twenty public IPv4 or IPv6 addresses and returns host names with a CSV download, without reading a registry. Limits: a PTR name exists only when the network operator sets it; private, loopback, link-local, shared, multicast, documentation and reserved addresses are not queried. Do not use when the user wants the owner, the registration dates or the abuse contact of an address (use lookup_ip for that).

Input parameters:

- `ips` (string, required): One to twenty public IPv4 or IPv6 addresses, separated by commas, spaces, or new lines. Example: 8.8.8.8, 1.1.1.1, 2606:4700:4700::1111.

Output parameters:

- `count` (number)
- `downloads` (object)
- `found_count` (number)
- `notes` (string)
- `preview_limit` (number)
- `preview_note` (string)
- `records` (array)
- `sources` (array)

## Diagnostics

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

## Score history

- 2026-10-23: 74
- 2026-10-22: 74

## Common questions

### What is the Zovo IP Lookup MCP server?

Zovo IP Lookup is an MCP server listed in the public MCP registry as io.github.theluckystrike/ip-lookup. Who owns an IP address? This page covers its hosted endpoint (https://ip-lookup.zovo.one/mcp).

### Is the Zovo IP Lookup MCP server safe to use?

Zovo IP Lookup scores 74 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 Zovo IP Lookup MCP server expose?

Zovo IP Lookup exposes 2 tools: lookup_ip, reverse_dns_lookup. Their descriptions and schemas cost roughly 440 tokens of context every time the server is loaded.

### Does the Zovo IP Lookup MCP server require authentication?

No. We connected to Zovo IP Lookup without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Zovo IP Lookup MCP server still maintained?

Zovo IP Lookup is still listed as active in the MCP registry. We last reached this channel on 23 October 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-lookup.zovo.one/mcp
- Website: https://ip-lookup.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-ip-lookup/ip-lookup.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-ip-lookup/ip-lookup.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-ip-lookup/ip-lookup