Skip to main content
Glama
Sign In
dark-mcp

dark-mcp

by superagent-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to dark-mcp

No user-submitted related servers found.

    Related Servers

    • StealthMole MCP Server

      StealthMole MCP Serverofficial

      StealthMole
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables access to StealthMole's threat intelligence API for searching and monitoring threats across Deep & Dark Web, Telegram channels, leaked credentials, and ransomware incidents. Provides comprehensive cybersecurity intelligence through natural language queries.
      -

    • darknet-mcp-server

      utrawal9185-cmd
      A
      license
      B
      quality
      D
      maintenance
      Unified 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.
      66
      419 npm
      3
      MIT
    • F6 Threat Intelligence MCP Server

      F6 Threat Intelligence MCPofficial

      F6-Security
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to search and retrieve threat-intelligence collections—including leaks, malware, attacks, suspicious IPs, threats, and group profiles—through indicator queries, filtered pagination, update tracking, and WHOIS enrichment.
      9
      1
      Apache 2.0

    • url-intelligence-agent

      vpicciuolo
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to investigate public URLs through evidence-first intelligence, including crawling, entity resolution, social discovery, SEO, technology detection, monitoring, reports, and optional AI reasoning.
      7
      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

    A3.5/5.0

    Scored across 9 tools

    Disambiguation4/5

    The onion tools are well-differentiated: search_onion hits an external provider, search_onion_cache queries the local index, and fetch_onion/crawl_onion are read vs. index operations. The Telegram search trio (search_telegram_messages vs search_telegram_posts) is the weakest boundary, relying on the 'allowed channel' vs 'public/free quota' distinction, but descriptions do clarify it.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern (get_status, fetch_onion, crawl_onion, search_onion, read_telegram_channel, etc.). The search_onion_cache suffix is the only minor deviation but still fits the convention cleanly.

    Tool Count5/5

    Nine tools is well-scoped for the domain, split sensibly between a Tor/onion surface (5) and a Telegram surface (4). No redundant or filler tools; each earns its place.

    Completeness4/5

    The set covers discovery, reading, crawling/indexing, and both local and external search across two sources, which is solid lifecycle coverage. Minor gaps remain: no index management (purge/delete) or explicit corpus listing beyond get_status's size report, but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Resources