Drand
Related Servers
Alternatives to Drand
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn 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.72Apache 2.0
- AlicenseNot gradedqualityAmaintenanceMCP server enabling provably-fair random selection and winner picking using drand randomness, with tools for instant picks, scheduled draws, and verification.MIT

provably-fair-mcpofficial
AlicenseNot gradedqualityBmaintenanceMCP server for provably-fair random selection using public drand randomness, enabling verifiable winner picks for giveaways, raffles, and tie-breaks.MIT- AlicenseAqualityCmaintenanceMCP server providing true randomness capabilities to Claude, enabling cryptographically secure random number generation for games, decision-making, sampling, simulations, and any operation requiring genuine randomness.132MIT
- AlicenseAqualityAmaintenanceProduction-ready MCP server that provides LLMs with essential random generation abilities, including random integers, floats, choices, shuffling, and cryptographically secure tokens.7174 PyPI51MIT
- AlicenseAqualityFmaintenanceEnables AI applications to fetch verifiable randomness from the drand network, supporting latest, time-based, and round-based beacon retrieval.35 npmMIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose with no overlap: get-randomness-by-round retrieves randomness for a specific round, get-randomness-by-time for a specific time, and get-randomness-latest for the most recent value. The descriptions explicitly differentiate the input parameters (round, time, latest), making it impossible to confuse them.
All tool names follow a consistent verb_noun pattern with hyphens: 'get-randomness-by-round', 'get-randomness-by-time', and 'get-randomness-latest'. This uniformity makes the naming predictable and easy to understand, adhering to a clear convention throughout the set.
With 3 tools, the count is appropriate for the server's purpose of fetching randomness from drand quicknet, as it covers the main use cases (by round, by time, latest). It is slightly lean but reasonable, as adding more tools might overcomplicate this focused domain without obvious gaps.
The tool set provides complete coverage for retrieving randomness values from drand quicknet, addressing key scenarios: specific rounds, specific times, and the latest value. A minor gap might be the lack of tools for metadata or chain information, but for the core functionality of fetching randomness, it is nearly complete and functional.