Zovo IP Lookup
REMOTE · IP-LOOKUP.ZOVO.ONE
Who owns an IP address?
Available components
Last scanned (1 hour ago)
Scores higher than 66% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Security
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 Security80
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
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.
- 23 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 22 Oct 26 74
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 23 Oct 2026 · Probed https://ip-lookup.zovo.one/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 17 Oct 2026 | 15 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 11d6383b6229e7430efb89196807b18d |
| SANs: zovo.one, ip-lookup.zovo.one, *.ip-lookup.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ip-lookup.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | 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=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ip-lookup.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://ip-lookup.zovo.one/mcp | HTTPS enforced | 301 | https://ip-lookup.zovo.one/mcp |
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 →
lookup_ip Look up IP address owners ~238
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ips | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| addresses | array | yes | – |
| columns | array | yes | – |
| count | number | yes | – |
| downloads | object | yes | – |
| error_count | number | yes | – |
| notes | string | yes | – |
| preview_limit | number | yes | – |
| preview_note | string | yes | – |
| public_count | number | yes | – |
| sources | array | yes | – |
No examples provided.
reverse_dns_lookup Reverse DNS lookup ~202
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).
| Name | Type | Req | Description |
|---|---|---|---|
| ips | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| downloads | object | yes | – |
| found_count | number | yes | – |
| notes | string | yes | – |
| preview_limit | number | yes | – |
| preview_note | string | yes | – |
| records | array | yes | – |
| sources | array | yes | – |
No examples provided.
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.
remote · ip-lookup.zovo.one
claude mcp add --transport http theluckystrike-ip-lookup 'https://ip-lookup.zovo.one/mcp'
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.