Skip to main content
Glama
k3nn3dy-ai

Shodan MCP Server

by k3nn3dy-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Shodan MCP Server

No user-submitted related servers found.

    Related Servers

    • offsec-mcp

      nadirzhon
      A
      license
      A
      quality
      B
      maintenance
      MCP server for offensive-security tooling, enabling AI agents to run reconnaissance, CVE intelligence, JavaScript analysis, HTTP probing, and port scanning against authorized targets.
      10
      MIT

    • Pentest MCP

      Holland8079
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables professional penetration testers to run reconnaissance, exploitation, password cracking, web fuzzing, vulnerability scanning, traffic capture, and client-reporting workflows through MCP transports with auth support.
      172 npm
      GPL 3.0

    • Pentest MCP

      aPhillips0102
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables professional penetration testers to run reconnaissance, network and web scanning, content fuzzing, vulnerability templates, brute-force checks, SQLi extraction, traffic capture, and engagement report generation through MCP clients.
      172 npm
      GPL 3.0
    • @guardbee/security-suite by GuardBee

      @guardbee/security-suiteofficial

      GuardBee
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables unified security workflows with secret scanning, dependency CVE auditing, TLS/SSL inspection, and DNS/SPF/DMARC checks through a single MCP server.
      911 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 47 tools

    Disambiguation4/5

    Most tools target distinct Shodan resources and actions, with clear separation between search, count, host lookup, DNS, scans, alerts, notifiers, datasets, CVEDB, and exploits. A few boundaries are softer—shodan_host vs. shodan_internetdb both enrich IPs, and cve/cves/cpes and exploits/exploit_count are closely related—but the descriptions generally clarify intended use.

    Naming Consistency5/5

    All tools use a consistent shodan_ prefix with snake_case names and mostly predictable noun or noun_action ordering (e.g., shodan_alert_create, shodan_notifier_delete, shodan_dns_resolve). Plural forms for list endpoints are used consistently enough that the pattern remains easy to follow.

    Tool Count2/5

    47 tools is very large for an MCP server and creates a heavy selection burden for an agent, even though Shodan's API is broad. The surface spans many subdomains, but the count is well beyond the range where tools are easy to scan and choose among.

    Completeness4/5

    Coverage is strong across search, host intelligence, DNS, scanning, alerts with triggers and notifiers, community queries, datasets, CVEDB, and exploits. Minor gaps may exist around streaming or other specialized Shodan APIs, but the major workflows are well covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources