Fair Random MCP server
com.intoperson.tools/fair-randomtools.intoperson.comstreamable-httpv1.1.0Scanned
Fair, reproducible randomness for agents: dice, coins, integers, list picks, shuffles, with seeds.
6 tools: 5 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Sign-in required, no OAuth metadata. Remote posture
Anlyon alternative
5 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Fair Random MCP server can do
The Fair Random MCP server is published by tools.intoperson.com, a domain the MCP Registry verified. It has 6 tools. It can create or change data (5 tools: roll_dice, flip_coin, random_integer, shuffle_list and 1 more), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Last scanned Oct 27, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 5Claude Code: ask
flip_coinFlip a fair coin 1 to 100 times.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Flip a fair coin 1 to 100 times.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- title: Flip a coin
prismtect_numberA 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Prismtect number (human touch only)
random_integerIntegers from min to max inclusive, 1 to 1000 of them, with or without repeats.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Integers from min to max inclusive, 1 to 1000 of them, with or without repeats. The range may hold at most 2^32 values.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- title: Random integers
roll_diceRoll 1 to 100 dice with 2 to 1000 sides each (default one six-sided die).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Roll 1 to 100 dice with 2 to 1000 sides each (default one six-sided die).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- title: Roll dice
shuffle_listPut up to 1000 items in a random order; every order is equally likely.1 finding
Why it is in this group
- The name "shuffle_list" says "list": a word for reading.
- The description's first verb is "put": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "shuffle_list" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "shuffle_list" says "list": a word for reading.
Description, as the server wrote it Put up to 1000 items in a random order; every order is equally likely.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- title: Shuffle a list
Only reads 1Show 1 read-only tool
pick_from_listPick 1 or more items from a list of up to 1000, each equally likely.No findings
Why it is in this group
- The name "pick_from_list" says "list": a word for reading.
Description, as the server wrote it Pick 1 or more items from a list of up to 1000, each equally likely. Without repeats by default.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- title: Pick from a list
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:40 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 404
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: initialize answered HTTP 404.
Posture changes
- Nov 20, 2026
- HTTP status of an anonymous initialize: 530 to 404
- Nov 13, 2026
- Reachable: no to yes
- HTTP status of an anonymous initialize: none to 530
- Nov 6, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 5 to 0
- Protocol version: 2025-06-18 to none
Findings
Matches of fixed checks, with the text they matched.
- Warnshuffle_list
The server marks "shuffle_list" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "shuffle_list" says "list": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 530 -> 404.View diff
- HTTP status of an anonymous initialize: 530 to 404
PostureRemote posture changed. Reachable: no -> yes; HTTP status of an anonymous initialize: none -> 530.View diff
- Reachable: no to yes
- HTTP status of an anonymous initialize: none to 530
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 2 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 5 to 0
- Protocol version: 2025-06-18 to none
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http fair-random https://tools.intoperson.com/mcp/randomclaude mcp add --transport http fair-random https://tools.intoperson.com/mcp/randomRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__fair-random__pick_from_list"
],
"ask": [
"mcp__fair-random__roll_dice",
"mcp__fair-random__flip_coin",
"mcp__fair-random__random_integer",
"mcp__fair-random__shuffle_list",
"mcp__fair-random__prismtect_number"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as fair-random. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.intoperson.tools/fair-random/verify?hash=3582b614d6376af2516ef7204784757c7a1a05fd8437be7fa170a135f0c40f23" | jq -e '.changed == false'Pinned hash 3582b614d637, from Oct 27, 2026, 06:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.intoperson.tools/fair-random/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.intoperson.tools/fair-random)Source: MCP Registry. Synced Nov 6, 2026, 14:17 UTC.
Fair Random MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Fair Random MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 5 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Fair Random MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Fair Random MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Fair Random MCP server have?
- 6 tools: 5 write, 1 read. roll_dice, flip_coin, random_integer, shuffle_list, prismtect_number and pick_from_list.
Does the Fair Random MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Fair Random MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Fair Random MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 27, 2026.