GreyNoise vs Shodan

GreyNoise 75

Read for a closed service with an open-source MCP server and SDK. MCP server v0.5.5 tagged 9 October 2026, 25 days before the check, and product updates on 31 August 2026 (30). In the 90 days to 3 November, dated entries are the Visualizer post of 17 August, the CrowdStrike post of 31 August and the MCP release of 9 October; the Python SDK's last tag is v3.1.0 of 9 July (12 of 20). The MCP repository merged pull request 18 from an outside account on 9 October and has commits from two outside contributors; issues could not be read on github.com; Slack and Discord communities and support@greynoise.io (15 of 25). The official MCP server is not in the official MCP registry, where three third-party servers are; the Python SDK is current (10 of 15). CI runs typecheck, tests, a build, npm audit and an MCPB pack, with a live read-only validation against the API, and releases publish from tags with npm provenance; the SDK repository has only a Slack notice workflow (8 of 10). 30 + 12 + 15 + 10 + 8 = 75.

Shodan 16

No dated API change found. The blog's newest post is 7 August 2024, and the official Python library shodan 1.31.0 was published on 17 December 2023 with the repository's last push on 5 August 2024 (0 of 30). No releases or dated changelog entries in the last 90 days (0 of 20). 63 open issues on the Python repository with no push since August 2024; a support email and a help centre exist (5 of 25). The official Python SDK still installs but is two years old, and the other clients are community work (8 of 15). The repository has no CI configuration and no CHANGELOG entry since 1.28.0 of July 2022 (3 of 10). 0 + 0 + 5 + 8 + 3 = 16.

GreyNoise 78

Read with the hosted lines for the v3 REST API. Status page at status.greynoise.io on incident.io with 16 components, ten of them GreyNoise's own, including API and API Data Freshness (20). No incident is listed for the 90 days to 3 November 2026. The API component shows 99.94 per cent uptime for August to November and the group 99.83 per cent, downtime the page gives no incident for, so read as clean or trivial with that caveat (25 of 30). Limits with numbers exist only for the free side, 10 lookups a day unauthenticated and 50 searches a week on a free account; paid plans are 'Unlimited' on the plans page and no per-minute figure was found (8 of 15). 429 responses are defined on 29 of 70 operations and a 503 at query engine capacity carries a documented Retry-After header, which the official SDK and MCP client honour with backoff. No idempotency keys for the blocklist, alert and feed writes (10 of 15). The plans page publishes an SLA of 1 business day, 8 hours or 4 hours on paid tiers beside support hours, which reads as a response time, and no availability SLA was found (5 of 10). The v3 API is generally available and v2 was decommissioned on 30 April 2026 (10). 20 + 25 + 8 + 10 + 5 + 10 = 78.

Shodan 40

Read with the hosted lines. A public status page exists at status.shodan.io (UptimeRobot), but on 3 November 2026 its component list failed to load and it showed only that there were no updates in the last 7 days, so no component history was readable (10 of 20). No readable incident record for the 90 days (5). The billing page states that all API plans are limited to 1 request a second, and credits per plan are published with numbers (15). No 429, Retry-After or backoff guidance was found in the reference or the OpenAPI document; the only error statement is that a non-200 status carries an error message, and no idempotency keys exist for alert, notifier or scan writes. The official Python client throttles itself to 1 request a second and retries a timed-out search cursor, which is client behaviour, not an API contract (0). No SLA found on the billing, enterprise or developer pages (0). The REST API is generally available (10). 10 + 5 + 15 + 0 + 0 + 10 = 40.

GreyNoise 83

OpenAPI 3.0.0 at api.greynoise.io/v3/openapi.yaml, 65 paths and 70 operations, every one with a description, 32 enums, a key header security scheme, and 400, 401, 403, 429 and 500 responses on nearly every operation (25). llms.txt at docs.greynoise.io/llms.txt, and every docs page is served as Markdown with a .md suffix (10). Operation descriptions say what each call returns and when to use quick, with little on when not to use a call; the MCP tool descriptions in the source are fuller (14 of 20). Typed path and query parameters with enums and required flags, and bulk bodies typed as {"ips": [...]} with a 10,000 limit in prose (12 of 15). The guides carry curl and Python examples and the spec defines error bodies with example messages, but the v3 IP reference page itself has no code sample (11 of 15). Versioned paths and a migration matrix with dated deprecation, end-of-life and decommission for v2, plus dated product-update posts naming new endpoints, but no API changelog as such and an empty roadmap page (11 of 15). 25 + 10 + 14 + 12 + 11 + 11 = 83.

Shodan 46

The surface graded is the REST API at api.shodan.io. An OpenAPI 3.0.0 document at developer.shodan.io/api/openapi.json covers 37 paths and 44 operations, but declares no securitySchemes, no enums and a non-200 response on one operation only (15 of 25). No llms.txt on developer.shodan.io or www.shodan.io, both 404, and no Markdown docs served for agents (0 of 10). Every operation carries a description, and the reference says which calls cost credits and which plans can scan, with little on when not to use a call (12 of 20). Required flags on the key and path parameters, with facets, query and fields as free strings and no enums or constraints (7 of 15). Example requests and responses for every endpoint in the reference, and errors documented only as a non-200 status with an error field (9 of 15). No version in the path, the OpenAPI document says 1.0.0, and the only dated record of changes is the blog, whose newest post is 7 August 2024 (3 of 15). 15 + 0 + 12 + 7 + 9 + 3 = 46.

GreyNoise 76

Closed service under an EULA last modified 7 May 2025 that is clear on scope, with the MCP server and SDK under MIT (15 of 30). Privacy policy of 3 September 2026 with retention periods (threat data indefinitely, backups 14 days, logs about 30 days, account data until deletion is requested), named subprocessors and standard contractual clauses for transfers; no DPA named, and the page as served repeats its sections twice with small differences, such as whether Cloudflare is a subprocessor (20 of 30). The migration matrix dates v2's deprecation (28 July 2025), end of life (1 January 2026) and decommission (30 April 2026) and marks five v3 endpoints deprecated, while the EULA lets GreyNoise discontinue any product at any time with 10 days' notice of EULA changes (15 of 20). Amazon Web Services, Snowflake, Auth0, Stripe, Stigg, Datadog, Webflow, Google, HubSpot and Cloudflare named, with hosting in the United States (15 of 20). 15 + 20 + 15 + 15 = 65.

Shodan 44

Editorial half. A closed service whose terms at static.shodan.io/legal/terms.html were not read, because that host answers 403 to robots.txt, so their clarity can't be assessed; the Python library is MIT (5 of 30). The privacy policy at account.shodan.io/privacy carries no date, names no legal entity, retention period, data location or subprocessor, and says Shodan may share information with advertisers, business partners, sponsors and other third parties (5 of 30). The help centre says export credits are deprecated and no longer sold, with no date; no deprecation policy found (3 of 20). No subprocessors or data locations disclosed (0 of 20). 5 + 5 + 3 + 0 = 13.

GreyNoise 40

One API key per workspace with no scopes and no read-only variant, sent in a key header, and no page read documents rotation or revocation; the MCP security page says only to rotate on compromise (12 of 30). Most endpoints read, and the MCP server marks its write and destructive tools and has a read-only validation mode, but the API has no read-only key or confirmation step for deleting a blocklist or alert (10 of 20). IP context returns raw HTTP paths, user agents and payloads sent by scanners, and GNQL returns the same at scale; no prompt-injection guidance was found in the docs, the MCP server page or its SECURITY.md (3 of 15). The workspace page shows weekly search usage and the MCP security page says to watch the dashboard for unexpected usage; no per-call log or key activity record was found (5 of 15). SOC 2 Type II announced on 8 June 2023, security@greynoise.io named in the MCP server's SECURITY.md, but security.txt returns 404, the trust centre at greynoise.hypercomply.io renders by script and was not read, and no bug bounty or disclosure policy was found (10 of 20). 12 + 10 + 3 + 5 + 10 = 40.

Shodan 19

One key per account with no scopes, sent as key= in the query string on every documented call and in the OpenAPI document, with no header option. Read as a plain key, the way the Alpha Vantage listing was read, less 10 for the query string (10 of 30). No read-only key or least-privilege mode; the free plan's limits are quotas, not scopes, and alerts, notifiers and org members can be deleted with the same key and no confirmation (3 of 20). Results carry banners, HTTP titles and page bodies collected from arbitrary hosts, and no guidance on treating them as untrusted was found (3 of 15). /api-info reports the plan and credits, and no call log for the key holder was found (3 of 15). security.txt returns 404 on www.shodan.io, and no bug bounty, disclosure policy, SOC 2 or ISO 27001 was found on the pages read (0 of 20). 10 + 3 + 3 + 3 + 0 = 19.

GreyNoise 76

quick=true cuts an IP lookup to found and the classification or trust level, /v3/gnql/metadata drops raw scan data, and request_metadata.restricted_fields names what a plan withholds; no arbitrary field selection (18 of 25). GNQL pages default to 1,000 results with size up to 10,000 and a scroll token, plus stats, count and export variants and CSV output in the SDK (18 of 20). Error bodies carry a message, 206 marks partial content from plan limits, and the 503 at capacity documents Retry-After, though the 429 example says only that the limit was hit (15 of 20). Nearly every call is a GET or a read POST; the blocklist, alert and feed-consumer writes have no idempotency key. The MCP server sets readOnlyHint true by default, marks 8 write tools and sets destructiveHint on the delete tools (15 of 20). One required parameter on most calls and sensible defaults, but the only official SDK is Python; the TypeScript MCP server is not a client library (10 of 15). 18 + 18 + 15 + 15 + 10 = 76.

Shodan 64

minify on host lookups drops banners and returns ports and host facts, minify on search (on by default) truncates large fields and fields selects which fields come back, so an agent can size a response (20 of 25). page with 100 results a page, facets for summaries, count for a free total, and the whole filter language of the search engine (18 of 20). Errors are a non-200 status and a short message such as Invalid IP, with no code list to branch on (8 of 20). Most calls are GET reads. Alerts, notifiers, scans and org members are written with POST, PUT and DELETE and no idempotency key, and nothing marks a destructive call (10 of 20). Few required parameters and sensible defaults, but only one official SDK, the Python library, with the other twelve languages community work (8 of 15). 20 + 18 + 8 + 10 + 8 = 64.