Skip to main content
Glama
dotMuny

mcp-recon

by dotMuny
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to mcp-recon

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

    • 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
      174 npm
      55
      MIT

    • Harrier

      Caleb68864
      A
      license
      B
      quality
      B
      maintenance
      A disciplined OSINT collection server for LLM agents that wraps free open-source reconnaissance tools behind a normalized schema, enabling automated, deterministic collection of public intelligence with confidence scoring and graceful degradation.
      12
      MIT

    • AynOps

      gaoharimran29-glitch
      F
      license
      Not graded
      quality
      B
      maintenance
      AI-powered cybersecurity reconnaissance platform that allows users to perform threat analysis and ethical scanning of domains via natural language, with policy enforcement and audit logging.
      -

    • asi-mcp

      deruke
      F
      license
      Not graded
      quality
      D
      maintenance
      AI-powered Attack Surface Intelligence server that exposes industry-standard penetration testing tools via MCP, enabling AI agents to perform comprehensive security assessments.
      3
      -
    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 12 tools

    Disambiguation4/5

    Each tool targets a distinct reconnaissance action or data source; overlapping pairs (certificate_transparency vs tls_certificate_info, analyze_jwt vs decode_payload, http_fetch vs http_headers_audit) are clearly differentiated by descriptions. Minor overlap remains but no serious misselection risk.

    Naming Consistency3/5

    All names are snake_case and descriptive, but the set mixes verb-first patterns (check_ports, parse_url) with noun-first patterns (dns_lookup, http_fetch) and noun-noun names (certificate_transparency, tls_certificate_info). The convention is readable but not fully predictable.

    Tool Count5/5

    12 tools for a scoped reconnaissance server is well within the ideal 3-15 range; each tool covers a distinct capability and there is no redundant filler.

    Completeness4/5

    The surface covers scope/budget, passive DNS/WHOIS/CT, live TLS, HTTP fetching/auditing, port checks, and local JWT/payload/URL analysis. Minor gaps exist (e.g., no reverse DNS/IP WHOIS or deeper active enumeration), but they are reasonable given the deliberate safety restrictions.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources