Skip to main content
Glama

Related Servers

Alternatives to scandomain-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      6
      MIT
    • 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server providing 15 OSINT tools over free, public sources for AI agents, enabling domain reconnaissance, subdomain discovery, DNS lookups, host profiling, CVE search, and more without API keys.
      MIT
    • 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
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      A production-style MCP server providing AI models with cybersecurity tools including port scanning, WHOIS, DNS, threat intelligence, CVE lookup, and more.
      -
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server for domain intelligence — WHOIS, DNS records, SSL certificate inspection, SPF/DMARC validation, security-header audits, and blacklist/reputation checks, callable by AI agents. Powered by domainintel.app; runs server-side, no local setup.
      7
      99
      MIT

    TDQS

    B3.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only a single tool, there is no possibility of confusion or overlap. The tool's purpose is clearly unique within the set.

    Naming Consistency5/5

    The single tool name 'scandomain_search' follows a clear prefix_verb pattern that is consistent and readable. No inconsistency arises with only one tool.

    Tool Count2/5

    Providing only one tool for scanning and searching assets feels too few. Even for a focused search server, additional tools like list, get_details, or scan_initiate would be expected for a complete workflow.

    Completeness2/5

    The tool surface is severely limited to only search functionality. Missing operations such as initiating scans, retrieving asset details, or managing results create significant gaps for any real-world asset management task.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues