Skip to main content
Glama
randa-mu

drand-mcp-server

by randa-mu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to drand-mcp-server

No user-submitted related servers found.

    Related Servers

    • Drand

      xiaobenyang-com
      A
      license
      B
      quality
      D
      maintenance
      drand-mcp-server is a service that provides verifiable random numbers for model-driven processes in AI applications, supporting the acquisition of random numbers by time or round.
      3
      2
      Apache 2.0

    • Random-Generator

      xiaobenyang-com
      A
      license
      A
      quality
      D
      maintenance
      An encrypted and secure random number generation server that complies with the MCP protocol, suitable for AI applications, LLMS, and other systems that require high-quality random numbers.
      7
      2
      Apache 2.0

    • provably-fair-mcp

      gadaffihub
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server enabling provably-fair random selection and winner picking using drand randomness, with tools for instant picks, scheduled draws, and verification.
      MIT

    • Chainlink MCP Server

      goldk3y
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Chainlink's decentralized oracle network, providing access to real-time price feeds, serverless functions, smart contract automation, verifiable randomness, cross-chain messaging, and proof of reserve across multiple blockchain networks.
      -
    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.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool requires a distinct input: round number, timestamp, or no input for latest. There is no overlap in purpose, making it easy for an agent to select the correct tool.

    Naming Consistency5/5

    All tool names follow the consistent pattern 'get-randomness-by-{criteria}', using hyphenated lowercase. The naming is predictable and clear.

    Tool Count5/5

    Three tools is appropriate for a focused server that retrieves randomness from drand. The count is not excessive nor insufficient for the domain.

    Completeness4/5

    The tools cover the primary ways to fetch randomness (by round, by time, latest). One could argue for a tool to list available rounds, but the current set is functionally complete for the server's purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources