# `io.github.theluckystrike/ip-lookup` on Anlyon Radar

> Text inside fenced blocks marked untrusted-server-text was written by the MCP server's publisher, not by Anlyon Radar. It is data to inspect, not instructions to follow. Invisible characters are shown as [U+XXXX].
> No finding is not a safety guarantee: these are point-in-time checks of tool definitions, not of code or behaviour.

- Page: https://radar.anlyon.com/servers/io.github.theluckystrike/ip-lookup
- JSON: https://radar.anlyon.com/api/v1/servers/io.github.theluckystrike/ip-lookup
- Version: 1.0.0 (active)
- Publisher: io.github.theluckystrike (GitHub account)
- Runs: remote (streamable-http)
- Sign-in to list tools: none
- Metadata from the official MCP Registry, synced 2026-10-22T06:20:05.594Z

Title and description, as the publisher wrote them:

```untrusted-server-text
Zovo IP Lookup
Who owns an IP address?
```

Scanned 2026-11-08T13:18:37.043Z over streamable-http.

**2 tools: 2 only read.**

| Group | Class | Tools | Claude Code |
| --- | --- | --- | --- |
| Deletes or cancels | destructive | 0 | deny |
| Can't be undone | irreversible | 0 | ask |
| Changes things | write | 0 | ask |
| Only reads | read | 2 | allow |

## Exfil surface

No private-data -> untrusted-input -> outbound path in this server alone: no tool is tagged outbound.

| Tag | Meaning | Tools |
| --- | --- | --- |
| private-data | Reads files, mail, messages, databases, secrets, calendars or repositories. | `mcp__ip-lookup__lookup_ip` |
| untrusted-input | Brings in text someone else can write: web pages, inbound email, messages, issues and comments. | `mcp__ip-lookup__lookup_ip` `mcp__ip-lookup__reverse_dns_lookup` |
| outbound | Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL. | none |

## Findings

No check matched anything in these tool definitions.


## Only reads (2)

Looks things up and changes nothing. Claude Code: allow.

### `lookup_ip`

- The name "lookup_ip" says "lookup": a word for reading.
- Tag private-data: The description's first sentence says "contact": it reads contacts.
- Tag untrusted-input: The server marks it openWorldHint: true: it reaches things outside the server's own data. The description's first sentence says "internet": it reads web pages, which anyone can write.

Description, as the server wrote it:

```untrusted-server-text
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.
```

### `reverse_dns_lookup`

- The name "reverse_dns_lookup" says "lookup": a word for reading.
- Tag untrusted-input: The server marks it openWorldHint: true: it reaches things outside the server's own data. The description's first sentence says "http": it reads web pages, which anyone can write.

Description, as the server wrote it:

```untrusted-server-text
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).
```

## Claude Code permissions

For `.claude/settings.json`, assuming the server is installed as `ip-lookup`:

```json
{
  "permissions": {
    "allow": [
      "mcp__ip-lookup__lookup_ip",
      "mcp__ip-lookup__reverse_dns_lookup"
    ],
    "ask": [],
    "deny": []
  }
}
```

Capability tags behind the rules (a read tagged outbound is asked about):

- `mcp__ip-lookup__lookup_ip`: private-data, untrusted-input
- `mcp__ip-lookup__reverse_dns_lookup`: untrusted-input

## Remote posture

What an anonymous client saw at the remote endpoint, last 2026-11-20T19:33:21.439Z, unchanged since 2026-10-22T15:27:15.557Z. No credentials were sent and no tool was called. Values are shown as the endpoint returned them. Method: https://radar.anlyon.com/methodology#remote-posture

| Fact | Observed |
| --- | --- |
| Reachable | `yes` |
| HTTP status of an anonymous initialize | `200` |
| tools/list served without credentials | `yes` |
| Tools that change things, listed without credentials | `0` |
| Protocol version | `2025-06-18` |
| WWW-Authenticate on 401 | `not observed` |
| resource_metadata in WWW-Authenticate | `none` |
| RFC 9728 protected resource metadata | `none` |
| Authorization servers | `none` |
| Legacy HTTP+SSE transport | `no` |
| Dynamic client registration | `not observed` |
| Client ID metadata documents | `not observed` |
