D20DAO MCP server
Allows requesting verifiable randomness on the Arc blockchain, including dice rolls, coin flips, ranges, winner selection, and shuffles, with request/fulfillment transactions and replayable proofs.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@D20DAO MCP server roll a d20 and show the proof link"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
Draws run on Arc through the D20DAO x402 API. D20DAO also runs on Robinhood Chain, where there is no x402 API: a contract there requests randomness directly on chain, using @d20dao/vrf-sdk 0.6.2 and its integration guide.
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.2Claude Desktop, Cursor and others (
mcpServersin the client's MCP config):{ "mcpServers": { "d20dao": { "command": "npx", "args": ["-y", "@d20dao/mcp@0.1.2"] } } }On Windows, use
"command": "cmd"with"args": ["/c", "npx", "-y", "@d20dao/mcp@0.1.2"]if the client cannot startnpxdirectly. 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.
Related MCP server: drand-mcp-server
Tools
Tool | Cost | Does |
| 0.05 USDC |
|
| free | Reads a draw by |
| free | Checks the CLI, login, wallet, Gateway balance and today's spending. |
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
Variable | Default | |
|
| Spending cap per UTC day, shared by every server process of the user. |
|
|
|
| first funded | Circle CLI chain code to pay from, such as |
| first agent wallet | Agent wallet to pay from. |
|
| Path to the CLI's |
|
| Where the spending record is kept. |
Safety
The server holds no keys. The Circle CLI signs, and your Circle wallet limits apply. It never accepts Circle's terms for you:
CIRCLE_ACCEPT_TERMSis kept out of the CLI it runs, andDO_NOT_TRACKis set so your item labels stay out of the CLI's telemetry.It pays only
api.d20dao.org(orapi-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 deletehalt.jsonfrom 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: falseonly when that is known. When it saysunknown, do not draw again; check withget_resultor the wallet.drawis marked as a tool with side effects, so clients ask before running it unless you allow it.
Verify
Every result links its request and fulfillment transactions and a proof page. Replay the proof yourself with @d20dao/vrf-sdk 0.6.2 or later; see verification and the agent API guide.
License
MIT
Available Tools
3 toolsdrawDraw verifiable randomness (0.05 USDC)ADestructive
Draw verifiable randomness for 0.05 USDC: dice, a coin flip, a number in a range, one or several winners, or a shuffle. Opens one VRF request on Arc and returns the result with request, fulfillment and proof links; the optional seed is bound to the payment on chain. Pays from the user's Circle Agent Wallet. One call returns every value of its operation, so ask once and never repeat a call to re-roll. An identical call within five minutes returns the earlier draw without paying; give each separate draw its own seed. The user sets a daily spending cap, so draws can run out: a paid answer carries what is left, and setup_status shows the cap.
Inputs: operation (required), max, min, seed, +4 more.
get_resultRead a draw (free)ARead-onlyIdempotent
Read a paid draw by paymentId, or a request by requestId, for free. Use it to finish a draw that came back pending or unanswered. Chosen items come back as indices here, not as labels: apply them to the list you sent.
Inputs: paymentId, requestId.
setup_statusCheck payment setup (free)ARead-onlyIdempotent
Check 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.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool addresses a distinct stage: draw executes a randomness request, get_result retrieves a prior request or payment, and setup_status reports payment readiness. There is no meaningful overlap or ambiguity between them.
get_result and setup_status follow a clear verb_noun pattern and draw is a concise imperative action. The only slight inconsistency is that draw lacks the prefixed/object style of the other two, but the intended action is still obvious.
Three tools is well-scoped for a focused randomness service: one action, one retrieval, and one status/readiness check. Each tool earns its place without redundancy.
The core lifecycle is covered: perform randomness, retrieve results, and verify ability to pay. A minor gap is the lack of a listing/history mechanism for past draws, but the described workflow is otherwise functional.
Maintenance
Related MCP Connectors
Verified EVM, Aptos and finance tools for AI agents; gas for 14 chains. Pay per call (x402).
Risk and verification data for ERC-8004 AI agents. Two free tools; rest per-call in USDC.
Paid agent work and paid verification, settled in USDC. Verified outcomes get signed receipts.
Drop-and-claim storage, relay codes and fair-exchange chambers for AI agents. Pay per use in USDC.
Related MCP 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
- AlicenseAqualityFmaintenanceEnables AI applications to fetch verifiable randomness from the drand network, supporting latest, time-based, and round-based beacon retrieval.314 npmMIT
- FlicenseNot gradedqualityDmaintenanceProvides true random generation tools for AI agents, including coin flip, dice roller, random numbers, and wheel of fortune, enabling decisions and TTRPG sessions.-
- AlicenseNot gradedqualityCmaintenanceEnables LLMs like Claude to generate genuine random numbers instead of inventing them, covering dice rolls, coin flips, number draws, random selection from lists, and shuffling. It runs as a free-tier Cloudflare Worker using a cryptographically secure generator, and also exposes a REST API, a demo page, and progress-reporting tools for long-running calls.MIT