# io.github.terradev-cloud/quorum (remote · quorum-mcp.terradev.cloud)

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

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-27

## Components

- remote · `quorum-mcp.terradev.cloud`: 63/100 (this document), [markdown](https://verifymcp.io/servers/terradev-cloud-quorum/quorum-mcp.md), [page](https://verifymcp.io/servers/terradev-cloud-quorum/quorum-mcp)

## Channel facts

- Endpoint: `https://quorum-mcp.terradev.cloud/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-27.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 77% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## 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.

### Claude

```bash
claude mcp add --transport http terradev-cloud-quorum 'https://quorum-mcp.terradev.cloud/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "terradev-cloud-quorum": {
      "url": "https://quorum-mcp.terradev.cloud/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "terradev-cloud-quorum": {
      "type": "http",
      "url": "https://quorum-mcp.terradev.cloud/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.terradev-cloud-quorum]
url = "https://quorum-mcp.terradev.cloud/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "terradev-cloud-quorum": {
      "type": "remote",
      "url": "https://quorum-mcp.terradev.cloud/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add terradev-cloud-quorum --url 'https://quorum-mcp.terradev.cloud/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  terradev-cloud-quorum:
    url: "https://quorum-mcp.terradev.cloud/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "terradev-cloud-quorum": {
      "Transport": "http",
      "Url": "https://quorum-mcp.terradev.cloud/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add terradev-cloud-quorum -t streamable-http -u 'https://quorum-mcp.terradev.cloud/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-27 (score 63)

First indexed and scored.

## MCP tools (7)

### `register` (~224 tokens)

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.

Input parameters:

- `api_key` (string, required): Your Quorum API key -- chosen by you, presented on propose, never stored.
- `telinea_key` (string, required): Your Telinea API key -- stored encrypted, used to authenticate span pushes.

### `propose` (~324 tokens)

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.

Input parameters:

- `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, required): Minutes until voting closes.
- `description` (string): Optional context for the audit trail.
- `name` (string, required): 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, required): 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, required): Expected voter identities. Only these may vote; missing voters at resolution are recorded abstained.

### `write` (~89 tokens)

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.

Input parameters:

- `author` (string): Optional author identity, recorded and attested.
- `key` (string, required): Key other agents use to filter this entry on read.
- `proposal_id` (string, required)
- `value` (required): Any JSON value.

### `read` (~62 tokens)

Read a proposal's blackboard: every write in order with timestamp, author, and attestation id -- the complete deliberation record, or filtered to one key.

Input parameters:

- `key` (string): Optional: only entries with this key.
- `proposal_id` (string, required)

### `vote` (~136 tokens)

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.

Input parameters:

- `proposal_id` (string, required)
- `reasoning` (string): Free-text rationale, kept in the audit trail.
- `value` (required): Ballot in the algorithm's format.
- `voter` (string, required)

### `resolve` (~67 tokens)

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.

Input parameters:

- `proposal_id` (string, required)

### `history` (~62 tokens)

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.

Input parameters:

- `filter` (string): Default all.
- `proposal_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/terradev-cloud-quorum/quorum-mcp#diagnostics

## Score history

- 2026-09-27: 63

## 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 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.

## Links

- Remote endpoint: https://quorum-mcp.terradev.cloud/mcp
- Repository: https://github.com/terradev-cloud/quorum-mcp
- Changelog RSS feed: https://verifymcp.io/servers/terradev-cloud-quorum/quorum-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/terradev-cloud-quorum/quorum-mcp.json
- HTML version of this page: https://verifymcp.io/servers/terradev-cloud-quorum/quorum-mcp