{
  "markdown": "# Shodan InternetDB — IP Hostname & Service Intelligence\n\nShodan's free InternetDB API. Lookup any IP and get its open ports, detected services, hostnames, vulnerabilities, and tags (CDN, cloud, ICS, etc.). The data behind \"what's actually running on this IP?\" — derived from Shodan's continuous internet scanning. Free, no auth.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Why this matters for AI agents\n\nFor security analysis, attack-surface reconnaissance (your own assets), or threat-hunting context, Shodan's data is canonical. InternetDB specifically is the free, lightweight subset — for full Shodan capabilities (search, historical, alerts), commercial Shodan API is needed.\n\nCommon flows:\n\n- **IP lookup.** \"What's running on 1.2.3.4?\" → open ports, services, vulnerabilities.\n- **Pre-attack reconnaissance (defensive).** Audit your own infrastructure as it appears externally.\n- **Pair with threat intel.** Cross-reference with [AbuseIPDB](/docs/reference/abuseipdb) (reputation), [PhishTank / URLhaus](/docs/reference) (URL threat).\n\n## Auth\n\nNone. InternetDB is free, no key, no signup. Generous rate limits.\n\nFor the full Shodan search API (historical scans, advanced search, real-time alerts), a Shodan membership is required (~$59/year for hobbyist tier). InternetDB exposes the static-snapshot subset.\n\n## What InternetDB returns\n\nFor a queried IP:\n\n```json\n{\n  \"ip\": \"1.2.3.4\",\n  \"hostnames\": [\"example.com\"],\n  \"ports\": [22, 80, 443],\n  \"vulns\": [\"CVE-2021-44228\"],\n  \"tags\": [\"cdn\", \"cloud\"]\n}\n```\n\n| Field | Meaning |\n|---|---|\n| `ports` | Open ports detected by Shodan's scanners |\n| `vulns` | CVE IDs that Shodan's heuristics flag as likely vulnerable based on detected service banners |\n| `hostnames` | Reverse DNS or self-reported hostnames |\n| `tags` | Categorical tags (cdn, cloud, ics, vpn, tor, etc.) |\n| `cpes` | (in some responses) detected software fingerprints |\n\n## Common pitfalls\n\n- **Snapshot, not real-time.** InternetDB data may be days or weeks stale. The IP may have closed those ports since the last scan. For \"current state,\" you need live scanning of your own assets.\n- **Vulnerability flags are heuristic.** Shodan flags `vulns` based on service banner matching — `nginx 1.18.0` → CVE-2021-23017. The actual instance may be patched (banners often retain old version strings post-patch). Never act on `vulns` alone — confirm with direct verification.\n- **CDN / proxy IPs.** Cloudflare, Akamai, AWS CloudFront IPs surface massive port footprints because they front many sites. The data isn't about a specific website — it's about the proxy infrastructure.\n- **Tor exit nodes.** Tagged `tor` in InternetDB. Reputation systems sometimes blacklist them; legitimate users (privacy-conscious) come through too.\n- **Coverage gaps.** Not every IP is scanned. Behind-NAT, IPv6, and dynamically-assigned IPs may have no Shodan record.\n- **Don't use for attack.** Shodan data is for defensive reconnaissance and research. Using it to identify and attack vulnerable systems you don't own is illegal and against Shodan's TOS.\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"shodan-internetdb\": {\n      \"url\": \"https://gateway.pipeworx.io/shodan-internetdb/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/shodan-internetdb/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Shodan Internetdb data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 5192,
  "sha": "39aabf5e929edab902cafb26c45a5245d6e1b141022a5e34b00ee57ddbc466b8",
  "repo_slug": "pipeworx-io/mcp-shodan-internetdb",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_shodan_internetdb_afe04103/readme"
}