About fairdraw
fairdraw is an MCP server and CLI for raffle organizers who need draws that anyone can independently verify. It ranks deduplicated entrants using public drand randomness, and supports immediate draws and scheduled reveals.
Key features
- 01Pick winners using drand randomness
- 02Deduplicate and sort entrant lists
- 03Schedule draws for future rounds
- 04Verify scheduled draws by ID
Use cases
- 01Run an immediately verifiable raffle
- 02Commit a draw to a future reveal
- 03Recompute winners after randomness is published
MCP support
It exposes tools to MCP clients for immediate winner selection, scheduling a draw against a future drand round, and verifying scheduled results.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
3Saved tool list · updated 1w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| winners | integer | No | How many winners to pick. Defaults to 1; must be between 1 and the number of entrants. |
| entrants | array | Yes | The entrant names. Duplicates are removed and the list is sorted before ranking. |
Details
From the project READMEfairdraw
A raffle nobody has to take your word for. fairdraw picks winners from the public drand randomness beacon: the winning names are a pure function of a drand round's published randomness and the entrant list, so after a draw anyone can recompute the ranking by hand and check that the announced winners are the ones the beacon actually produced.
How a result is decided:
- The entrant list is deduplicated and sorted.
- Each entrant is scored with
sha256(randomness + "|" + entrant)(hex digest). - Entrants are ranked by score, lowest first — the lowest scores win, in ranked order.
The three tools:
pick_winner_now— draw immediately against the latest drand round and get the winner (or winners) right away, with the round number and the start of the randomness in the result so the draw can be rechecked.create_scheduled_draw— seal a draw to a future reveal. The drand round is committed the instant the draw is created, from the chain's timing: the first round whose randomness becomes available at or afternow + delay_sec. The reply carries a draw id.verify_draw— look a scheduled draw up by id. While its round is still unpublished you get a pending note naming the committed round; once the round is out, you get the winners recomputed from that round's randomness, marked as verified.
Scheduled draws are kept in the server process's memory: they live as long as the process does, and a draw id is only meaningful to the process that created it.
CLI
Each tool is a subcommand taking one JSON argument string:
npx @reneturcios/fairdraw pick_winner_now '{"entrants":["alice","bob","carol"],"winners":2}'
npx @reneturcios/fairdraw create_scheduled_draw '{"title":"Spring raffle","entrants":["alice","bob"],"delay_sec":3600}'
npx @reneturcios/fairdraw verify_draw '{"id":"<draw id>"}'
npx @reneturcios/fairdraw --version
Output is the tool's result text. Exit codes: 0 on
success, 1 on a runtime error (including a validation or
drand failure), 2 on a usage error.
MCP server
npx -y @reneturcios/fairdraw mcp
MCP client config:
{
"mcpServers": {
"fairdraw": {
"command": "npx",
"args": ["-y", "@reneturcios/fairdraw", "mcp"]
}
}
}
Docker
docker run -i ghcr.io/cloudcorprecords/fairdraw
docker run --rm ghcr.io/cloudcorprecords/fairdraw pick_winner_now '{"entrants":["alice","bob"]}'
Development
npm install
npm run build # tsc -> dist/
npm test # tsx --test test/*.test.ts (fake fetch + fake clock, no network)
npm run dev # run the CLI from source
License
MIT — Copyright (c) 2026 Rene Turcios
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.