Skip to main content
Glama
5uper0

parley-mcp

Related Servers

Alternatives to parley-mcp

Related Servers

  • A
    license
    B
    quality
    B
    maintenance
    An MCP server that enforces fail-closed deterministic checks, independent refute-first review, and tamper-evident hash-chained receipts for AI agent outputs before claiming completion.
    4
    3
    MIT
  • F
    license
    Not graded
    quality
    D
    maintenance
    Cryptographically anchored, tamper-evident evidence receipts for AI agents — verified run receipts, existence-at-time proofs, and cited answers from an anchored public record. Remote MCP with proof-gated settlement; attests existence and integrity, never truth.
    -
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to run structured multi-persona debates over high-stakes decisions and merge their positions into an explainable consensus, complete with logged dissenting minority opinions. It runs as a zero-dependency Python MCP server or importable module, compatible with Claude Desktop, Cursor, and custom agent frameworks.
    7
    MIT
  • F
    license
    Not graded
    quality
    B
    maintenance
    Aggregates multiple divergent LLM reasoning trajectories through majority voting and consensus scoring to produce high-confidence deterministic outputs without additional model calls. Plug into any MCP-compliant client to resolve agent tasks with sub-millisecond, zero-dependency execution.
    7
    -

TDQS

A4.4/5.0

Scored across 3 tools

Disambiguation4/5

The three tools have distinct targets: parley_decide produces a decision, parley_verify_receipt re-checks the full transcript/hash and max-min, and parley_check_party replays one party's red lines. There is mild overlap between the two verification tools, but the descriptions clearly delineate what each checks.

Naming Consistency5/5

All three names follow a single, predictable pattern: parley_ prefix plus a consistent verb_noun form (decide, verify_receipt, check_party). No mixed conventions or vague verbs.

Tool Count4/5

Three tools is on the thin side, but the domain is a narrow, self-contained decision engine, and decide/verify/check each earns a clear place. It is a touch under-provisioned rather than bloated.

Completeness4/5

The surface covers the core lifecycle: reach a decision, verify the recorded transcript, and re-check a single party. Privacy-mode execution is delegated to examples/run_env.py rather than a tool, and there is no batch check, but nothing leaves an obvious dead end for the stated purpose.

Maintenance

ActivityActive
ResponsivenessUnresponsive