Skip to main content
Glama

Related Servers

Alternatives to @voidly/mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      C
      maintenance
      Enables AI agents to run open-source intelligence workflows such as sanctions screening, prioritized vulnerability briefs, IOC searches, evidence-chain verification, and sun-position chronolocation.
      5
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Provides tools for AI agents to access Bitcoin, Lightning Network, and Nostr knowledge, including real-time network statistics and Web of Trust reputation data. It features an integrated Lightning Network payment system for micro-transactions and query-based interactions.
      12
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to conduct zero-key multi-source deep research, run quick searches across DuckDuckGo, Wikipedia, and ArXiv, and cryptographically verify claims with token-compressed, citation-backed evidence.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Provides AI agents with 12 real-time tools for search synthesis, grounded research dossiers, claim verification, citation generation, sentiment analysis, expert ranking, timeline creation, and competitive landscape mapping over Streamable HTTP or stdio.
      1
      12
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to validate AI infrastructure claims, check endpoint availability, solve CAPTCHA challenges, convert web pages to Markdown, search the web, extract structured JSON, and fetch bot-protected HTML through native tool calls.
      MIT

    TDQS

    B3.1/5.0

    Scored across 89 tools

    Disambiguation3/5

    The agent relay tools are mostly distinct, but the censorship tools have significant overlap: get_country_status, check_domain_blocked, get_isp_status, check_service_accessibility, and get_domain_status all answer similar blocking questions. Descriptions provide some differentiation (e.g., 'UNIQUE' labels and 'use X instead'), but with 89 tools an agent can still easily misselect among the many query variants.

    Naming Consistency4/5

    All names use snake_case, and the agent_* prefix creates a clear namespace for relay tools. The sentinel_* prefix groups forecast tools, though those names are more noun-based than verb_noun; censorship tools lack a unified prefix but remain readable and consistent in style.

    Tool Count1/5

    89 tools is an extreme mismatch for a single MCP server, far exceeding the typical 3-15 range. The surface sprawls across two large domains (censorship monitoring and agent relay), and many tools are minor variants that could be consolidated.

    Completeness3/5

    Core censorship querying and agent relay workflows (identity, messaging, tasks, attestations, memory) are well covered. However, obvious lifecycle gaps exist: no delete/leave channel, no delete or update webhook, no get specific message, no unpin key, and no alert subscription management for censorship alerts.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues