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.

Dice Roller

NPM · @PIPEWORX/MCP-DICE-ROLLER · 2 COMPONENTS

dice-roller — tabletop dice, coin flips and exact dice odds on the Pipeworx chance engine…

81 Trust /100

Last scanned (3 hours ago)

Scores higher than 68% of npm servers

Category Entertainment and Games

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
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-dice-roller). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 754 tokens (~251/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 Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 79

    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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-dice-roller@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-dice-roller
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-dice-roller/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3617511210
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:2377e711cb993db0be8729d825a4ea489ae7125e525edac9e6653fbf5bbdeb369c509457ed93d20fbd09c6a3cf9a6e2d823180e0709404e8c274c767e

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~699 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
dice_odds ~274

Pipeworx dice engine: the probability distribution of a dice notation (same grammar as roll_dice: 2d6+3, 4d6kh3, 2d20kl1, 4dF, 3d6!) — min, max, mean, standard deviation, mode, the probability of every total and, given `target`, the chance the total is >=, >, <=, < or == that target (e.g. "what are the odds of 15 or more on 3d6"). Exact by enumeration where the outcomes can be enumerated (plain sums, and keep/drop pools up to 1,000,000 outcomes); otherwise a 100,000-sample Monte Carlo estimate labelled method:"monte_carlo" (exploding dice always use it). `seed` makes a Monte Carlo estimate reproducible.

NameTypeReqDescription
comparisonstring–How the total is compared with target (default ">=").
notationstringyesDice notation, e.g. "3d6", "4d6kh3", "2d20kh1+5".
seedstring–Optional seed for the Monte Carlo path; exact results ignore it. Always returned.
targetnumber–Optional target total to compute a probability for.

No output schema declared.

No examples provided.

flip_coins ~133

Pipeworx dice engine: flip fair coins with real randomness — up to 1,000 per call. Returns the sequence (H/T), heads and tails counts, and the longest run. Omit `seed` for fresh flips; pass the returned `seed` to reproduce them exactly. The outcome is random — the calling agent decides what it means.

NameTypeReqDescription
countinteger–Number of coins to flip (default 1, max 1000).
seedstring–Optional seed. Same seed + same count = same flips. Omit for fresh flips; the seed used is always returned.

No output schema declared.

No examples provided.

roll_dice ~292

Pipeworx dice engine: roll tabletop dice notation with real randomness — NdS terms joined by + or - (2d6+1d4+3, 1d20-2), keep/drop (4d6kh3, 2d20kl1 for disadvantage, 4d6dl1), exploding dice (3d6!), fudge/Fate dice (4dF) and percentile (d% or d100). Up to 1,000 dice and 10,000 sides. Returns every die rolled, which dice were kept, per-term subtotals, the total and a readable breakdown; `times` repeats the roll (up to 100) and adds min/max/mean. Omit `seed` for a fresh roll; pass the returned `seed` to reproduce it exactly. The outcome is random — the calling agent decides what it means.

NameTypeReqDescription
notationstringyesDice notation, e.g. "2d6+3", "4d6kh3", "2d20kl1", "d%", "4dF", "3d6!".
seedstring–Optional seed. Same seed + same arguments = same result. Omit for a fresh random roll; the seed used is always returned.
timesinteger–How many times to roll the whole notation (default 1, max 100).

No output schema declared.

No examples provided.

Install

How do I install the Dice Roller MCP server?

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

npm · @pipeworx/mcp-dice-roller

# add to Claude Code
claude mcp add pipeworx-io-dice-roller -- npx -y @pipeworx/mcp-dice-roller
Common questions

What is the Dice Roller MCP server?

Dice Roller is an MCP server listed in the public MCP registry as io.github.pipeworx-io/dice-roller. dice-roller, tabletop dice, coin flips and exact dice odds on the Pipeworx chance engine… This page covers its npm package (@pipeworx/mcp-dice-roller).

Is the Dice Roller MCP server safe to use?

Dice Roller scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Dice Roller MCP server expose?

Dice Roller exposes 3 tools: roll_dice, flip_coins, dice_odds. Their descriptions and schemas cost roughly 699 tokens of context every time the server is loaded.

Is the Dice Roller MCP server still maintained?

Dice Roller is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Dice Roller MCP server under?

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