# IP-DB IP Reputation (remote · ip-db.com)

Free abuse IP check: reputation score, threat-feed blacklist matches, Tor/VPN flags, domain WHOIS.

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

## Components

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

## Channel facts

- Endpoint: `https://ip-db.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

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

- **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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 458 tokens (~152/item across 3 items; 3 tools + 0 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 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.

## Install

### How do I install the IP-DB IP Reputation MCP server?

IP-DB IP Reputation is a hosted endpoint at https://ip-db.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-ip-db-ip-reputation 'https://ip-db.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-ip-db-ip-reputation": {
      "url": "https://ip-db.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-ip-db-ip-reputation]
url = "https://ip-db.com/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-ip-db-ip-reputation:
    url: "https://ip-db.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

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

- [functional improvement] Stability: unverified → 0.03

### 2026-11-20 (score 73, +45)

- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security improvement] HSTS header: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100

### 2026-11-19 (score 28, −7)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-11-17 (score 35, 0)

- [security regression] TLS certificate: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Transport: pass → fail
- [security] Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional] Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- [functional] Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities.
- [functional] Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.

### 2026-11-16 (score 35)

First indexed and scored.

## MCP tools (3)

### `domain_whois` (~107 tokens)

Domain WHOIS lookup

WHOIS/RDAP record of a domain from whois.ip-db.com: registrar, creation date (domain age), expiry date, status codes, nameservers, the hosting IPs with their ip-db.com reputation, subdomain count and a short security assessment (SPF, DMARC, TLS, transfer lock). Works for .com.tr and the other .tr domains.

Input parameters:

- `domain` (string, required): A registered domain name, e.g. example.com or ornek.com.tr

### `check_ip` (~124 tokens)

Check IP reputation

Reputation of one IP address from IP-DB: 0-100 abuse confidence score and label, network type (residential, datacenter/hosting, vpn, tor), the threat-intelligence blocklists and DNSBLs that list it, community abuse reports, country, ASN and owner, the network's abuse contact, and a fraud-screening recommendation (allow, review, challenge, block).

Input parameters:

- `ip` (string, required): IPv4 or IPv6 address, or a hostname to resolve first (e.g. 185.220.101.1, mail.example.com)

### `check_blacklists` (~101 tokens)

Check IP blacklists

Check one IP address against every threat-intelligence blocklist IP-DB carries plus live DNSBL/RBL spam blacklists (SpamCop, Barracuda, PSBL, UCEPROTECT, Mailspike and more). Returns which lists carry it and which do not.

Input parameters:

- `ip` (string, required): IPv4 or IPv6 address, or a hostname to resolve first (e.g. 185.220.101.1, mail.example.com)

## Diagnostics

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

## Score history

- 2026-11-21: 74
- 2026-11-20: 73
- 2026-11-19: 28
- 2026-11-18: 35
- 2026-11-17: 35
- 2026-11-16: 35

## Common questions

### What is the IP-DB IP Reputation MCP server?

IP-DB IP Reputation is an MCP server listed in the public MCP registry as com.ip-db/ip-reputation. Free abuse IP check: reputation score, threat-feed blacklist matches, Tor/VPN flags, domain WHOIS. This page covers its hosted endpoint (https://ip-db.com/mcp).

### Is the IP-DB IP Reputation MCP server safe to use?

IP-DB IP Reputation 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 IP-DB IP Reputation MCP server expose?

IP-DB IP Reputation exposes 3 tools: domain_whois, check_ip, check_blacklists. Their descriptions and schemas cost roughly 332 tokens of context every time the server is loaded.

### Does the IP-DB IP Reputation MCP server require authentication?

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

### Is the IP-DB IP Reputation MCP server still maintained?

IP-DB IP Reputation is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the IP-DB IP Reputation MCP server?

VerifyMCP ran 13 checks on IP-DB IP Reputation, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://ip-db.com/mcp
- Website: https://ip-db.com/en/api-docs
- Changelog RSS feed: https://verifymcp.io/servers/com-ip-db-ip-reputation/ip-db.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-ip-db-ip-reputation/ip-db/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-ip-db-ip-reputation/ip-db.json
- HTML version of this page: https://verifymcp.io/servers/com-ip-db-ip-reputation/ip-db
