Remote MCP · Endpoint

Fair Random MCP server

Yes, as of 15 hours ago: the server returned an HTTP error.

DownLast checked 15 hours ago

Server URL

https://hanaprism.com/mcp/random

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

Registry name
com.hanaprism/fair-random
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
6 tools
Uptime, last 30 days
70.0% from 10 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
15 hours agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
7 days agoFailed - the server returned an HTTP error—
16 days agoHandshake completed690 ms
17 days agoHandshake completed657 ms
19 days agoHandshake completed655 ms
20 days agoHandshake completed611 ms
21 days agoHandshake completed623 ms
22 days agoHandshake completed650 ms
22 days agoHandshake completed705 ms

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

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.