Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

D20DAO Verifiable Randomness

NPM · @D20DAO/MCP · SCANNED SEP 25

Verifiable dice, draws and shuffles with on-chain VRF proofs on Arc. 0.05 USDC per draw.

Available components

npm · @d20dao/mcp 69
69 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 4 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 750 tokens (~250/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

How do I install the D20DAO Verifiable Randomness MCP server?

D20DAO Verifiable Randomness runs locally as an npm package, launched with npx -y @d20dao/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @d20dao/mcp

# add to Claude Code
claude mcp add org-d20dao-vrf -- npx -y @d20dao/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "org-d20dao-vrf": {
      "command": "npx",
      "args": [
        "-y",
        "@d20dao/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "org-d20dao-vrf": {
      "command": "npx",
      "args": [
        "-y",
        "@d20dao/mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add org-d20dao-vrf -- npx -y @d20dao/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-d20dao-vrf": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@d20dao/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add org-d20dao-vrf --command npx --arg -y --arg @d20dao/mcp
# ~/.hermes/config.yaml
mcp_servers:
  org-d20dao-vrf:
    command: "npx"
    args: ["-y", "@d20dao/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "org-d20dao-vrf": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@d20dao/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add org-d20dao-vrf -t stdio -c npx -a -y @d20dao/mcp
// mcp.json
{
  "mcpServers": {
    "org-d20dao-vrf": {
      "command": "npx",
      "args": [
        "-y",
        "@d20dao/mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 21 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
  • 20 Sept 26 54

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 25 Sept 2026 · Analysed npm/@d20dao/mcp@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 4 packages
Packages resolved 4
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~567 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
draw ~426

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.

NameTypeReqDescription
countinteger–dice: rolls, 1 to 128 (default 1). chooseMany: distinct picks, required.
itemsarray–chooseOne, chooseMany, shuffle: labels to draw from (1 to 256, each at most 200 bytes). Only their count is proven; the answer adds picked. Give this or population.
max––range only, required: highest value, inclusive, at least min.
min––range only, required: lowest value, inclusive.
operationstringyesraw: one 256-bit word. coinFlip: 0 (tails) or 1 (heads). dice: count rolls of 1 to sides. range: one integer from min to max. chooseOne: one zero-based index. chooseMany: count distinct indices. shuf…
populationinteger–chooseOne, chooseMany, shuffle: how many to draw from, 1 to 256. Give this or items.
seedstring–Context bound on chain to this draw, such as "raffle-7 round 2" (at most 64 bytes). Use a new seed for each separate draw. To commit to an item list, put its hash here.
sides––dice only, required: faces per die, at least 2.

No output schema declared.

No examples provided.

get_result ~102

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.

NameTypeReqDescription
paymentIdstring–The paymentId of a paid draw (0x and 64 hex characters).
requestIdstring–A request id this API opened, as a decimal string.

No output schema declared.

No examples provided.

setup_status ~39

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the D20DAO Verifiable Randomness MCP server?

D20DAO Verifiable Randomness is an MCP server listed in the public MCP registry as org.d20dao/vrf. Verifiable dice, draws and shuffles with on-chain VRF proofs on Arc. 0.05 USDC per draw. This page covers its npm package (@d20dao/mcp).

Is the D20DAO Verifiable Randomness MCP server safe to use?

D20DAO Verifiable Randomness scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the D20DAO Verifiable Randomness MCP server expose?

D20DAO Verifiable Randomness exposes 3 tools: draw, get_result, setup_status. Their descriptions and schemas cost roughly 567 tokens of context every time the server is loaded.

Is the D20DAO Verifiable Randomness MCP server still maintained?

D20DAO Verifiable Randomness is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the D20DAO Verifiable Randomness MCP server under?

D20DAO Verifiable Randomness declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.