Skip to main content
Glama
0day404

FOFA MCP

by 0day404
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to FOFA MCP

No user-submitted related servers found.

    Related Servers

    • SurveyHub-MCP

      helGayhub233
      A
      license
      B
      quality
      B
      maintenance
      Aggregates multiple cyberspace search engines (FOFA, Quake, Hunter, ZoomEye) into a unified MCP server, enabling asset search, pagination, statistics, and account info retrieval.
      26
      35 PyPI
      MIT

    • mcp-recon

      dotMuny
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to run reconnaissance tasks such as DNS, WHOIS, certificate transparency, TLS certificate, HTTP header, and limited port checks against explicitly authorized domains and IPs. Scope permissions, deny rules, default-deny resolution pinning, rate budgets, and append-only audit logging are all enforced inside the server so an out-of-scope request cannot be expressed.
      12
      Apache 2.0

    • mcp-shodan

      KellyGrigorev50
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to query the Shodan API and Shodan CVEDB for internet-connected device search, IP and host reconnaissance, DNS and subdomain lookups, and CVE/CPE vulnerability intelligence with CVSS, EPSS and KEV data. Supports credit-aware operations over stdio or HTTP streaming.
      -
    • mlab.sh MCP server by mlab-sh

      mlab.sh MCP serverofficial

      mlab-sh
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables threat intelligence for SOC and DFIR workflows, including IOC enrichment, CVE and threat actor lookup, domain scanning, and account-based scan management.
      2
      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/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct role, and the descriptions explicitly cross-reference when to use alternatives (search vs structured vs next, host vs stats). The search-family trio is well differentiated by intent and the cursor/token flow.

    Naming Consistency5/5

    All tools use the fofa_ prefix with consistent snake_case and predictable action suffixes (search, search_structured, search_next, host, stats, account_info, health). The pattern is uniform and readable throughout.

    Tool Count5/5

    Seven tools is well-scoped for a read-only FOFA search API, with each tool earning its place (query building, pagination, host detail, aggregation, account, health). No redundant or filler tools.

    Completeness4/5

    Covers the full lifecycle of a search service: query construction, pagination continuation, asset drill-down, stats, quota, and config health. Only minor gaps exist, such as bulk export/download, which agents can work around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources