Fair Random
REMOTE · DRAWSTODAY.COM
Fair, reproducible randomness for agents: dice, coins, integers, list picks, shuffles, with seeds.
Available components
Last scanned (7 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 5 Nov 2026.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 795 tokens (~132/item across 6 items; 6 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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage77
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 31% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 4 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.
- 2 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 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “flip_coin” rewrote its description, which is the text the model reads security
- Tool “pick_from_list” rewrote its description, which is the text the model reads security
- Tool “random_integer” rewrote its description, which is the text the model reads security
- Tool “roll_dice” rewrote its description, which is the text the model reads security
- Tool “shuffle_list” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- “flip_coin” reworded the description of “seed” cosmetic
- “pick_from_list” reworded the description of “seed” cosmetic
- “random_integer” reworded the description of “seed” cosmetic
- “roll_dice” reworded the description of “seed” cosmetic
- “shuffle_list” reworded the description of “seed” cosmetic
- 31 Oct 26 64
First indexed and scored.
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 · Probed https://drawstoday.com/mcp/random
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=drawstoday.com | CN=YE1,O=Let's Encrypt,C=US | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6d2740409b53bcc18f0c53280585cd4cb1b |
| SANs: *.drawstoday.com, drawstoday.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of drawstoday.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| drawstoday.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://drawstoday.com/mcp/random | Verified | 200 | |
| http (plaintext) | http://drawstoday.com/mcp/random | Inconclusive | 405 |
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 →
flip_coin Flip a coin ~93
Flip a fair coin 1 to 100 times. The answer is a drawstoday.com link where the result is shown; the answer itself carries no result.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| seed | string | – | Optional. 64 hex characters. Give the seed shown on an earlier result page to get the same result again (that is how a draw is checked). Leave it out for a fresh draw. |
No output schema declared.
No examples provided.
pick_from_list Pick from a list ~122
Pick 1 or more items from a list of up to 1000, each equally likely. Without repeats by default. The answer is a drawstoday.com link where the result is shown; the answer itself carries no result.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| items | array | yes | – |
| seed | string | – | Optional. 64 hex characters. Give the seed shown on an earlier result page to get the same result again (that is how a draw is checked). Leave it out for a fresh draw. |
| unique | boolean | – | – |
No output schema declared.
No examples provided.
prismtect_number Prismtect number (human touch only) ~71
A personal two-digit number from the Prismtect glass prism, for a user who asks for a lucky number, a number of their own or a number for today. Only a human touch can draw it, so this tool gives no number: it gives the link your user taps themselves. Pass the link on.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
random_integer Random integers ~137
Integers from min to max inclusive, 1 to 1000 of them, with or without repeats. The range may hold at most 2^32 values. The answer is a drawstoday.com link where the result is shown; the answer itself carries no result.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| max | integer | yes | – |
| min | integer | yes | – |
| seed | string | – | Optional. 64 hex characters. Give the seed shown on an earlier result page to get the same result again (that is how a draw is checked). Leave it out for a fresh draw. |
| unique | boolean | – | – |
No output schema declared.
No examples provided.
roll_dice Roll dice ~113
Roll 1 to 100 dice with 2 to 1000 sides each (default one six-sided die). The answer is a drawstoday.com link where the result is shown; the answer itself carries no result.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| seed | string | – | Optional. 64 hex characters. Give the seed shown on an earlier result page to get the same result again (that is how a draw is checked). Leave it out for a fresh draw. |
| sides | integer | – | – |
No output schema declared.
No examples provided.
shuffle_list Shuffle a list ~100
Put up to 1000 items in a random order; every order is equally likely. The answer is a drawstoday.com link where the result is shown; the answer itself carries no result.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| seed | string | – | Optional. 64 hex characters. Give the seed shown on an earlier result page to get the same result again (that is how a draw is checked). Leave it out for a fresh draw. |
No output schema declared.
No examples provided.
How do I install the Fair Random MCP server?
Fair Random is a hosted endpoint at https://drawstoday.com/mcp/random, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · drawstoday.com
claude mcp add --transport http com-drawstoday-fair-random 'https://drawstoday.com/mcp/random'
What is the Fair Random MCP server?
Fair Random is an MCP server listed in the public MCP registry as com.drawstoday/fair-random. Fair, reproducible randomness for agents: dice, coins, integers, list picks, shuffles, with seeds. This page covers its hosted endpoint (https://drawstoday.com/mcp/random).
Is the Fair Random MCP server safe to use?
Fair Random scores 66 out of 100 on VerifyMCP. 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 Fair Random MCP server expose?
Fair Random exposes 6 tools: roll_dice, flip_coin, random_integer, pick_from_list, shuffle_list, prismtect_number. Their descriptions and schemas cost roughly 636 tokens of context every time the server is loaded.
Does the Fair Random MCP server require authentication?
No. We connected to Fair Random without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Fair Random MCP server still maintained?
Fair Random 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 did VerifyMCP test on the Fair Random MCP server?
VerifyMCP ran 12 checks on Fair Random, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Fair Random: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.