Diceport

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Oct 29, 2026

Dice rolls, coin flips, and random numbers, reproducible with a seed.

VerifiedSTDIODesktop only

Overview

AI-generated overview

Local MCP server that rolls dice, flips coins and picks random integers, optionally seeded so results are reproducible.

What you can do
  • Roll dice in NdM notation, returning each face, the modifier and the total
  • Flip a coin and get heads or tails
  • Pick a random integer between two inclusive bounds
  • Replay any result by passing an optional integer seed
When to use it
Useful when an assistant needs a fair, explainable bit of chance — tabletop or game logic, picking a random item, or generating a verifiable random outcome that can be replayed later with the same seed.
Requirements
Runs as a local stdio process, started with npx from the npm package or from the container image; Node.js is needed for the npx route and Docker for the container route. No accounts, API keys, environment variables or headers are declared.
Before you install
Unseeded calls use the platform random source, so they are not cryptographically guaranteed; seeded calls are fully deterministic and predictable, so do not use them for security-sensitive randomness. The server only returns values and does not write or send data.

Installation

In SourceWeft

  1. Open Diceport in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

diceport

diceport rolls dice, flips coins, and picks random integers. It is built for the moments when a script or an agent needs a fair, explainable bit of chance: a roll reports every face that went into its total, and any call can take a seed that makes the outcome reproducible — same seed, same result, every time.

Install

bash
npx @reneturcios/diceport roll 2d6

Or run the container image:

bash
docker run -i ghcr.io/cloudcorprecords/diceport

The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.

CLI

bash
# Roll dice in NdM notation, with an optional +N / -N modifierdiceport roll 2d6# 2d6: [3, 5] total 8diceport roll 3d8+2 --seed 42   # reproducible
# Flip a coindiceport flip                   # heads (or tails)diceport flip --seed 7 --json
# Pick an integer between two bounds, inclusivediceport random 1 100diceport random 1 100 --seed 42
diceport --version

Notation is NdM: roll N dice with M sides each. The count may be left off (d20 rolls one die) and a flat modifier may be appended (2d6+3, 1d100-5).

Exit codes: 0 on success, 1 when a roll or range cannot be done (bad notation, an inverted range — the error says why), 2 for usage errors.

MCP server

One bin serves both faces. The mcp subcommand starts a stdio MCP server:

bash
npx -y @reneturcios/diceport mcp

MCP client configuration:

json
{  "mcpServers": {    "diceport": {      "command": "npx",      "args": ["-y", "@reneturcios/diceport", "mcp"]    }  }}

Tools

ToolInputWhat it returns
roll_dicenotation (string, required, e.g. 2d6+3), seed (integer, optional)Every individual face rolled, the modifier, and the total.
flip_coinseed (integer, optional)heads or tails.
random_numbermin, max (integers, required), seed (integer, optional)One integer between min and max, inclusive.

Seeded calls use a mulberry32 generator, so a seed fully determines the outcome and any reported result can be replayed. Unseeded calls draw from the platform random source.

Development

bash
npm installnpm run build   # tsc -> dist/npm test        # node test runner over test/*.test.ts, no networknpm run dev     # run the CLI from source via tsx

License

MIT — see LICENSE.

Source: README.md at commit 1711e46

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestOct 29, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts