
Fairdraw
io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026
Provably fair raffle draws: winners picked from public drand randomness, verifiable by anyone.
Overview
Fairdraw's local MCP server; no sign-in required; STDIO.
No AI overview yet: these facts come from the registry entry and the server itself.
Installation
In SourceWeft
- Open Fairdraw in the dashboard and add it to a workspace.
- 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
fairdraw
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:
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
MCP client config:
Docker
Development
License
MIT — Copyright (c) 2026 Rene Turcios
Source: README.md at commit a293067
Tools
0Version history
1- v0.1.0LatestNov 3, 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