Skip to main content
Glama
helGayhub233

SurveyHub-MCP

by helGayhub233
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to SurveyHub-MCP

No user-submitted related servers found.

    Related Servers

    • FOFA Quake Hunter MCP Server

      RuoJi6
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables AI models to query FOFA, 360 Quake, and Hunter cyberspace mapping platforms for asset discovery and security research. It supports natural language parameter configuration and provides comprehensive search tools for retrieving IP, port, and domain data.
      3
      7
      MIT

    • touful-vuln-search-mcp

      touful
      F
      license
      Not graded
      quality
      B
      maintenance
      Unified vulnerability search MCP server for penetration testing agents, integrating 5 data sources (NVD, OSV, EPSS, CISA KEV, Exploit-DB+GitHub) and 10 MCP tools for CVE query, keyword search, batch query, EPSS scoring, KEV checking, exploit search, and comprehensive assessment with Chinese output.
      2
      -

    • 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
    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 26 tools

    Disambiguation4/5

    Tools are clearly grouped by platform (fofa, hunter, quake, zoomeye, daydaymap), making them distinct. Minor confusion arises from quake_search being an alias for quake_service_scroll, and similar patterns across platforms (e.g., user_info), but overall an agent can differentiate.

    Naming Consistency4/5

    Naming follows a consistent platform_action pattern (e.g., fofa_search, hunter_enterprise_search). Inconsistencies include quake_search as an alias and variations like service_search vs. service_scroll, but the system is largely predictable.

    Tool Count4/5

    26 tools is slightly high but appropriate given the aggregation of five different search engines, each requiring multiple operations (search, user info, aggregation, batch). The count reflects the breadth of the domain without being excessive.

    Completeness4/5

    The toolset covers the essential lifecycle for asset intelligence search: query, pagination, aggregation, and account info across multiple platforms. Minor gaps exist, like missing user info for DayDayMap, but core workflows are complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources