OSINT MCP Server
Related Servers
Alternatives to OSINT MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP 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
- FlicenseNot gradedqualityDmaintenanceAn MCP server for communication service connectors that currently provides multi-account Telegram integration with granular tool access and security controls. It allows AI models to manage messages, chats, and media across various accounts through a flexible, extensible routing architecture.1-
- AlicenseBqualityDmaintenanceUnified dark web and threat intelligence MCP server providing 66 tools across 16 data sources, including breach databases, ransomware tracking, Tor .onion access, blockchain intel, and malware analysis for AI agents.66186 npmMIT
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server that exposes multiple OSINT tools to AI assistants like Claude, enabling sophisticated reconnaissance and information gathering tasks using industry-standard OSINT tools.237MIT
- AlicenseAqualityBmaintenanceAn MCP server that gives AI agents full access to a personal Telegram account via MTProto, enabling chat reading, history search, messaging, media handling, and automations.79MIT
- AlicenseAqualityAmaintenanceMCP server that acts as a gateway to Telegram, providing AI-optimized tools for messaging, search, and chat management via MTProto. Supports multi-user authentication with QR login and HTTP/stdio transports.82MIT
TDQS
Scored across 71 tools
Many tools have heavily overlapping purposes, especially the large cluster of stats/dashboard tools (get_platform_dashboard, get_platform_stats_overview, get_metrics_overview, get_system_status, get_system_health, get_metrics_services, get_processing_stats, get_worker_stats, etc.). While some search tools are well-differentiated, an agent would frequently struggle to choose the correct endpoint.
The overwhelming majority follow a clean get_/list_/search_ convention, making the set largely predictable. Minor deviations like unified_search, find_similar_messages, suggest_locations, and reverse_geocode break the pattern slightly but do not create serious confusion.
With 71 tools, this server is far beyond the recommended range and feels like an entire platform API exposed as MCP tools. Even accounting for a broad OSINT domain, the sheer number of narrowly-scoped stats and analytics endpoints creates a bloated, hard-to-navigate surface.
For a read-only OSINT/analytics platform, the surface is quite comprehensive: message retrieval, semantic search, entity search, event timelines, channel analytics, map data, and platform health are all covered. Minor gaps exist around data export, mutating operations, or direct access to some raw sources, but agents can likely accomplish the intended research workflows.