Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

IP-DB IP Reputation

REMOTE · IP-DB.COM

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

Available components

74 Trust /100

Last scanned (23 hours ago)

Scores higher than 61% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 categories)

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. 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. 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
Schema Quality & AI Usability74
  • AI-judged instruction clarity (excellent).Pass
  • 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. 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 20 Nov 26 +45
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • TLS certificate: unverified → pass ▲ security
    • HSTS header: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • First check of Judged manipulation: pass security
    • Tool coverage: unverified → 100 ▲ functional
    • 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 functional
  • 19 Nov 26 −7

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

  • 17 Nov 26 0
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • 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. security
    • 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. functional
  • 16 Nov 26 35

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://ip-db.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=ip-db.com CN=YE1,O=Let's Encrypt,C=US 19 Nov 2026 17 Feb 2027 ECDSA 256 ECDSA-SHA384 6ae66fdf3956de61db347ff628361a8afdf
SANs: ip-db.com, www.ip-db.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of ip-db.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
ip-db.com. No DS 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=31536000
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), camera=(), microphone=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ip-db.com/mcp Verified 200
http (plaintext) http://ip-db.com/mcp HTTPS enforced 301 https://ip-db.com/mcp
MCP tools · 3 exposed · ~332 tokens

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 →

Tool Tokens
check_blacklists ~101

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.

NameTypeReqDescription
ipstringyesIPv4 or IPv6 address, or a hostname to resolve first (e.g. 185.220.101.1, mail.example.com)

No output schema declared.

No examples provided.

check_ip ~124

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).

NameTypeReqDescription
ipstringyesIPv4 or IPv6 address, or a hostname to resolve first (e.g. 185.220.101.1, mail.example.com)

No output schema declared.

No examples provided.

domain_whois ~107

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.

NameTypeReqDescription
domainstringyesA registered domain name, e.g. example.com or ornek.com.tr

No output schema declared.

No examples provided.

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.

remote · ip-db.com

# add to Claude Code
claude mcp add --transport http com-ip-db-ip-reputation 'https://ip-db.com/mcp'
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.