# Parley (pypi · parley-consensus)

Multi-party decisions for agents: red lines rejected in code, max-min pick, SHA-256 receipt. Stdlib.

- Trust score: 85/100 (high trust)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- pypi · `parley-consensus`: 85/100 (this document), [markdown](https://verifymcp.io/servers/5uper0-parley/parley-consensus.md), [page](https://verifymcp.io/servers/5uper0-parley/parley-consensus)

## Channel facts

- Registry: `pypi`
- Package: `parley-consensus`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-10-17.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to 5uper0/parley).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 19 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 817 tokens (~272/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Parley MCP server?

Parley runs locally as a PyPI package, launched with uvx parley-consensus. 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 5uper0-parley -- uvx parley-consensus
```

### Cursor

```json
{
  "mcpServers": {
    "5uper0-parley": {
      "command": "uvx",
      "args": [
        "parley-consensus"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "5uper0-parley": {
      "command": "uvx",
      "args": [
        "parley-consensus"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add 5uper0-parley -- uvx parley-consensus
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "5uper0-parley": {
      "type": "local",
      "command": [
        "uvx",
        "parley-consensus"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add 5uper0-parley --command uvx --arg parley-consensus
```

### Hermes

```yaml
mcp_servers:
  5uper0-parley:
    command: "uvx"
    args: ["parley-consensus"]
```

### Netclaw

```json
{
  "McpServers": {
    "5uper0-parley": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "parley-consensus"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add 5uper0-parley -t stdio -c uvx -a parley-consensus
```

### Other

```json
{
  "mcpServers": {
    "5uper0-parley": {
      "command": "uvx",
      "args": [
        "parley-consensus"
      ]
    }
  }
}
```

## 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-10-16 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 84, +5)

- [functional improvement] Stability: unverified → 0.37

### 2026-10-04 (score 79, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-03 (score 64)

First indexed and scored.

## MCP tools (3)

### `parley_decide` (~337 tokens)

Reach a decision among parties with conflicting interests. Give the options and each party's red lines (hard constraints, checked in code) and soft preferences. An option that crosses any party's red line is rejected outright; among the options acceptable to everyone the max-min rule picks the one whose least-satisfied party is best off, tie-broken by total score. No option acceptable to all parties yields an honest status 'deadlock' with decision null, never a forced choice. Returns JSON: status ('agreed'|'deadlock'), decision (the winning option object or null), transcript (every option with each party's masked verdict), and transcript_sha256 (the receipt hash; keep it to verify the transcript later with parley_verify_receipt). HONESTY NOTE: in this mode you, the caller, hold every party's spec and pass them all in one call, so there is no privacy between parties or from you. What still holds: red lines reject an option deterministically (a violating option cannot win), the max-min rule picks among options feasible for everyone, and the returned transcript is tamper-evident via transcript_sha256, provided the hash is kept by someone other than whoever might edit the transcript (it is unsigned and this server does not store it). For private sheets run one process per owner: examples/run_env.py.

Input parameters:

- `rule` (string): Selection rule. Only 'egalitarian' (max-min) exists.
- `spec` (object, required): A DecisionSpec: the shared options plus every party's position, the same JSON as examples/demo/recipe_*.json. Extra keys are ignored.

### `parley_verify_receipt` (~329 tokens)

Two independent checks on a transcript from parley_decide. Returns JSON: match, max_min_verified, expected_sha256, recomputed_sha256. match=true means only that this transcript hashes to the sha256 you passed. The hash is unsigned and this server does not store it, so if the transcript and the hash come from the same party, match proves nothing: whoever edits the record can re-hash it. It detects tampering only when the hash was kept by someone other than whoever could edit the transcript. max_min_verified recomputes the decision from the recorded verdicts: true when the announced result is exactly the max-min option over them (or an honest deadlock), false when the announced winner does not follow from the recorded verdicts. Verdicts are unsigned, so whoever can rewrite the record can rewrite them to fit a swapped winner; only a hash kept by another party, or signed verdicts, rules that out. It needs every entry to carry exactly one verdict per owner. Pass expected_owners (the roster you know took part) so a record missing a whole owner also fails; that roster is only as trustworthy as where you got it. A malformed transcript is a tool error, not a mismatch.

Input parameters:

- `expected_owners` (array): Optional. The owners you know took part; every entry must carry exactly this set for max_min_verified to be true.
- `sha256` (string, required): The transcript_sha256 you were given, hex.
- `transcript` (object, required): The `transcript` object returned by parley_decide, unmodified.

### `parley_check_party` (~151 tokens)

Replay one party's red lines against a decision: did the outcome cross any of them? Pass the party's spec (the same object you would put in parley_decide's parties) and the decision object returned by parley_decide. Returns JSON: owner and holds (true when every red line of that party holds on the decision). A null decision (deadlock) forces nothing on anyone, so holds is true. Soft preferences are not judged here, only red lines.

Input parameters:

- `decision` (object|null, required): The decision from parley_decide, or null for a deadlock.
- `party` (object, required): One party: a distinct owner name, hard red lines, soft utility terms.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/5uper0-parley/parley-consensus#diagnostics

## Score history

- 2026-10-17: 85
- 2026-10-16: 85
- 2026-10-15: 84
- 2026-10-14: 84
- 2026-10-13: 79
- 2026-10-12: 79
- 2026-10-04: 79
- 2026-10-03: 64

## Common questions

### What is the Parley MCP server?

Parley is an MCP server listed in the public MCP registry as io.github.5uper0/parley. Multi-party decisions for agents: red lines rejected in code, max-min pick, SHA-256 receipt. Stdlib. This page covers its PyPI package (parley-consensus).

### Is the Parley MCP server safe to use?

Parley scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. Its build provenance is signed and verified. 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 Parley MCP server expose?

Parley exposes 3 tools: parley_decide, parley_verify_receipt, parley_check_party. Their descriptions and schemas cost roughly 817 tokens of context every time the server is loaded.

### Is the Parley MCP server still maintained?

Parley is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Parley MCP server under?

Parley declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/parley-consensus/
- Socket report: https://socket.dev/pypi/package/parley-consensus
- Repository: https://github.com/5uper0/parley
- Website: https://parleyprotocol.com/
- Changelog RSS feed: https://verifymcp.io/servers/5uper0-parley/parley-consensus.xml
- Changelog JSON feed: https://verifymcp.io/servers/5uper0-parley/parley-consensus.json
- HTML version of this page: https://verifymcp.io/servers/5uper0-parley/parley-consensus