Skip to main content
Glama
aqhmal

securitytrails-mcp

by aqhmal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to securitytrails-mcp

No user-submitted related servers found.

    Related Servers

    • osint-mcp-server

      badchars
      A
      license
      A
      quality
      C
      maintenance
      Provides AI agents with 37 OSINT tools and 12 data sources to perform unified reconnaissance, domain analysis, and attack surface mapping. It enables agents to query, correlate, and reason across platforms like Shodan, VirusTotal, and Censys in parallel.
      37
      364 npm
      60
      MIT

    • mcp-shodan

      Astrid43
      F
      license
      Not graded
      quality
      A
      maintenance
      Gives AI agents access to the Shodan API and Shodan CVEDB for host reconnaissance, device search, DNS lookups, and CVE/CPE vulnerability intelligence. It returns open ports, banners, TLS certificates, subdomains, and CVSS/EPSS/KEV severity data through eleven read-only tools.
      -

    • Clearfront MCP Server

      scottmartinanderson
      A
      license
      A
      quality
      B
      maintenance
      Enables AI-driven open-source intelligence investigations by exposing 30 tools for scanning emails, usernames, domains, IPs, and more, with real subprocess execution.
      31
      44 PyPI
      10
      MIT

    • mcp-shodan

      ferreira04707
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to perform internet-facing reconnaissance and vulnerability research by looking up open ports, banners and TLS details for IPs, searching devices with Shodan query syntax, resolving DNS records in batch, and retrieving CVE/CPE intelligence with CVSS, EPSS and KEV status. Tools are read-only, credit-aware, and exposed over stdio or HTTP streaming.
      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

    A4.1/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: WHOIS, DNS, subdomains, history, SSL, IP data, and search are clearly separated. The only potential overlap is domain_details vs whois_current, but the descriptions make their scopes explicit (DNS vs WHOIS record). No two tools appear to serve the same purpose.

    Naming Consistency4/5

    All tools share the 'securitytrails_' prefix and use snake_case, which is consistent. However, some names are nouns (ping, usage, tags) while others are verb_noun (search_domains, get_domain_details implied), so the pattern is not uniformly verb-first. Minor deviation but still predictable and readable.

    Tool Count4/5

    17 tools is on the heavier side but appropriate for the breadth of SecurityTrails' API (WHOIS, DNS, subdomains, IP intelligence, search). Each tool covers a meaningful function; the count reflects the domain's scope rather than redundancy. It sits just above the ideal range but remains well-scoped.

    Completeness5/5

    The tool surface covers the major SecurityTrails capabilities: current and historical WHOIS/DNS, subdomain enumeration, associated domains, SSL certificates, IP information, and flexible search with scrolling. There are no obvious dead ends—quota checks and paging support are included. The API's core workflows appear fully represented.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources