Skip to main content
Glama
voidly-ai

@voidly/mcp-server

by voidly-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @voidly/mcp-server

No user-submitted related servers found.

    Related Servers

    • voidsend-mcp

      JamshedMemon
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for VoidSend enabling AI agents to send and receive end-to-end encrypted messages.
      6 npm
      MIT

    • 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

    • agent-relay

      cloud1map
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables AI agents on different machines to communicate and collaborate directly through relay channels, supporting structured agent contracts, real-time messaging, and human-in-the-loop approval workflows.
      12,453 npm
      MIT

    • Frostbyte MCP

      Robocular
      A
      license
      Not graded
      quality
      C
      maintenance
      A unified MCP server providing AI agents with 40+ developer APIs including geolocation, crypto prices, DNS lookup, and web scraping. Enables natural language access to various tools through a single gateway.
      1
      MIT
    • warmthengine.com/mcp by warmthengine

      warmthengine.com/mcpofficial

      warmthengine
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server exposing 16 programmatic tools for AI systems to query verified Coordination Intelligence on AI infrastructure events, connections, and actors across geopolitical blocs.
      1
      -
    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 158 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes with detailed descriptions, but there is some overlap within categories like anomaly detection (anomaly_dbscan, anomaly_fused, anomaly_score) and forecasting (forecast_multi_horizon, forecast_tft) where agents might struggle to choose the right one without deeper knowledge.

    Naming Consistency4/5

    Names follow a consistent verb_noun pattern with prefixes like agent_, atlas_, classifier_, forecast_, etc. Minor deviations exist (relay_info, voidly_pay_overview) but do not significantly harm predictability.

    Tool Count2/5

    158 tools is excessively large for most use cases. While the domain is complex, this number likely overwhelms agents and requires extensive filtering or selection logic, reducing practical coherence.

    Completeness5/5

    The tool set covers the entire censorship monitoring and agent relay domain extremely thoroughly, including agent lifecycle, communication, memory, multiple ML models, incident management, probes, and verification. No obvious gaps remain.

    Maintenance

    ActivitySlowing
    ResponsivenessSyncing

    Resources