entropy MCP server
io.github.terradev-cloud/entropyterradev-cloudstreamable-httpv0.1.1Scanned
Cryptographically sound randomness for agents, with verifiable commit-reveal.
4 tools: 4 change things.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
4 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 entropy MCP server can do
The entropy MCP server is published by the GitHub account terradev-cloud. It has 4 tools. It can create or change data (4 tools: random, commitment, test and explore), but cannot delete data. None of its tools only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 21, 2026, version 0.1.1.
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.
4 tools
Changes things 4Claude Code: ask
commitmentVerifiable commit-reveal.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.
Description, as the server wrote it Verifiable commit-reveal. operation selects the step: commit -- hash a seed, bind it to draw_spec {operation, params}, attest via Stamp. The seed is returned to the caller and never stored. reveal -- verify a seed against commitment_id, re-execute the draw deterministically, attest the outcome. draw -- commit + execute + reveal in one call. Pass draw_spec, or operation + params directly. verify -- pure third-party verification of commitment_record + reveal_record. No local state. list -- read-only view of the local commitment log (limit, since).
exploreBandit arm selection: epsilon_greedy, thompson, or ucb1.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.
Description, as the server wrote it Bandit arm selection: epsilon_greedy, thompson, or ucb1. Stateless -- caller passes state in as {arm: {pulls, successes, total_reward}} and gets a selection back. params: {epsilon} for epsilon_greedy.
randomDirect randomness.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.
Description, as the server wrote it Direct randomness. operation selects the primitive: bytes -- raw CSPRNG bytes. params: {count<=4096, encoding: hex|base64} int -- unbiased integers in [min,max] via rejection sampling. params: {min, max, count<=10000} shuffle -- Fisher-Yates; permutation[i] is the original index now at position i. params: {items, return_permutation} choose -- k items, weighted or not, with/without replacement. params: {items, k, weights, replacement} sample -- named distributions: uniform, normal, lognormal, exponential, triangular, beta. params: {distribution, params, n<=10000} constrained -- records with independently sampled attributes + chi-squared conformance proof. params: {attributes: {attr: {value: prop}}, n} seed (top level) makes any operation reproducible.
testStatistical battery over a sequence: frequency, chi-squared, runs, longest run, serial correlation, Shannon entropy, KS, gap test.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.
Description, as the server wrote it Statistical battery over a sequence: frequency, chi-squared, runs, longest run, serial correlation, Shannon entropy, KS, gap test. Informed by NIST SP 800-22; no certification claimed. sequence is a list of numbers, list of strings, or a hex/base64 byte string.
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, 19:11 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- 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: The operation was aborted due to timeout
Posture changes
- 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: 4 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://entropy-mcp.terradev.cloud/.well-known/oauth-protected-resource/mcp to none
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 3 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: 4 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://entropy-mcp.terradev.cloud/.well-known/oauth-protected-resource/mcp to none
Install
Pinned to version 0.1.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http entropy https://entropy-mcp.terradev.cloud/mcpclaude mcp add --transport http entropy https://entropy-mcp.terradev.cloud/mcpRun 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": [],
"ask": [
"mcp__entropy__random",
"mcp__entropy__commitment",
"mcp__entropy__test",
"mcp__entropy__explore"
],
"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 entropy. 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/io.github.terradev-cloud/entropy/verify?hash=805d74796db5a839e59183783c6f1c64e2a668afda3329cbccfff9a2f2629973" | jq -e '.changed == false'Pinned hash 805d74796db5, from Oct 21, 2026, 19:28 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.terradev-cloud/entropy/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.terradev-cloud/entropy)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:50 UTC.
entropy MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the entropy MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the entropy MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the entropy 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 entropy MCP server have?
- 4 tools: 4 write. random, commitment, test and explore.
Does the entropy MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the entropy MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the entropy MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 21, 2026.