D20DAO Verifiable Randomness MCP server
org.d20dao/vrf·v0.1.2Verifiable VRF draws on Arc, 0.05 USDC each. On Robinhood Chain, integrate on chain with the SDK.
0 stars414 downloads/wk
Reviews
Write oneNobody has reviewed D20DAO Verifiable Randomness yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
D20DAO Verifiable Randomness tools (3)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
drawDraw verifiable randomness for … USDC: dice, a coin flip, a number in a range, one or several winners, or a shuffle.
get_resultRead a paid draw by paymentId, or a request by requestId, for free. Use it to finish a draw that came back pending or unanswered.
setup_statusCheck whether draws can be paid: the Circle CLI, its login, the agent wallet, its Gateway balance and today's spending. Returns the next setup step.
Public scan report
scanner v0.1.10 · 2026-10-15 · same rubric, same numbers if you re-run it
- Code scan10 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 6 days ago15/15
- Maintainer identityregistry namespace matches repository owner; website matches verified namespace9/10
How D20DAO Verifiable Randomness compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 94/100
- higher than 96% of 48,243 servers
- Tools
- 3
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 414
- more than 85% of 12,306 servers with a package
What its tools let an agent do: 2 read · 1 change
Release history: 2 versions in the registry since 2026-09-19, latest 2026-10-09, typically one every 20 days.
Install D20DAO Verifiable Randomness in Claude Code, Cursor or VS Code
Runs npx -y @d20dao/mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add vrf -- npx -y @d20dao/mcp
What the publisher says
From the D20DAO Verifiable Randomness repository's README, as published. We do not edit it. Read it on GitHub
D20DAO MCP server
Verifiable randomness for AI agents: dice, coin flips, ranges, winners and shuffles, each one a VRF request on Arc with a proof anyone can replay. 0.05 USDC per draw, paid from your Circle Agent Wallet.
Setup
- Wallet. Have your agent follow Circle's setup guide. It installs the Circle CLI, logs you in with an emailed code and creates an agent wallet. You accept Circle's terms yourself.
- Funds. Fund the wallet with USDC and deposit some into Circle Gateway, for example on Arc:
circle gateway deposit --chain ARC --method direct --amount 1 --address <wallet>Arc, Polygon, Avalanche, Base, Arbitrum, Optimism, Unichain and Ethereum balances all work.
- Server. Add it to your client.
Claude Code:
claude mcp add d20dao -- npx -y @d20dao/mcp@0.1.0Claude Desktop, Cursor and others (mcpServers in the client's MCP config):
{ "mcpServers": { "d20dao": { "command": "npx", "args": ["-y", "@d20dao/mcp@0.1.0"] } } }On Windows, use "command": "cmd" with "args": ["/c", "npx", "-y", "@d20dao/mcp@0.1.0"] if the client cannot start npx directly. Pin the version, since the server runs with your Circle session.
Ask your agent to call setup_status; it names the next step until everything is ready.
Tools
An optional seed (up to 64 bytes) is bound on chain to the draw, so a raffle can name its round before the result exists. Give each separate draw its own seed: an identical draw within five minutes returns the earlier one without paying.
A draw usually answers in about ten seconds, but it can take longer. If your client's tool timeout is short (60 seconds is a common default), raise it; a retry after a timeout returns the same draw rather than paying twice.
Settings
Safety
- The server holds no keys. The Circle CLI signs, and your Circle wallet limits apply. It never accepts Circle's terms for you: CIRCLEACCEPTTERMS is kept out of the CLI it runs, and DONOTTRACK is set so your item labels stay out of the CLI's telemetry.
- It pays only api.d20dao.org (or api-testnet.d20dao.org) and never more than 0.05 USDC per draw. If the CLI ever reports another seller, that draw comes back with a warning and paid draws stop until you delete halt.json from the server's home folder.
- Each draw reserves its price in the daily record before paying; if the record cannot be written, it does not pay.
- A draw that is still pending is finished for free with get_result. If the answer is lost after payment, the server resends the payment the CLI signed, which the API honours at most once.
- A result says charged: false only when that is known. When it says unknown, do not draw again; check with get_result or the wallet.
- draw is marked as a tool with side effects, so clients ask before running it unless you allow it.
Verify
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
D20DAO Verifiable Randomness: common questions
- Is D20DAO Verifiable Randomness MCP server safe?
- Yes, by our scan: it is graded A (94/100). Read the D20DAO Verifiable Randomness safety report
- How do I install D20DAO Verifiable Randomness?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does D20DAO Verifiable Randomness need an API key?
- No secret keys are declared. It reads 6 settings from the environment.
- Is D20DAO Verifiable Randomness maintained?
- The last commit was 27 days ago (2026-10-09). The latest release is v0.1.2.
- How does D20DAO Verifiable Randomness compare with other MCP servers?
- safety score 94/100 (higher than 96% of 48,243 servers); tools 3 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.