Skip to main content
Glama
DanDaDaDanDan

mcp-osint

by DanDaDaDanDan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to mcp-osint

No user-submitted related servers found.

    Related Servers

    • OSINT MCP Server

      CloudWaddie
      A
      license
      D
      quality
      D
      maintenance
      A comprehensive MCP server providing tools for IP, domain, email, and image-based open-source intelligence. It integrates services like Shodan, VirusTotal, and HaveIBeenPwned to facilitate advanced security research and data gathering.
      56
      52 npm
      ISC

    • OSINT MCP Server

      osintukraine
      A
      license
      C
      quality
      D
      maintenance
      MCP server for the OSINT Intelligence Platform, enabling AI assistants to interact with Telegram intelligence archives via 65 tools for search, entity analysis, event tracking, social graph, and platform monitoring.
      71
      2
      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

    • 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
    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.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clear, non-overlapping purpose: listing sources, searching, previewing schemas, and fetching data. No ambiguity between them.

    Naming Consistency5/5

    All tools follow a consistent 'osint_verb' pattern (preview, list_sources, search, get), with predictable naming.

    Tool Count5/5

    Four tools cover the essential OSINT workflow (list, search, preview, get) without excess or deficiency.

    Completeness5/5

    The tool surface covers the full lifecycle: discover sources, search, preview data, and fetch. No obvious gaps for the intended use case.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources