Skip to main content
Glama
fitzypopper

osint-mcp-server

by fitzypopper
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to osint-mcp-server

No user-submitted related servers found.

    Related Servers

    • recon-mcp

      nekiyRichie
      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

    • 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

    • omega-mcp-server

      Ekoelogan
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that exposes 108+ omega-cli OSINT tools for reconnaissance, web analysis, threat intelligence, and reporting, enabling AI assistants to perform comprehensive open-source intelligence tasks.
      MIT

    • 221B

      eugepolo
      A
      license
      A
      quality
      B
      maintenance
      A local MCP server that gives AI clients OSINT tools to find public profiles, search the web, inspect pages, look up domains and Shodan services, and export sourced, timestamped findings without requiring API keys by default.
      8
      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.3/5.0

    Scored across 32 tools

    Disambiguation3/5

    Most tools map to a distinct source or entity (WHOIS, BGP, GitHub, Reddit, OTX), so an agent can usually choose correctly. However, dns_lookup and dns_lookup_all appear near-identical, crtsh_search and hackertarget_hostsearch both target subdomains, and the all-in-one recon tools duplicate many individual lookups.

    Naming Consistency4/5

    The set mostly follows a clean snake_case source_or_object convention (github_user_repos, check_email_breaches, otx_indicator). Minor inconsistencies such as dns_lookup vs dns_lookup_all, hackertarget_hostsearch, and osint_list_sources are easy to learn but break the pattern slightly.

    Tool Count2/5

    At 32 tools, the surface is heavy and likely to increase prompt and selection cost for an agent; while each tool represents a plausible OSINT data source, the count exceeds the range where an agent can quickly scan and disambiguate options. Consolidating the recon aggregators or reducing similar lookups would help.

    Completeness4/5

    The server covers a coherent OSINT workflow: DNS/WHOIS/subdomain enumeration, IP/BGP/geo enrichment, social and username lookup, breach checking, and threat-intel feeds. Some broader OSINT categories such as phone numbers, image search, or mainstream social platforms beyond GitHub/Reddit/Keybase are absent, but the core domain is well covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources