Remote MCP · Endpoint

Fair Random MCP server

Yes, as of 19 minutes ago: the server returned an HTTP error.

DownLast checked 19 minutes ago

Server URL

https://tools.intoperson.com/mcp/random

The last check failed: the server returned an HTTP error.

Registry name
com.intoperson.tools/fair-random
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
6 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Fair, reproducible randomness for agents: dice, coins, integers, list picks, shuffles, with seeds.
Listing
From the official MCP registry (deprecated).
Recent checks of Fair Random
CheckedResultHandshake
19 minutes agoFailed - the server returned an HTTP error—
10 days agoHandshake completed638 ms
10 days agoHandshake completed652 ms
11 days agoHandshake completed688 ms
13 days agoHandshake completed657 ms
14 days agoHandshake completed668 ms
14 days agoHandshake completed652 ms
15 days agoHandshake completed672 ms
17 days agoHandshake completed708 ms
19 days agoHandshake completed704 ms
21 days agoHandshake completed821 ms
24 days agoHandshake completed607 ms
26 days agoHandshake completed757 ms
28 days agoHandshake completed764 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Fair Random and makes no claim about it beyond what these checks measured.