Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.terradev-cloud/quorum

REMOTE · QUORUM-MCP.TERRADEV.CLOUD

Attested multi-agent consensus: proposals, votes, and outcomes stamped and traced.

−77 this week 0 Trust /100

Last scanned (10 days ago)

Scores higher than 0% of remote servers

Unreachable for 7 days in a row. Last reached 4 Nov 2026.

Category Workflow Automation

Dead

Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.

Trust breakdown (7 categories)

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 Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (3)

  • HTTPS
  • DNSSEC
  • Transport

Checks we could not complete (8)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 −15

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 10 Nov 26 −16

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 9 Nov 26 −15

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 8 Nov 26 −16

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 7 Nov 26 −15

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • HSTS header: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 27 Oct 26 0
    • Stability: 0.97 → pass security
Diagnostics

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 11 Nov 2026 · Probed https://quorum-mcp.terradev.cloud/mcp

TLS unreached
DNSSEC insecure

Validation of quorum-mcp.terradev.cloud. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
cloud. DS published 7041 13 Verified
terradev.cloud. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

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 Unreachable
http (plaintext) http://quorum-mcp.terradev.cloud/mcp HTTPS enforced
MCP tools · 7 exposed · ~964 tokens

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 →

Tool Tokens
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.

NameTypeReqDescription
filterstring–Default all.
proposal_idstringyes–

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.

NameTypeReqDescription
algorithmstring–Aggregation algorithm. Default approval -- robust general-purpose choice with no strategic incentive.
api_keystring–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_minutesnumberyesMinutes until voting closes.
descriptionstring–Optional context for the audit trail.
namestringyesHuman-readable proposal id, e.g. pr-review-2026-09-18. Letters, digits, . _ - only; becomes the key for all subsequent calls.
namespacestring–Optional tenant namespace. The proposal id becomes '<namespace>:<name>' -- different teams can reuse names without colliding. Same charset as name.
optionsarray–Named options. Default ["yes","no"].
questionstringyesThe thing being decided.
quorumnumber–Min percent of expected voters that must vote before resolution. Default 100.
thresholdnumber–Supermajority only: required share of votes cast, percent. Default 66.67.
votersarrayyesExpected 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.

NameTypeReqDescription
keystring–Optional: only entries with this key.
proposal_idstringyes–

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.

NameTypeReqDescription
api_keystringyesYour Quorum API key -- chosen by you, presented on propose, never stored.
telinea_keystringyesYour 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.

NameTypeReqDescription
proposal_idstringyes–

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.

NameTypeReqDescription
proposal_idstringyes–
reasoningstring–Free-text rationale, kept in the audit trail.
value–yesBallot in the algorithm's format.
voterstringyes–

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.

NameTypeReqDescription
authorstring–Optional author identity, recorded and attested.
keystringyesKey other agents use to filter this entry on read.
proposal_idstringyes–
value–yesAny JSON value.

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http terradev-cloud-quorum 'https://quorum-mcp.terradev.cloud/mcp'
Common questions

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 0 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?

Its publisher declares no required credentials for io.github.terradev-cloud/quorum. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the io.github.terradev-cloud/quorum MCP server still maintained?

io.github.terradev-cloud/quorum has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.terradev-cloud/quorum MCP server?

VerifyMCP ran 3 checks on io.github.terradev-cloud/quorum, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about io.github.terradev-cloud/quorum: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.