# IP99 IP risk & geolocation (remote · ip99.com)

Free IP risk and geolocation lookup: proxy, VPN and datacenter detection. No API key.

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-26

## Components

- remote · `ip99.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-ip99-ip99/ip99.md), [page](https://verifymcp.io/servers/com-ip99-ip99/ip99)

## Channel facts

- Endpoint: `https://ip99.com/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-09-26.

- **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**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 272 tokens (~272/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### How do I install the IP99 IP risk & geolocation MCP server?

IP99 IP risk & geolocation is a hosted endpoint at https://ip99.com/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 com-ip99-ip99 'https://ip99.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-ip99-ip99": {
      "url": "https://ip99.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-ip99-ip99": {
      "type": "http",
      "url": "https://ip99.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-ip99-ip99]
url = "https://ip99.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-ip99-ip99": {
      "type": "remote",
      "url": "https://ip99.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-ip99-ip99 --url 'https://ip99.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-ip99-ip99:
    url: "https://ip99.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-ip99-ip99": {
      "Transport": "http",
      "Url": "https://ip99.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-ip99-ip99 -t streamable-http -u 'https://ip99.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-ip99-ip99": {
      "type": "http",
      "url": "https://ip99.com/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-25 (score 74, +1)

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

### 2026-09-23 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 69, +1)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-09-13 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 67, −1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “ip_risk_lookup” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 203 → 286

## MCP tools (1)

### `ip_risk_lookup` (~173 tokens)

IP risk & geolocation lookup

Look up the risk profile and geolocation of an IPv4 or IPv6 address. Returns a 0-100 risk score measuring the freshness and strength of verifiable risk evidence (proxy, VPN, dial-up pool, cloud phone, datacenter), the evidence state, network (ASN, usage type) and geographic attribution. The score is NOT a probability that the address is an attacker. Free tier: 1000 lookups per day per client IP and 60 per minute; higher limits with an API key sent as the X-API-Key header (https://ip99.com/en/pricing).

Input parameters:

- `ip` (string, required): The IPv4 or IPv6 address to look up, e.g. 8.8.8.8 or 2001:4860:4860::8888.

## Diagnostics

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

## Score history

- 2026-09-26: 74
- 2026-09-25: 74
- 2026-09-24: 73
- 2026-09-23: 73
- 2026-09-22: 72
- 2026-09-21: 72
- 2026-09-20: 71
- 2026-09-19: 71
- 2026-09-18: 70
- 2026-09-17: 70
- 2026-09-16: 69
- 2026-09-15: 69
- 2026-09-14: 68
- 2026-09-13: 68
- 2026-09-12: 67
- 2026-09-11: 68
- 2026-09-10: 68

## Common questions

### What is the IP99 IP risk & geolocation MCP server?

IP99 IP risk & geolocation is an MCP server listed in the public MCP registry as com.ip99/ip99. Free IP risk and geolocation lookup: proxy, VPN and datacenter detection. No API key. This page covers its hosted endpoint (https://ip99.com/mcp).

### Is the IP99 IP risk & geolocation MCP server safe to use?

IP99 IP risk & geolocation 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 IP99 IP risk & geolocation MCP server expose?

IP99 IP risk & geolocation exposes 1 tool: ip_risk_lookup. Their descriptions and schemas cost roughly 173 tokens of context every time the server is loaded.

### Does the IP99 IP risk & geolocation MCP server require authentication?

No. We connected to IP99 IP risk & geolocation without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the IP99 IP risk & geolocation MCP server still maintained?

IP99 IP risk & geolocation is still listed as active in the MCP registry. We last reached this channel on 26 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://ip99.com/mcp
- Website: https://ip99.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-ip99-ip99/ip99.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-ip99-ip99/ip99.json
- HTML version of this page: https://verifymcp.io/servers/com-ip99-ip99/ip99