Skip to main content
Glama

Related Servers

Alternatives to tor-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to search, fetch, and interactively browse web pages through a fail-closed Tor/VPN-only tunnel, rotate identities, and exchange end-to-end encrypted messages with other agents via MCP.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents and compatible MCP clients to fetch, search, and download web content—including .onion services—anonymously through the Tor network, using a fresh circuit per call and retrying when exit nodes are blocked.
      6
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to control Tor Browser with full anonymity preservation, including navigation, Tor circuit management, and traffic interception.
      1
      MIT
    • F
      license
      B
      quality
      B
      maintenance
      Enables coding agents and scripts to crawl and map sites, read pages as clean Markdown or structured content, extract data with schemas or local AI, and run multi-angle deep research with numbered sources. It also handles JavaScript-rendered pages through a headless browser and applies safety controls for private addresses, robots.txt, and polite pacing.
      10
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to retrieve verified web evidence via headless Chromium rendering, sitemap navigation, and search candidate discovery, returning clean Markdown, structured JSON, and verbatim quoted proof.
      12 npm
      MIT

    TDQS

    A4.1/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct action: status check, static fetch, JS-capable browsing, page interaction (click/type/screenshot), archiving, and circuit reset. The only potential overlap — tor_fetch vs tor_browse — is explicitly resolved in both descriptions (lightweight no-JS retrieval vs headless Chromium with interaction follow-ups). tor_click, tor_type and tor_screenshot are clearly scoped as continuations of a tor_browse session.

    Naming Consistency4/5

    All names share a uniform tor_ snake_case prefix with single-word verbs (fetch, browse, click, type, screenshot, archive), which is highly predictable. Minor deviation: tor_status and tor_new_identity are noun-phrase style rather than verb_noun, but semantics remain obvious.

    Tool Count5/5

    Eight tools is well within the sweet spot and each one maps to a real capability: connectivity check, two retrieval modes, three interaction primitives, evidence capture, and identity rotation. Nothing feels redundant or padded for a Tor browsing server.

    Completeness4/5

    The surface covers the full core lifecycle: verify Tor connectivity, retrieve pages (static or JS), interact, capture evidence, archive, and rotate identity. Gaps are minor — no back/forward navigation or history control, no explicit session close/cleanup beyond tor_new_identity, and no scroll or multi-element form submission — but agents can largely work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues