io.github.terradev-cloud/quorum
REMOTE · QUORUM-MCP.TERRADEV.CLOUD · SCANNED SEP 27
Attested multi-agent consensus: proposals, votes, and outcomes stamped and traced.
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 7 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 Usability72
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 964 tokens (~137/item across 7 items; 7 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 Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 77% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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/quorum MCP server?
io.github.terradev-cloud/quorum is a hosted endpoint at https://quorum-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 · quorum-mcp.terradev.cloud
claude mcp add --transport http terradev-cloud-quorum 'https://quorum-mcp.terradev.cloud/mcp'
{
"mcpServers": {
"terradev-cloud-quorum": {
"url": "https://quorum-mcp.terradev.cloud/mcp"
}
}
} {
"servers": {
"terradev-cloud-quorum": {
"type": "http",
"url": "https://quorum-mcp.terradev.cloud/mcp"
}
}
} [mcp_servers.terradev-cloud-quorum] url = "https://quorum-mcp.terradev.cloud/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"terradev-cloud-quorum": {
"type": "remote",
"url": "https://quorum-mcp.terradev.cloud/mcp",
"enabled": true
}
}
} openclaw mcp add terradev-cloud-quorum --url 'https://quorum-mcp.terradev.cloud/mcp' --transport streamable-http
mcp_servers:
terradev-cloud-quorum:
url: "https://quorum-mcp.terradev.cloud/mcp" {
"McpServers": {
"terradev-cloud-quorum": {
"Transport": "http",
"Url": "https://quorum-mcp.terradev.cloud/mcp"
}
}
} assistant mcp add terradev-cloud-quorum -t streamable-http -u 'https://quorum-mcp.terradev.cloud/mcp'
{
"mcpServers": {
"terradev-cloud-quorum": {
"type": "http",
"url": "https://quorum-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 63
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://quorum-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=quorum-mcp.terradev.cloud | CN=YE1,O=Let's Encrypt,C=US | 18 Sept 2026 | 17 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6dc67194d0eae6f426032409757763b1f8c |
| SANs: quorum-mcp.terradev.cloud | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 quorum-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://quorum-mcp.terradev.cloud/mcp | Verified | 200 | |
| http (plaintext) | http://quorum-mcp.terradev.cloud/mcp | HTTPS enforced | 308 | https://quorum-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 →
history ~62
The complete attested record of a proposal in chronological order: creation, every blackboard write, every vote with reasoning, the outcome. Optional filter: all | writes | votes | outcome.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | Default all. |
| proposal_id | string | yes | – |
No output schema declared.
No examples provided.
propose ~324
Open a new proposal: a question, named options, expected voter identities, an aggregation algorithm, a deadline, and a quorum threshold. Returns the proposal id, the creation attestation, and the deadline. All later operations key off the proposal id.
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm | string | – | Aggregation algorithm. Default approval -- robust general-purpose choice with no strategic incentive. |
| api_key | string | – | Optional. Your Quorum API key (from register). Binds the proposal to your account so its spans push to your Telinea. Omit for anonymous use -- everything works, no spans. |
| deadline_minutes | number | yes | Minutes until voting closes. |
| description | string | – | Optional context for the audit trail. |
| name | string | yes | Human-readable proposal id, e.g. pr-review-2026-09-18. Letters, digits, . _ - only; becomes the key for all subsequent calls. |
| namespace | string | – | Optional tenant namespace. The proposal id becomes '<namespace>:<name>' -- different teams can reuse names without colliding. Same charset as name. |
| options | array | – | Named options. Default ["yes","no"]. |
| question | string | yes | The thing being decided. |
| quorum | number | – | Min percent of expected voters that must vote before resolution. Default 100. |
| threshold | number | – | Supermajority only: required share of votes cast, percent. Default 66.67. |
| voters | array | yes | Expected voter identities. Only these may vote; missing voters at resolution are recorded abstained. |
No output schema declared.
No examples provided.
read ~62
Read a proposal's blackboard: every write in order with timestamp, author, and attestation id -- the complete deliberation record, or filtered to one key.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | – | Optional: only entries with this key. |
| proposal_id | string | yes | – |
No output schema declared.
No examples provided.
register ~224
OPTIONAL one-time setup -- only needed if you want proposal telemetry (OTLP spans) pushed to your Telinea account. Call once before propose: it binds an api_key you choose to your Telinea API key. Afterwards, pass the same api_key on propose and every span for that proposal is pushed to your Telinea with standard OTLP bearer auth. Storage: the Telinea key is sealed with AES-256-GCM under a key derived from your api_key (HKDF-SHA256, per-account salt); only sha256(api_key) is kept as the lookup id, so neither key is ever stored in the clear. Re-registering with the same api_key rotates the stored Telinea key. Skip this tool entirely for anonymous use -- propose works without an api_key, just with no span streaming.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your Quorum API key -- chosen by you, presented on propose, never stored. |
| telinea_key | string | yes | Your Telinea API key -- stored encrypted, used to authenticate span pushes. |
No output schema declared.
No examples provided.
resolve ~67
Compute and attest the outcome once quorum is met (or the deadline has passed). Idempotent: resolving twice returns the recorded outcome. Condorcet cycles and missed supermajority thresholds return co_winners with status unresolved rather than an arbitrary tiebreak.
| Name | Type | Req | Description |
|---|---|---|---|
| proposal_id | string | yes | – |
No output schema declared.
No examples provided.
vote ~136
Submit a vote from an expected voter identity, with optional reasoning stored in the attested record. Vote shape depends on the algorithm: plurality/supermajority take an option string; approval takes an option or list of options; borda takes a ranking of all options; condorcet takes a ranking or a single option; opinion_pool takes a probability distribution over options. Duplicates and post-deadline votes are rejected.
| Name | Type | Req | Description |
|---|---|---|---|
| proposal_id | string | yes | – |
| reasoning | string | – | Free-text rationale, kept in the audit trail. |
| value | – | yes | Ballot in the algorithm's format. |
| voter | string | yes | – |
No output schema declared.
No examples provided.
write ~89
Append a key-value entry to a proposal's blackboard. Any agent may write; writes are appended, never replaced -- the full ordered history is preserved and attested.
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | Optional author identity, recorded and attested. |
| key | string | yes | Key other agents use to filter this entry on read. |
| proposal_id | string | yes | – |
| value | – | yes | Any JSON value. |
No output schema declared.
No examples provided.
What is the io.github.terradev-cloud/quorum MCP server?
io.github.terradev-cloud/quorum is an MCP server listed in the public MCP registry as io.github.terradev-cloud/quorum. Attested multi-agent consensus: proposals, votes, and outcomes stamped and traced. This page covers its hosted endpoint (https://quorum-mcp.terradev.cloud/mcp).
Is the io.github.terradev-cloud/quorum MCP server safe to use?
io.github.terradev-cloud/quorum scores 63 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/quorum MCP server expose?
io.github.terradev-cloud/quorum exposes 7 tools: register, propose, write, read, vote, and 2 more. Their descriptions and schemas cost roughly 964 tokens of context every time the server is loaded.
Does the io.github.terradev-cloud/quorum MCP server require authentication?
No. We connected to io.github.terradev-cloud/quorum without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.terradev-cloud/quorum MCP server still maintained?
io.github.terradev-cloud/quorum 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.