{ "data": { "a": { "slug": "abuseipdb", "name": "AbuseIPDB", "vendor": "AbuseIPDB LLC", "vendorUrl": "https://www.abuseipdb.com", "kind": "http-api", "category": "security-intelligence", "summary": "AbuseIPDB is a crowdsourced database of IP addresses reported for abuse, run by AbuseIPDB LLC under Marathon Studios. Its API v2 returns an abuse confidence score and report history for an address, a subnet or a blacklist, and takes reports.", "url": "https://www.anchorterminal.com/tools/abuseipdb", "markdownUrl": "https://www.anchorterminal.com/tools/abuseipdb.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/abuseipdb.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/abuseipdb.json", "dns": "abuseipdb.grade.anchorterminal.com", "repo": "https://github.com/AbuseIPDB/abuseipdb-mcp", "transports": [ "stdio" ], "packages": [ { "registry": "pypi", "name": "mcp-server-abuseipdb" } ], "auth": "api-key", "authNotes": "API key from the account page after a browser signup, sent in a `Key` header. The docs also accept the key as a lowercase `key` query or form parameter. No scopes were found. The official MCP server reads the key from `ABUSEIPDB_API_KEY` and is read-only.", "pricing": "freemium", "pricingNotes": "Free Individual plan with 1,000 checks and 1,000 reports a day, 100 block checks, a 10,000-address blacklist and no card. Basic $25 a month (10,000 checks a day) and Premium $99 a month (50,000 a day), each with a 30-day trial. Enterprise by contact. Free plans are for evaluation, contributing reports or non-commercial personal projects under the terms.", "priceSummary": "$25 / mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs, the pricing page or the MCP server repository (checked 2026-11-03). Plan limits exceeded on check-block return 402 Payment Required with a plain error, not payment requirements.", "endpoints": [] }, "toolCount": 2, "popularity": { "githubStars": 6, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://docs.abuseipdb.com/", "llmsTxt": "https://www.abuseipdb.com/llms.txt", "registryName": "io.github.abuseipdb/abuseipdb-mcp", "capabilities": [ "secintel.reputation", "secintel.indicators", "secintel.ip-enrichment" ], "tags": [ "hosted", "freemium", "no-card", "free-tier", "api-key", "mcp", "official", "mcp-registry", "stdio", "read-only-mode", "llms-txt", "sla", "status-page", "python", "closed-source" ], "lastRelease": "2026-08-02", "graded": true, "anchor": { "graded": true, "score": 55.7, "grade": "C", "agentReady": false, "rank": 765, "ranked": true, "rankOf": 1349, "categoryRank": 6, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 74, "maintenance": 38, "payments": 30, "reliability": 75, "schema": 59, "security": 37, "transparency": 63 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "A free key allows 1,000 IP checks a day with published per-endpoint limits, rate-limit headers and a 99 per cent SLA in the terms, and the official MCP server is read-only. One key covers reads, reports and deletes, the key may travel in a query string, there is no OpenAPI document, and the terms bar redistribution of results.", "bestFor": "An agent that needs a quick reputation verdict on an IP or subnet, or wants to report abuse from its own logs, with a free daily quota large enough for one incident.", "strengths": [ "1,000 checks and 1,000 reports a day on a free key with no card, and daily limits published for every endpoint and plan", "429 responses carry Retry-After and X-RateLimit headers, and errors follow the JSON API shape with a status and detail", "The terms include a service level agreement with a 99 per cent monthly availability target", "The first-party MCP server has two read-only tools annotated readOnlyHint and idempotentHint, with per-item errors in bulk checks", "llms.txt on abuseipdb.com describes the API, categories and reporting rules for agents" ], "weaknesses": [ "No OpenAPI document, no API changelog (the blog's last post is from December 2018) and the reports endpoint is marked open beta and may change without notice", "One key per account reaches reads, reports, bulk reports and clear-address deletes, and the docs accept it as a query parameter", "No security.txt, disclosure policy or certification found, and the status page's incident history could not be read", "The terms bar reproducing, copying or reselling any portion of the service and its data, and free plans exclude commercial use", "The privacy policy of 15 March 2023 gives no retention periods and marks every provider's GDPR status as in process" ], "agentNotes": [ "Send `Accept: application/json` and the key in the `Key` header; without the Accept header the API answers with an HTML page", "Act on `abuseConfidenceScore` rather than `isWhitelisted`, and pass `maxAgeInDays` to bound how old the reports can be (default 30, maximum 365)", "Watch `X-RateLimit-Remaining` per endpoint and on a 429 wait for `Retry-After`, which can be most of a day since limits reset at 00:00 UTC", "Use `check-block` for a subnet (up to /24 on the free plan) and `blacklist` with `confidenceMinimum` only on a paid plan; over-limit `limit` values are truncated silently", "Strip personal data from report comments, which are public, and prefer the read-only MCP server when the task never reports" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 55.7 } ], "editorialScores": { "ergonomics": 74, "maintenance": 38, "payments": 30, "reliability": 75, "schema": 59, "security": 37, "transparency": 42 }, "provenanceScore": 84, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "uvx mcp-server-abuseipdb", "http": "curl -G https://api.abuseipdb.com/api/v2/check --data-urlencode \"ipAddress=118.25.6.39\" -d maxAgeInDays=90 -H \"Key: $ABUSEIPDB_API_KEY\" -H \"Accept: application/json\"", "claudeCode": "claude mcp add abuseipdb -e ABUSEIPDB_API_KEY=YOUR_KEY -- uvx mcp-server-abuseipdb", "config": { "mcpServers": { "abuseipdb": { "args": [ "mcp-server-abuseipdb" ], "command": "uvx", "env": { "ABUSEIPDB_API_KEY": "${ABUSEIPDB_API_KEY}" } } } } }, "letme": { "capability": "https://letme.dev/secintel.reputation", "tool": "https://letme.dev/abuseipdb" }, "area": "developer", "unitPrices": [ { "item": "Basic, 10,000 checks a day", "unit": "month", "usd": 25, "note": "$228 a year" }, { "item": "Premium, 50,000 checks a day", "unit": "month", "usd": 99, "note": "$1,068 a year" } ], "provenance": { "legalEntity": "AbuseIPDB LLC", "domain": "abuseipdb.com", "domainRegistered": "2010-04-06", "endpointOnVendorDomain": true, "terms": "https://www.abuseipdb.com/legal", "privacy": "https://www.abuseipdb.com/privacy", "statusPage": "https://status.abuseipdb.com/", "changelog": "https://github.com/AbuseIPDB/abuseipdb-mcp/blob/main/CHANGELOG.md", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "The terms of use and privacy policy, both last updated 15 March 2023, name AbuseIPDB LLC, a Pennsylvania limited liability company, under Pennsylvania law with arbitration in Philadelphia. The about page says the project is managed by Marathon Studios Inc.", "Section 3 of the terms forbids accessing the website by automated means other than search engines that follow robots.txt and authorised API use. Public pages were read for this listing and the clause is recorded as a fact.", "www.abuseipdb.com/robots.txt disallows /account and /enterprise/ for all crawlers with a crawl delay of 2; neither path was fetched. docs.abuseipdb.com has no robots.txt.", "The changelog link is the MCP server's. No changelog for the REST API was found; the blog's newest post is dated 13 December 2018.", "status.abuseipdb.com is an UptimeRobot page linked from the footer. Its monitors and history load by script and answered with an error when read on 3 November 2026.", "www.abuseipdb.com/.well-known/security.txt returns 404. RDAP at Verisign gives a registration date of 6 April 2010." ], "score": 84 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/abuseipdb.json", "live": { "slug": "abuseipdb", "vendorStatus": { "page": "https://status.abuseipdb.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-04T21:25:08.27739387Z" }, "versions": [ { "registry": "pypi", "name": "mcp-server-abuseipdb", "version": "0.1.1", "released": "2026-08-03", "seenAt": "2026-11-04T19:54:02.081091414Z" } ], "githubStars": 6, "pypiWeekly": 38, "securityTxt": { "url": "https://abuseipdb.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:53:21.604779568Z" }, "updatedAt": "2026-11-04T21:25:08.27739387Z" } }, "answer": "WhoisXML API scores 56.8 (C) on agent readiness against AbuseIPDB's 55.7 (C), and leads in 3 of 7 scored categories. AbuseIPDB leads on reliability, agent ergonomics and payments \u0026 pricing.", "b": { "slug": "whoisxml-api", "name": "WhoisXML API", "vendor": "Whois API, Inc.", "vendorUrl": "https://www.whoisxmlapi.com", "kind": "http-api", "category": "security-intelligence", "summary": "WhoisXML API is a set of domain, DNS, IP and threat intelligence APIs from Whois API, Inc. Its WHOIS API returns parsed registration records for a domain or address, and a hosted MCP server bundles 35 tools on one balance.", "url": "https://www.anchorterminal.com/tools/whoisxml-api", "markdownUrl": "https://www.anchorterminal.com/tools/whoisxml-api.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/whoisxml-api.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/whoisxml-api.json", "dns": "whoisxml-api.grade.anchorterminal.com", "transports": [ "streamable-http", "stdio" ], "remoteUrl": "https://mcp-hosted.whoisxmlapi.com/mcp", "packages": [ { "registry": "npm", "name": "@whoisxmlapidotcom/mcp-whoisxmlapi" } ], "auth": "mixed", "authNotes": "API key from the account after a browser signup, sent as an `apiKey` query parameter (which takes priority) or as `Authorization: Bearer`, which also accepts a server-to-server OAuth token. An IP allowlist can be set (403 AUTHENTICATE_10). The hosted MCP server uses OAuth, taking the API key once in the connect flow; local installs take the key as an environment variable.", "pricing": "freemium", "pricingNotes": "500 free WHOIS API credits on signup with no card. A WHOIS lookup costs 1 credit, 5 with a forced real-time refresh. WXA.ONE universal credit pools, one balance across the APIs and the MCP server, start from $129 a month, monthly or yearly; per-credit rates sit behind a calculator and were not read. Enterprise packages and premium support by sales. Credits expire after 12 months and orders are non-refundable under the terms.", "priceSummary": "$129 / mo", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the WHOIS API docs, the pricing pages, the terms or the MCP server docs (checked 2026-11-03). An exhausted balance answers 401 AUTHENTICATE_05.", "endpoints": [] }, "toolCount": 35, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://whois.whoisxmlapi.com/documentation/making-requests", "llmsTxt": "https://www.whoisxmlapi.com/llms.txt", "registryName": "io.github.whois-api-llc/mcp-whoisxmlapi", "capabilities": [ "secintel.dns", "secintel.reputation", "secintel.ip-enrichment", "secintel.indicators" ], "tags": [ "hosted", "freemium", "no-card", "free-tier", "api-key", "oauth", "mcp", "remote-mcp", "official", "mcp-registry", "llms-txt", "status-page", "prepaid", "typescript", "python", "go", "docker", "closed-source" ], "lastRelease": "2026-11-03", "graded": true, "anchor": { "graded": true, "score": 56.8, "grade": "C", "agentReady": false, "rank": 731, "ranked": true, "rankOf": 1349, "categoryRank": 5, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 65, "maintenance": 76, "payments": 25, "reliability": 65, "schema": 70, "security": 39, "transparency": 60 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "500 free credits with no card, JSON Schema and XSD for every response, 429s with Retry-After, cache controls that set the price per lookup, and a 35-tool hosted MCP server with OAuth. Per-credit prices sit behind a calculator, the terms confine data to one site and forbid AI training on it, and the key is accepted in the query string.", "bestFor": "An agent investigating a domain's registration, history, DNS, certificates or related domains at scale, on a prepaid credit pool.", "strengths": [ "500 free WHOIS credits on signup with no card, and 1 credit a lookup from cache or 5 for a forced refresh", "JSON Schema and XSD documents for the record, availability and error responses, with an error code table and Retry-After on 429", "Each record carries audit.createdDate and audit.updatedDate, so an agent can tell when the copy was collected", "Official MCP server with 35 tools, hosted with OAuth, in the official MCP registry with 21 versions since May 2026", "llms.txt on whoisxmlapi.com lists the APIs, feeds and databases" ], "weaknesses": [ "Per-credit prices are not published outside a calculator; the only public figure is from $129 a month, and orders are non-refundable", "The terms license data for one site, bar sharing it with third parties and forbid AI model training on it without written authorisation", "The docs say 200 requests a second while the terms say 50, 20 concurrent and 5 concurrent bulk", "The key is accepted as a query parameter that overrides the header, no scopes were found, and security.txt returns 404", "The privacy policy was last modified on 6 April 2020, cites Privacy Shield, and names no processors, locations or retention periods", "No OpenAPI document, no API version, and the MCP server's source was not found" ], "agentNotes": [ "Send the key as `Authorization: Bearer` and `outputFormat=JSON`; the default output is XML and an `apiKey` query parameter overrides the header", "Leave the cache flags alone for 1 credit a lookup; `_hardRefresh=1` costs 5 credits, and `_dbOnly=1` returns WHOIS_03 when nothing is cached", "Read `audit.updatedDate` before trusting a record, and check `dataError` for MASKED_WHOIS_DATA or PARTIAL_DATA", "Watch `X-RateLimit-Remaining` and on 429 AUTHENTICATE_06 wait for `Retry-After`; a 401 AUTHENTICATE_05 means the balance is spent, so stop", "Keep results inside the customer's own systems; the terms forbid passing data to third parties or using it to train models" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 56.8 } ], "editorialScores": { "ergonomics": 65, "maintenance": 76, "payments": 25, "reliability": 65, "schema": 70, "security": 39, "transparency": 31 }, "provenanceScore": 89, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npx @whoisxmlapidotcom/mcp-whoisxmlapi --help", "http": "curl -H \"Authorization: Bearer $WHOISXML_API_KEY\" \"https://www.whoisxmlapi.com/whoisserver/WhoisService?domainName=example.com\u0026outputFormat=JSON\"", "claudeCode": "claude mcp add --transport http whoisxmlapi https://mcp-hosted.whoisxmlapi.com/mcp", "config": { "mcpServers": { "whoisxmlapi": { "url": "https://mcp-hosted.whoisxmlapi.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/secintel.dns", "tool": "https://letme.dev/whoisxml-api" }, "area": "developer", "unitPrices": [ { "item": "WXA.ONE universal credit pool, smallest plan", "unit": "month", "usd": 129, "note": "from $129 a month; credits included and per-credit rates were not read" } ], "provenance": { "legalEntity": "Whois API, Inc.", "domain": "whoisxmlapi.com", "domainRegistered": "2009-03-20", "endpointOnVendorDomain": true, "terms": "https://main.whoisxmlapi.com/terms-of-service", "privacy": "https://main.whoisxmlapi.com/privacy-policy", "statusPage": "https://main.whoisxmlapi.com/api-status", "changelog": "https://main.whoisxmlapi.com/press-release", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "The terms of service, last updated 3 March 2025 and effective 3 May 2025, name Whois API, Inc. under California law with AAA arbitration. The company page's copyright line reads 2010 to 2026 Whois API, Inc. No postal address was found on the terms, privacy policy or company page.", "The terms forbid unauthorised data mining and obtaining materials through means not intentionally made available, and set a rate limit of 50 requests a second. Public pages were read for this listing and the clauses are recorded as facts.", "whois.whoisxmlapi.com/robots.txt allows all paths for general crawlers and blocks five named bots. www.whoisxmlapi.com/robots.txt disallows blog admin paths and /BulkWhoisLookup/, none fetched. www.whoisxmlapi.com/terms-of-service redirects to a 404; the terms live at main.whoisxmlapi.com.", "The status page is the vendor's own Service Status and Data Releases page, which describes a JSON status file and feeds but lists no incidents.", "The changelog link is the press release page, whose newest product update is dated 9 May 2025. MCP server versions are dated in the official MCP registry.", "main.whoisxmlapi.com/.well-known/security.txt returns 404. RDAP at Verisign gives a registration date of 20 March 2009." ], "score": 89 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/whoisxml-api.json", "live": { "slug": "whoisxml-api", "probe": { "target": "https://mcp-hosted.whoisxmlapi.com/mcp", "method": "get", "lastAt": "2026-11-04T21:28:20.437933986Z", "lastOk": true, "lastStatus": 401, "lastMs": 391, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 413, "p95ms24h": 537, "samples24h": 62, "samples30d": 62, "days": [ { "date": "2026-11-04", "probes": 62, "ok": 62 } ] }, "vendorStatus": { "page": "https://main.whoisxmlapi.com/api-status", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-04T21:26:59.259669881Z" }, "versions": [ { "registry": "mcp-registry", "name": "io.github.whois-api-llc/mcp-whoisxmlapi", "version": "1.15.0", "seenAt": "2026-11-04T17:11:44.552009456Z" }, { "registry": "npm", "name": "@whoisxmlapidotcom/mcp-whoisxmlapi", "version": "1.15.0", "seenAt": "2026-11-04T21:06:02.286471255Z" } ], "npmWeekly": 1559, "securityTxt": { "url": "https://whoisxmlapi.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:53:49.350283946Z" }, "updatedAt": "2026-11-04T21:28:20.437933986Z" } }, "edges": [ { "by": 38, "category": "maintenance", "leads": "whoisxml-api", "name": "Maintenance \u0026 community", "reasons": { "a": "Read as a closed service with an official MCP server. The newest dated change to the surface is the MCP server's v0.1.1 on 2 August 2026, 93 days before the check; the API docs and blog carry no later date (10 of 30). One release in the last 90 days, v0.1.1 fell just outside it (0 of 20). Support is a contact form with no guaranteed response on the free plan, there is no public changelog for the API, and the MCP repository shows a pull request merged on 2 August but GitHub's issue pages could not be read (5 of 15). The MCP server sits in the official registry under io.github.abuseipdb (15). The MCP package has CI on Python 3.11 to 3.14 with ruff, pytest and a packaging check, and a locked dependency set (8 of 10). 10 + 0 + 5 + 15 + 8 = 38.", "b": "Read as a closed service with an official MCP server. MCP server 1.13.0 was published in the official registry on 3 November 2026 and the ProfessionalServices and ipgeo-community repositories were pushed the same day (30). 1.8.6 on 8 September through 1.13.0 on 3 November 2026 is nine registry versions in 90 days (20). Product updates are summarised in yearly press releases, the newest 9 May 2025, support is a contact form with tiered response times sold separately, and the client library repositories were last pushed in 2023 (8 of 15). The MCP server is in the official registry under io.github.whois-api-llc, and official Python and Go clients exist (15). The MCP server's source was not found on GitHub, and the SDK repositories show no activity since 2023 (3 of 10). 30 + 20 + 8 + 15 + 3 = 76." }, "scores": { "a": 38, "b": 76 } }, { "by": 11, "category": "schema", "leads": "whoisxml-api", "name": "Schema \u0026 documentation", "reasons": { "a": "The surface graded is the REST API v2, with the official MCP server noted. No OpenAPI document was found. The MCP server's two tools carry JSON Schema inputs with range constraints from pydantic Field (8 of 25). llms.txt on abuseipdb.com describes the API, endpoints, categories and reporting rules (10). Each endpoint has a purpose statement and a parameter table, the FAQ explains scoring and decay, and the docs say to act on abuseConfidenceScore rather than isWhitelisted, with little on when not to call (14 of 20). Parameters give defaults and ranges (maxAgeInDays 1 to 365, perPage 1 to 100), usageType has a listed set of values and categories are numbered, but types are not stated and the categories default is ambiguous (10 of 15). Examples in cURL, Python, PHP, C# and VBScript for every endpoint, and errors follow the JSON API shape with 422, 429 and 402 examples (12 of 15). v2 is in the path, there is no API changelog, the blog's last post is from December 2018, and the reports endpoint may change without notice (5 of 15). 8 + 10 + 14 + 10 + 12 + 5 = 59.", "b": "The surface graded is the WHOIS API, with the hosted MCP server noted. No OpenAPI document. JSON Schema draft-07 and XSD files define the WHOIS record, the DomainInfo response and the error body, and a Postman collection is published (15 of 25). llms.txt on www.whoisxmlapi.com lists the APIs, databases and feeds (10). The making-requests page states each parameter's purpose, default and credit cost, lists deprecated parameters that are still accepted, and says when RDAP applies, with little on when not to call (15 of 20). rdap, outputFormat and the cache flags have enumerated values and the record schema is typed, but unknown parameters are ignored silently and the output page gives no types in prose (11 of 15). Request examples, example records and an error table with HTTP status, errorCode and message (12 of 15). No API version and no changelog for the API; press releases summarise product updates yearly, the newest dated 9 May 2025, and the MCP server's versions are dated in the registry (7 of 15). 15 + 10 + 15 + 11 + 12 + 7 = 70." }, "scores": { "a": 59, "b": 70 } }, { "by": 10, "category": "reliability", "leads": "abuseipdb", "name": "Reliability", "reasons": { "a": "Read with the hosted lines. A status page on UptimeRobot is linked from every page's footer (20). Its monitors and 90-day history load by script and answered with an error on 3 November 2026, so no incident record could be read (5). Daily limits are published per endpoint and per plan, 1,000 checks a day on the free plan up to 50,000 on Premium (15). A 429 carries Retry-After, X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset, and a repeated report of the same address with the same comment within 24 hours updates the earlier report instead of adding one (15). The terms carry a service level agreement with a 99 per cent monthly availability target and a refund as the sole remedy (10). API v2 is generally available, with only the reports endpoint in open beta (10). 20 + 5 + 15 + 15 + 10 + 10 = 75.", "b": "Read with the hosted lines. The vendor's own Service Status and Data Releases page is linked from the docs and describes a per-API JSON status file with four levels (20). It shows no incident history and the status file's live values could not be read, so no 90-day record (5). The docs give 200 requests a second with rejection until the next second; the terms give 50 a second, 20 concurrent and 5 concurrent bulk requests, so numbers are published even though they disagree (15). A 429 AUTHENTICATE_06 carries Retry-After and every response X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset, with guidance to slow before zero; all calls are reads (15). No SLA; the terms guarantee no minimum uptime and cite a historical 99.9 per cent, with enterprise SLAs by separate agreement (0). The API is generally available (10). 20 + 5 + 15 + 15 + 0 + 10 = 65." }, "scores": { "a": 75, "b": 65 } }, { "by": 9, "category": "ergonomics", "leads": "abuseipdb", "name": "Agent ergonomics", "reasons": { "a": "check returns a compact record unless verbose is set, which adds the reports array, maxAgeInDays bounds the window, and blacklist takes a limit and a plaintext form (18 of 25). reports is paginated with page and perPage up to 100 and next and previous links, and blacklist filters by confidence, country and IP version, though check has no field selection (16 of 20). Errors carry a status and a detail an agent can act on, 429 names the daily limit and the headers say when it resets, and a 402 marks a plan limit on check-block (16 of 20). Every lookup is a GET, duplicate reports within 24 hours collapse, and both MCP tools are annotated readOnlyHint and idempotentHint (16 of 20). One required parameter per endpoint with sensible defaults. No official SDK beyond a Laravel package in the vendor's GitHub organisation and the Python MCP server (8 of 15). 18 + 16 + 16 + 16 + 8 = 74.", "b": "ignoreRawTexts drops the raw text fields, cmd=GET_DN_AVAILABILITY returns a two-field record, and the MCP server's reverse_whois defaults to a count-only mode; the MCP server lists 35 tools, more than 30, with a tool_search for deferred loading over stdio only (17 of 25). The WHOIS API returns one record per call with no pagination; bulk variants take up to 10,000 domains as jobs with status and results tools (8 of 20). Errors carry a code and a message an agent can branch on, though WHOIS_01 names both a validation error on HTTP 200 and an internal error on 500 (14 of 20). Every call is a read, and the cache flags make a repeat cheap, but a retry with _hardRefresh costs 5 credits each time and no annotations were found on the MCP tools (14 of 20). One required parameter, sensible defaults, and official Python and Go client libraries in the vendor's GitHub organisation, last pushed in 2023 (12 of 15). 17 + 8 + 14 + 14 + 12 = 65." }, "scores": { "a": 74, "b": 65 } }, { "by": 5, "category": "payments", "leads": "abuseipdb", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). Plan prices are public, $25 and $99 a month, sold by daily quota rather than per call (10). The Individual plan allows 1,000 checks a day with no card, and paid plans carry a 30-day trial (20). The key comes from the account page after a browser signup, and the terms forbid multiple accounts to raise quota, so no autonomous route (0). 0 + 10 + 20 + 0 = 30.", "b": "No x402, MPP or L402 (0). The only public price is from $129 a month for a universal credit pool; per-credit rates are behind a calculator whose output was not read and enterprise packages are by sales (5 of 20). 500 free WHOIS credits on signup with no card (20). The key comes from the account after a browser signup and no key API was found (0). 0 + 5 + 20 + 0 = 25." }, "scores": { "a": 30, "b": 25 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "AbuseIPDB LLC", "b": "Whois API, Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "https://mcp-hosted.whoisxmlapi.com/mcp", "name": "Hosted endpoint" }, { "a": "stdio", "b": "Streamable HTTP, stdio", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "2", "b": "35", "name": "Tools exposed" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "io.github.abuseipdb/abuseipdb-mcp", "b": "io.github.whois-api-llc/mcp-whoisxmlapi", "name": "MCP registry" }, { "a": "2026-08-02", "b": "2026-11-03", "name": "Last release" }, { "a": "no date given", "b": "2025-03-03", "name": "Terms last updated" }, { "a": "no date given", "b": "2020-04-06", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "6 stars", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "WhoisXML API scores 56.8 (C) on agent readiness against AbuseIPDB's 55.7 (C), and leads in 3 of 7 scored categories. AbuseIPDB leads on reliability, agent ergonomics and payments \u0026 pricing.", "question": "Which is better for AI agents, AbuseIPDB or WhoisXML API?" }, { "answer": "AbuseIPDB needs an API key. WhoisXML API takes an API key or an OAuth sign-in.", "question": "Do AbuseIPDB and WhoisXML API need an API key?" }, { "answer": "AbuseIPDB runs on your own machine, with no hosted endpoint listed. WhoisXML API has a hosted endpoint at https://mcp-hosted.whoisxmlapi.com/mcp.", "question": "Can an agent call AbuseIPDB and WhoisXML API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 75 against 65", "Agent ergonomics, 74 against 65", "Payments \u0026 pricing, 30 against 25" ], "also": null, "goodFor": "An agent that needs a quick reputation verdict on an IP or subnet, or wants to report abuse from its own logs, with a free daily quota large enough for one incident.", "slug": "abuseipdb", "watchFor": "No OpenAPI document, no API changelog (the blog's last post is from December 2018) and the reports endpoint is marked open beta and may change without notice" }, { "aheadOn": [ "Schema \u0026 documentation, 70 against 59", "Maintenance \u0026 community, 76 against 38" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "An agent investigating a domain's registration, history, DNS, certificates or related domains at scale, on a prepaid credit pool.", "slug": "whoisxml-api", "watchFor": "Per-credit prices are not published outside a calculator; the only public figure is from $129 a month, and orders are non-refundable" } ], "history": null, "job": { "capability": "secintel.reputation", "name": "Secintel reputation" }, "others": [ { "json": "https://www.anchorterminal.com/compare/abuseipdb-vs-censys.json", "title": "AbuseIPDB vs Censys", "url": "https://www.anchorterminal.com/compare/abuseipdb-vs-censys" }, { "json": "https://www.anchorterminal.com/compare/abuseipdb-vs-greynoise.json", "title": "AbuseIPDB vs GreyNoise", "url": "https://www.anchorterminal.com/compare/abuseipdb-vs-greynoise" }, { "json": "https://www.anchorterminal.com/compare/abuseipdb-vs-ipinfo.json", "title": "AbuseIPDB vs IPinfo", "url": "https://www.anchorterminal.com/compare/abuseipdb-vs-ipinfo" }, { "json": "https://www.anchorterminal.com/compare/abuseipdb-vs-pulsedive.json", "title": "AbuseIPDB vs Pulsedive", "url": "https://www.anchorterminal.com/compare/abuseipdb-vs-pulsedive" }, { "json": "https://www.anchorterminal.com/compare/abuseipdb-vs-virustotal.json", "title": "AbuseIPDB vs VirusTotal", "url": "https://www.anchorterminal.com/compare/abuseipdb-vs-virustotal" }, { "json": "https://www.anchorterminal.com/compare/greynoise-vs-whoisxml-api.json", "title": "GreyNoise vs WhoisXML API", "url": "https://www.anchorterminal.com/compare/greynoise-vs-whoisxml-api" }, { "json": "https://www.anchorterminal.com/compare/virustotal-vs-whoisxml-api.json", "title": "VirusTotal vs WhoisXML API", "url": "https://www.anchorterminal.com/compare/virustotal-vs-whoisxml-api" }, { "json": "https://www.anchorterminal.com/compare/ipinfo-vs-whoisxml-api.json", "title": "IPinfo vs WhoisXML API", "url": "https://www.anchorterminal.com/compare/ipinfo-vs-whoisxml-api" }, { "json": "https://www.anchorterminal.com/compare/censys-vs-whoisxml-api.json", "title": "Censys vs WhoisXML API", "url": "https://www.anchorterminal.com/compare/censys-vs-whoisxml-api" }, { "json": "https://www.anchorterminal.com/compare/securitytrails-vs-whoisxml-api.json", "title": "SecurityTrails vs WhoisXML API", "url": "https://www.anchorterminal.com/compare/securitytrails-vs-whoisxml-api" }, { "json": "https://www.anchorterminal.com/compare/shodan-vs-whoisxml-api.json", "title": "Shodan vs WhoisXML API", "url": "https://www.anchorterminal.com/compare/shodan-vs-whoisxml-api" }, { "json": "https://www.anchorterminal.com/compare/abuseipdb-vs-shodan.json", "title": "AbuseIPDB vs Shodan", "url": "https://www.anchorterminal.com/compare/abuseipdb-vs-shodan" }, { "json": "https://www.anchorterminal.com/compare/pulsedive-vs-whoisxml-api.json", "title": "Pulsedive vs WhoisXML API", "url": "https://www.anchorterminal.com/compare/pulsedive-vs-whoisxml-api" } ], "panel": null, "scores": [ { "abuseipdb": 75, "by": 10, "edge": "abuseipdb", "key": "reliability", "name": "Reliability", "weight": 16, "whoisxml-api": 65 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "abuseipdb": 59, "by": 11, "edge": "whoisxml-api", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "whoisxml-api": 70 }, { "abuseipdb": 74, "by": 9, "edge": "abuseipdb", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "whoisxml-api": 65 }, { "abuseipdb": 37, "by": 2, "edge": "whoisxml-api", "key": "security", "name": "Security \u0026 auth", "weight": 14, "whoisxml-api": 39 }, { "abuseipdb": 30, "by": 5, "edge": "abuseipdb", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "whoisxml-api": 25 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "abuseipdb": 38, "by": 38, "edge": "whoisxml-api", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "whoisxml-api": 76 }, { "abuseipdb": 63, "by": 3, "edge": "abuseipdb", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "whoisxml-api": 60 } ], "summary": "WhoisXML API scores 56.8 (C) on agent readiness against AbuseIPDB's 55.7 (C), and leads in 3 of 7 scored categories. AbuseIPDB leads on reliability, agent ergonomics and payments \u0026 pricing. Both do secintel reputation.", "tasks": null, "tutorials": [], "verdicts": { "abuseipdb": "A free key allows 1,000 IP checks a day with published per-endpoint limits, rate-limit headers and a 99 per cent SLA in the terms, and the official MCP server is read-only. One key covers reads, reports and deletes, the key may travel in a query string, there is no OpenAPI document, and the terms bar redistribution of results.", "whoisxml-api": "500 free credits with no card, JSON Schema and XSD for every response, 429s with Retry-After, cache controls that set the price per lookup, and a 35-tool hosted MCP server with OAuth. Per-credit prices sit behind a calculator, the terms confine data to one site and forbid AI training on it, and the key is accepted in the query string." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/abuseipdb-vs-whoisxml-api", "json": "https://www.anchorterminal.com/compare/abuseipdb-vs-whoisxml-api.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/abuseipdb-vs-whoisxml-api.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/abuseipdb-vs-whoisxml-api.min.md" }, "markdown": "WhoisXML API scores 56.8 (C) on agent readiness against AbuseIPDB's 55.7 (C), and leads in 3 of 7 scored categories. AbuseIPDB leads on reliability, agent ergonomics and payments \u0026 pricing. Both do secintel reputation.\n\n- AbuseIPDB: grade C, 55.7/100, rank #765 of 1349. Markdown https://www.anchorterminal.com/tools/abuseipdb.md · JSON https://www.anchorterminal.com/api/v1/tools/abuseipdb.json\n- WhoisXML API: grade C, 56.8/100, rank #731 of 1349. Markdown https://www.anchorterminal.com/tools/whoisxml-api.md · JSON https://www.anchorterminal.com/api/v1/tools/whoisxml-api.json\n- Best threat and security intelligence APIs for AI agents: https://www.anchorterminal.com/best/security-intelligence/index.md\n- All 33 security intel comparisons: https://www.anchorterminal.com/compare/security-intelligence/index.md\n\n## Which one, for what\n\n### AbuseIPDB (C)\n\nGood for: An agent that needs a quick reputation verdict on an IP or subnet, or wants to report abuse from its own logs, with a free daily quota large enough for one incident.\n\nAhead on:\n- Reliability, 75 against 65\n- Agent ergonomics, 74 against 65\n- Payments \u0026 pricing, 30 against 25\n\nWatch for: No OpenAPI document, no API changelog (the blog's last post is from December 2018) and the reports endpoint is marked open beta and may change without notice\n\n### WhoisXML API (C)\n\nGood for: An agent investigating a domain's registration, history, DNS, certificates or related domains at scale, on a prepaid credit pool.\n\nAhead on:\n- Schema \u0026 documentation, 70 against 59\n- Maintenance \u0026 community, 76 against 38\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: Per-credit prices are not published outside a calculator; the only public figure is from $129 a month, and orders are non-refundable\n\n\n## Why the edge\n\n### Maintenance \u0026 community: WhoisXML API +38\n\n- AbuseIPDB (38): Read as a closed service with an official MCP server. The newest dated change to the surface is the MCP server's v0.1.1 on 2 August 2026, 93 days before the check; the API docs and blog carry no later date (10 of 30). One release in the last 90 days, v0.1.1 fell just outside it (0 of 20). Support is a contact form with no guaranteed response on the free plan, there is no public changelog for the API, and the MCP repository shows a pull request merged on 2 August but GitHub's issue pages could not be read (5 of 15). The MCP server sits in the official registry under io.github.abuseipdb (15). The MCP package has CI on Python 3.11 to 3.14 with ruff, pytest and a packaging check, and a locked dependency set (8 of 10). 10 + 0 + 5 + 15 + 8 = 38.\n- WhoisXML API (76): Read as a closed service with an official MCP server. MCP server 1.13.0 was published in the official registry on 3 November 2026 and the ProfessionalServices and ipgeo-community repositories were pushed the same day (30). 1.8.6 on 8 September through 1.13.0 on 3 November 2026 is nine registry versions in 90 days (20). Product updates are summarised in yearly press releases, the newest 9 May 2025, support is a contact form with tiered response times sold separately, and the client library repositories were last pushed in 2023 (8 of 15). The MCP server is in the official registry under io.github.whois-api-llc, and official Python and Go clients exist (15). The MCP server's source was not found on GitHub, and the SDK repositories show no activity since 2023 (3 of 10). 30 + 20 + 8 + 15 + 3 = 76.\n\n### Schema \u0026 documentation: WhoisXML API +11\n\n- AbuseIPDB (59): The surface graded is the REST API v2, with the official MCP server noted. No OpenAPI document was found. The MCP server's two tools carry JSON Schema inputs with range constraints from pydantic Field (8 of 25). llms.txt on abuseipdb.com describes the API, endpoints, categories and reporting rules (10). Each endpoint has a purpose statement and a parameter table, the FAQ explains scoring and decay, and the docs say to act on abuseConfidenceScore rather than isWhitelisted, with little on when not to call (14 of 20). Parameters give defaults and ranges (maxAgeInDays 1 to 365, perPage 1 to 100), usageType has a listed set of values and categories are numbered, but types are not stated and the categories default is ambiguous (10 of 15). Examples in cURL, Python, PHP, C# and VBScript for every endpoint, and errors follow the JSON API shape with 422, 429 and 402 examples (12 of 15). v2 is in the path, there is no API changelog, the blog's last post is from December 2018, and the reports endpoint may change without notice (5 of 15). 8 + 10 + 14 + 10 + 12 + 5 = 59.\n- WhoisXML API (70): The surface graded is the WHOIS API, with the hosted MCP server noted. No OpenAPI document. JSON Schema draft-07 and XSD files define the WHOIS record, the DomainInfo response and the error body, and a Postman collection is published (15 of 25). llms.txt on www.whoisxmlapi.com lists the APIs, databases and feeds (10). The making-requests page states each parameter's purpose, default and credit cost, lists deprecated parameters that are still accepted, and says when RDAP applies, with little on when not to call (15 of 20). rdap, outputFormat and the cache flags have enumerated values and the record schema is typed, but unknown parameters are ignored silently and the output page gives no types in prose (11 of 15). Request examples, example records and an error table with HTTP status, errorCode and message (12 of 15). No API version and no changelog for the API; press releases summarise product updates yearly, the newest dated 9 May 2025, and the MCP server's versions are dated in the registry (7 of 15). 15 + 10 + 15 + 11 + 12 + 7 = 70.\n\n### Reliability: AbuseIPDB +10\n\n- AbuseIPDB (75): Read with the hosted lines. A status page on UptimeRobot is linked from every page's footer (20). Its monitors and 90-day history load by script and answered with an error on 3 November 2026, so no incident record could be read (5). Daily limits are published per endpoint and per plan, 1,000 checks a day on the free plan up to 50,000 on Premium (15). A 429 carries Retry-After, X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset, and a repeated report of the same address with the same comment within 24 hours updates the earlier report instead of adding one (15). The terms carry a service level agreement with a 99 per cent monthly availability target and a refund as the sole remedy (10). API v2 is generally available, with only the reports endpoint in open beta (10). 20 + 5 + 15 + 15 + 10 + 10 = 75.\n- WhoisXML API (65): Read with the hosted lines. The vendor's own Service Status and Data Releases page is linked from the docs and describes a per-API JSON status file with four levels (20). It shows no incident history and the status file's live values could not be read, so no 90-day record (5). The docs give 200 requests a second with rejection until the next second; the terms give 50 a second, 20 concurrent and 5 concurrent bulk requests, so numbers are published even though they disagree (15). A 429 AUTHENTICATE_06 carries Retry-After and every response X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset, with guidance to slow before zero; all calls are reads (15). No SLA; the terms guarantee no minimum uptime and cite a historical 99.9 per cent, with enterprise SLAs by separate agreement (0). The API is generally available (10). 20 + 5 + 15 + 15 + 0 + 10 = 65.\n\n### Agent ergonomics: AbuseIPDB +9\n\n- AbuseIPDB (74): check returns a compact record unless verbose is set, which adds the reports array, maxAgeInDays bounds the window, and blacklist takes a limit and a plaintext form (18 of 25). reports is paginated with page and perPage up to 100 and next and previous links, and blacklist filters by confidence, country and IP version, though check has no field selection (16 of 20). Errors carry a status and a detail an agent can act on, 429 names the daily limit and the headers say when it resets, and a 402 marks a plan limit on check-block (16 of 20). Every lookup is a GET, duplicate reports within 24 hours collapse, and both MCP tools are annotated readOnlyHint and idempotentHint (16 of 20). One required parameter per endpoint with sensible defaults. No official SDK beyond a Laravel package in the vendor's GitHub organisation and the Python MCP server (8 of 15). 18 + 16 + 16 + 16 + 8 = 74.\n- WhoisXML API (65): ignoreRawTexts drops the raw text fields, cmd=GET_DN_AVAILABILITY returns a two-field record, and the MCP server's reverse_whois defaults to a count-only mode; the MCP server lists 35 tools, more than 30, with a tool_search for deferred loading over stdio only (17 of 25). The WHOIS API returns one record per call with no pagination; bulk variants take up to 10,000 domains as jobs with status and results tools (8 of 20). Errors carry a code and a message an agent can branch on, though WHOIS_01 names both a validation error on HTTP 200 and an internal error on 500 (14 of 20). Every call is a read, and the cache flags make a repeat cheap, but a retry with _hardRefresh costs 5 credits each time and no annotations were found on the MCP tools (14 of 20). One required parameter, sensible defaults, and official Python and Go client libraries in the vendor's GitHub organisation, last pushed in 2023 (12 of 15). 17 + 8 + 14 + 14 + 12 = 65.\n\n### Payments \u0026 pricing: AbuseIPDB +5\n\n- AbuseIPDB (30): No x402, MPP or L402 (0). Plan prices are public, $25 and $99 a month, sold by daily quota rather than per call (10). The Individual plan allows 1,000 checks a day with no card, and paid plans carry a 30-day trial (20). The key comes from the account page after a browser signup, and the terms forbid multiple accounts to raise quota, so no autonomous route (0). 0 + 10 + 20 + 0 = 30.\n- WhoisXML API (25): No x402, MPP or L402 (0). The only public price is from $129 a month for a universal credit pool; per-credit rates are behind a calculator whose output was not read and enterprise packages are by sales (5 of 20). 500 free WHOIS credits on signup with no card (20). The key comes from the account after a browser signup and no key API was found (0). 0 + 5 + 20 + 0 = 25.\n\n## Score by category\n\n| Category | Weight | AbuseIPDB | WhoisXML API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 75 | 65 | AbuseIPDB +10 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 59 | 70 | WhoisXML API +11 |\n| Agent ergonomics | 13% (16.2 this run) | 74 | 65 | AbuseIPDB +9 |\n| Security \u0026 auth | 14% (17.5 this run) | 37 | 39 | WhoisXML API +2 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 25 | AbuseIPDB +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 38 | 76 | WhoisXML API +38 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 63 | 60 | AbuseIPDB +3 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **55.7 · C** | **56.8 · C** | |\n\n## Facts side by side\n\n| Fact | AbuseIPDB | WhoisXML API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | AbuseIPDB LLC | Whois API, Inc. |\n| Hosted endpoint | no (local only) | `https://mcp-hosted.whoisxmlapi.com/mcp` |\n| Transports | stdio | Streamable HTTP, stdio |\n| Auth | API key | OAuth or key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Tools exposed | 2 | 35 |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | yes |\n| MCP registry | `io.github.abuseipdb/abuseipdb-mcp` | `io.github.whois-api-llc/mcp-whoisxmlapi` |\n| Last release | 2026-08-02 | 2026-11-03 |\n| Terms last updated | no date given | 2025-03-03 |\n| Privacy policy last updated | no date given | 2020-04-06 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | yes | yes |\n| Popularity | 6 stars | none |\n\n## Verdicts\n\n**AbuseIPDB.** A free key allows 1,000 IP checks a day with published per-endpoint limits, rate-limit headers and a 99 per cent SLA in the terms, and the official MCP server is read-only. One key covers reads, reports and deletes, the key may travel in a query string, there is no OpenAPI document, and the terms bar redistribution of results.\n\n**WhoisXML API.** 500 free credits with no card, JSON Schema and XSD for every response, 429s with Retry-After, cache controls that set the price per lookup, and a 35-tool hosted MCP server with OAuth. Per-credit prices sit behind a calculator, the terms confine data to one site and forbid AI training on it, and the key is accepted in the query string.\n\n## Before you call either\n\n### AbuseIPDB\n\n1. Send `Accept: application/json` and the key in the `Key` header; without the Accept header the API answers with an HTML page\n2. Act on `abuseConfidenceScore` rather than `isWhitelisted`, and pass `maxAgeInDays` to bound how old the reports can be (default 30, maximum 365)\n3. Watch `X-RateLimit-Remaining` per endpoint and on a 429 wait for `Retry-After`, which can be most of a day since limits reset at 00:00 UTC\n4. Use `check-block` for a subnet (up to /24 on the free plan) and `blacklist` with `confidenceMinimum` only on a paid plan; over-limit `limit` values are truncated silently\n5. Strip personal data from report comments, which are public, and prefer the read-only MCP server when the task never reports\n\n### WhoisXML API\n\n1. Send the key as `Authorization: Bearer` and `outputFormat=JSON`; the default output is XML and an `apiKey` query parameter overrides the header\n2. Leave the cache flags alone for 1 credit a lookup; `_hardRefresh=1` costs 5 credits, and `_dbOnly=1` returns WHOIS_03 when nothing is cached\n3. Read `audit.updatedDate` before trusting a record, and check `dataError` for MASKED_WHOIS_DATA or PARTIAL_DATA\n4. Watch `X-RateLimit-Remaining` and on 429 AUTHENTICATE_06 wait for `Retry-After`; a 401 AUTHENTICATE_05 means the balance is spent, so stop\n5. Keep results inside the customer's own systems; the terms forbid passing data to third parties or using it to train models\n\n## Questions\n\n### Which is better for AI agents, AbuseIPDB or WhoisXML API?\n\nWhoisXML API scores 56.8 (C) on agent readiness against AbuseIPDB's 55.7 (C), and leads in 3 of 7 scored categories. AbuseIPDB leads on reliability, agent ergonomics and payments \u0026 pricing.\n\n### Do AbuseIPDB and WhoisXML API need an API key?\n\nAbuseIPDB needs an API key. WhoisXML API takes an API key or an OAuth sign-in.\n\n### Can an agent call AbuseIPDB and WhoisXML API without installing anything?\n\nAbuseIPDB runs on your own machine, with no hosted endpoint listed. WhoisXML API has a hosted endpoint at https://mcp-hosted.whoisxmlapi.com/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/abuseipdb-vs-whoisxml-api.json, and with the fewest tokens: https://www.anchorterminal.com/compare/abuseipdb-vs-whoisxml-api.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"abuseipdb\", \"b\": \"whoisxml-api\"}`. From a terminal: `anchor compare abuseipdb whoisxml-api`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/abuseipdb.json and https://www.anchorterminal.com/api/v1/tools/whoisxml-api.json\n\n## Other comparisons with AbuseIPDB or WhoisXML API\n\n- [AbuseIPDB vs Censys](https://www.anchorterminal.com/compare/abuseipdb-vs-censys.md)\n- [AbuseIPDB vs GreyNoise](https://www.anchorterminal.com/compare/abuseipdb-vs-greynoise.md)\n- [AbuseIPDB vs IPinfo](https://www.anchorterminal.com/compare/abuseipdb-vs-ipinfo.md)\n- [AbuseIPDB vs Pulsedive](https://www.anchorterminal.com/compare/abuseipdb-vs-pulsedive.md)\n- [AbuseIPDB vs VirusTotal](https://www.anchorterminal.com/compare/abuseipdb-vs-virustotal.md)\n- [GreyNoise vs WhoisXML API](https://www.anchorterminal.com/compare/greynoise-vs-whoisxml-api.md)\n- [VirusTotal vs WhoisXML API](https://www.anchorterminal.com/compare/virustotal-vs-whoisxml-api.md)\n- [IPinfo vs WhoisXML API](https://www.anchorterminal.com/compare/ipinfo-vs-whoisxml-api.md)\n- [Censys vs WhoisXML API](https://www.anchorterminal.com/compare/censys-vs-whoisxml-api.md)\n- [SecurityTrails vs WhoisXML API](https://www.anchorterminal.com/compare/securitytrails-vs-whoisxml-api.md)\n- [Shodan vs WhoisXML API](https://www.anchorterminal.com/compare/shodan-vs-whoisxml-api.md)\n- [AbuseIPDB vs Shodan](https://www.anchorterminal.com/compare/abuseipdb-vs-shodan.md)\n- [Pulsedive vs WhoisXML API](https://www.anchorterminal.com/compare/pulsedive-vs-whoisxml-api.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "AbuseIPDB vs WhoisXML API", "url": "" } ], "description": "WhoisXML scores 56.8 (C) to AbuseIPDB's 55.7 (C) for secintel reputation. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "AbuseIPDB C 55.7", "WhoisXML API C 56.8", "scores" ], "h1": "AbuseIPDB vs WhoisXML API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/abuseipdb-vs-whoisxml-api", "published": "2026-10-01", "section": "tools", "title": "AbuseIPDB vs WhoisXML for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/abuseipdb-vs-whoisxml-api" }, "tokens": { "markdown": 4350, "slim": 2730 }, "version": 1 }