mcpbeat Sign in

TrueRandomness MCP Server

by cipshadow Your server? Claim it
not responding

TrueRandomness is listed as active in the registry but did not answer our last check. It exposes 3 tools.

Verified random integers via free MCP tools, plus Tempo-paid signed random certificates.

Uptime history 36 days of history · worst day 0%
36 days agonow
0.0%
Uptime 24h
0 of 91 checks
3
Tools
read from the server
186 ms
Response time
average over 24h
open, no key
Access
streamable-http

TrueRandomness does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add truerandomness --transport http https://random.cipblujdea.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://random.cipblujdea.com/mcp
~/.codex/config.toml
[mcp_servers.truerandomness]
url = "https://random.cipblujdea.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "truerandomness": {
      "url": "https://random.cipblujdea.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "truerandomness": {
      "type": "http",
      "url": "https://random.cipblujdea.com/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

random
random_int
Return a uniformly distributed random integer in [min, max], derived from a signature-verified drand quicknet beacon mixed with a server secret and, when a public KiwiSDR receiver delivers one, a hash of live HF atmospheric noise. The response carries the drand round, the beacon signature, a per-request nonce, a commitment hash binding them to the value, a URL where the round can be re-verified, and a `physical` block stating whether noise went in and from where. Free and rate-limited.
random_int_signed
Return a uniformly distributed random integer in [min, max] with the same drand quicknet provenance as random_int, plus a payment receipt. Costs $0.01 per call in stablecoin over the Machine Payments Protocol. New unpaid challenge requests are safety-limited. An unpaid call answers with a payment challenge (JSON-RPC -32042); a client that cannot pay should use random_int instead.
status
status
Report service and beacon health: the current drand quicknet round, which relay answered, the rate-limiter mode, and whether the last draw obtained live atmospheric noise. Free, and does not consume rate limit.

Endpoints

URLTransportStateLatencyChecked
https://random.cipblujdea.com/mcp streamable-http answering 186 ms 11 min ago

Alternatives to TrueRandomness

same job, measured the same way
Eth Legion
by liren001

Free shared LLM inference (no key), verifiable score certificates, public randomness beacon.

8 tools answering
costheta
by costheta

Verifiable physical randomness from cosmic-ray detections. Free beacon, paid signed decisions.

3 tools answering
A
Agent Record
by llpro-agentrecord

Daily signed census of which MCP tools work, plus a delivery record. Free. No paid ranking.

5 tools answering
Paceproof
by rudrendupaul

Verifies Ed25519-signed attestation records and builds audit reports via MCP tools.

57 installs/wk local only
Policyrecall
by cloudcorprecords

Policy-verified recall and calibration for tool calls via signed operational memory.

274 installs/wk local only
Agent Guild
by agenttanuki

Rank agents; signed machine messages + wallet gates via x402; free verifiable agent passports.

44 tools answering
Slipway
by qompass

Android build/sign/verify/install/release MCP server with measured certification gates.

local only
LION Trend Intent MCP
by lionmaster20

Read-only x402-paid trend-intent MCP tools for JSON and CSV signals.

5 tools answering

TrueRandomness — questions

Answers built from our own checks of this server.

What can TrueRandomness do?
It exposes 3 tools, read directly from the server on our last check. Among them: random_int, random_int_signed, status. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is TrueRandomness working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 186 ms. The bar chart above shows every period we have measured.
The registry lists TrueRandomness as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect TrueRandomness?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does TrueRandomness need an API key?
No. TrueRandomness completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.