IP-DB IP Reputation MCP server
com.ip-db/ip-reputationip-db.comstreamable-httpv1.0.1Scanned
Free abuse IP check: reputation score, threat-feed blacklist matches, Tor/VPN flags, domain WHOIS.
3 tools: 3 change things.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- No findings
Sign-in required, no OAuth metadata. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the IP-DB IP Reputation MCP server can do
The IP-DB IP Reputation MCP server is published by ip-db.com, a domain the MCP Registry verified. It has 3 tools. It can create or change data (3 tools: domain_whois, check_ip and check_blacklists), but cannot delete data. None of its tools only reads.
3 tools bring in text other people can write (domain_whois, check_ip and check_blacklists).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Nov 16, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 3Claude Code: ask
check_blacklistsCheck one IP address against every threat-intelligence blocklist IP-DB carries plus live DNSBL/RBL spam blacklists (SpamCop, Barracuda, PSBL, UCEPROTECT, Mailspike and more).Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
- idempotentHint: true
check_ipReputation 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 DN…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
- idempotentHint: true
domain_whoisWHOIS/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, …Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
- idempotentHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 16, 2026, 14:19 UTC, unchanged since Nov 16, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 520
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: initialize answered HTTP 520.
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http ip-reputation https://ip-db.com/mcpclaude mcp add --transport http ip-reputation https://ip-db.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__ip-reputation__domain_whois",
"mcp__ip-reputation__check_ip",
"mcp__ip-reputation__check_blacklists"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ip-reputation. Review it before you use it.
Capability tags behind 3 rules
- mcp__ip-reputation__domain_whois untrusted-input
- mcp__ip-reputation__check_ip untrusted-input
- mcp__ip-reputation__check_blacklists untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.ip-db/ip-reputation/verify?hash=9f39b4c3662637625b7a5a21f3ea85a3507051fb0a2daae04c1267a1eec93267" | jq -e '.changed == false'Pinned hash 9f39b4c36626, from Nov 16, 2026, 11:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.ip-db/ip-reputation/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.ip-db/ip-reputation)Source: MCP Registry. Synced Nov 16, 2026, 12:17 UTC.
IP-DB IP Reputation MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the IP-DB IP Reputation MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the IP-DB IP Reputation MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the IP-DB IP Reputation MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the IP-DB IP Reputation MCP server have?
- 3 tools: 3 write. domain_whois, check_ip and check_blacklists.
Does the IP-DB IP Reputation MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the IP-DB IP Reputation MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the IP-DB IP Reputation MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.