io.github.terradev-cloud/entropy
REMOTE · ENTROPY-MCP.TERRADEV.CLOUD · SCANNED SEP 27
Cryptographically sound randomness for agents, with verifiable commit-reveal.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 716 tokens (~179/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage77
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 31% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the io.github.terradev-cloud/entropy MCP server?
io.github.terradev-cloud/entropy is a hosted endpoint at https://entropy-mcp.terradev.cloud/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · entropy-mcp.terradev.cloud
claude mcp add --transport http terradev-cloud-entropy 'https://entropy-mcp.terradev.cloud/mcp'
{
"mcpServers": {
"terradev-cloud-entropy": {
"url": "https://entropy-mcp.terradev.cloud/mcp"
}
}
} {
"servers": {
"terradev-cloud-entropy": {
"type": "http",
"url": "https://entropy-mcp.terradev.cloud/mcp"
}
}
} [mcp_servers.terradev-cloud-entropy] url = "https://entropy-mcp.terradev.cloud/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"terradev-cloud-entropy": {
"type": "remote",
"url": "https://entropy-mcp.terradev.cloud/mcp",
"enabled": true
}
}
} openclaw mcp add terradev-cloud-entropy --url 'https://entropy-mcp.terradev.cloud/mcp' --transport streamable-http
mcp_servers:
terradev-cloud-entropy:
url: "https://entropy-mcp.terradev.cloud/mcp" {
"McpServers": {
"terradev-cloud-entropy": {
"Transport": "http",
"Url": "https://entropy-mcp.terradev.cloud/mcp"
}
}
} assistant mcp add terradev-cloud-entropy -t streamable-http -u 'https://entropy-mcp.terradev.cloud/mcp'
{
"mcpServers": {
"terradev-cloud-entropy": {
"type": "http",
"url": "https://entropy-mcp.terradev.cloud/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 27 Sept 26 60
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://entropy-mcp.terradev.cloud/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=entropy-mcp.terradev.cloud | CN=YE2,O=Let's Encrypt,C=US | 12 Sept 2026 | 11 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6c568b5abd2e7aae148136644ccd4828ed1 |
| SANs: entropy-mcp.terradev.cloud | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of entropy-mcp.terradev.cloud. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cloud. | present | 7041 | 13 | Verified |
| terradev.cloud. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://entropy-mcp.terradev.cloud/mcp | Verified | 200 | |
| http (plaintext) | http://entropy-mcp.terradev.cloud/mcp | HTTPS enforced | 308 | https://entropy-mcp.terradev.cloud/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
commitment ~226
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).
| Name | Type | Req | Description |
|---|---|---|---|
| anchor_beacon | boolean | – | – |
| attested | boolean | – | – |
| commitment_id | string | – | – |
| commitment_record | object | – | – |
| description | string | – | – |
| draw_spec | object | – | {operation, params} for commit/draw |
| limit | integer | – | – |
| operation | string | yes | – |
| reveal_record | object | – | – |
| seed | string | – | – |
| since | string | – | ISO 8601 lower bound |
No output schema declared.
No examples provided.
explore ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| arms | array | yes | – |
| params | object | – | – |
| seed | string | – | – |
| state | object | – | – |
| strategy | string | yes | – |
No output schema declared.
No examples provided.
random ~228
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.
| Name | Type | Req | Description |
|---|---|---|---|
| operation | string | yes | – |
| params | object | – | operation-specific arguments |
| seed | string | – | optional seed for a reproducible draw |
No output schema declared.
No examples provided.
test ~165
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.
| Name | Type | Req | Description |
|---|---|---|---|
| alpha | number | – | – |
| dist_params | object | – | – |
| distribution | string | – | enables the KS test |
| expected | object | – | {symbol: probability} for chi_squared |
| input_type | string | – | – |
| sequence | – | yes | list of numbers, list of strings, or hex/base64 |
| tests | – | – | 'all' or a list of: frequency, chi_squared, runs, longest_run, serial, entropy, ks, gap |
No output schema declared.
No examples provided.
What is the io.github.terradev-cloud/entropy MCP server?
io.github.terradev-cloud/entropy is an MCP server listed in the public MCP registry as io.github.terradev-cloud/entropy. Cryptographically sound randomness for agents, with verifiable commit-reveal. This page covers its hosted endpoint (https://entropy-mcp.terradev.cloud/mcp).
Is the io.github.terradev-cloud/entropy MCP server safe to use?
io.github.terradev-cloud/entropy scores 60 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.terradev-cloud/entropy MCP server expose?
io.github.terradev-cloud/entropy exposes 4 tools: random, commitment, test, explore. Their descriptions and schemas cost roughly 716 tokens of context every time the server is loaded.
Does the io.github.terradev-cloud/entropy MCP server require authentication?
No. We connected to io.github.terradev-cloud/entropy without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.terradev-cloud/entropy MCP server still maintained?
io.github.terradev-cloud/entropy is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.