Skip to main content
Glama

Server Details

Neutral fairness computation for agents: fair division, verifiable random, Shapley shares.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
redeal-dev/redeal
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A4.1/5.0

Scored across 12 tools

Disambiguation4/5

The core lifecycle tools (create_deal, commit_input, reveal_input, get_deal) are clearly distinct, and validate_input, compute_commitment_tool, and list_algorithms each serve unique steps. The certificate trio (get_certificate, get_public_certificate, verify_certificate) creates some ambiguity because two are fetch-style and one is verify-style, but their descriptions are strong enough to disambiguate in most contexts.

Naming Consistency4/5

Most tools follow a consistent verb_noun snake_case pattern: create_deal, get_deal, commit_input, reveal_input, verify_certificate. The deviations are minor but noticeable: compute_commitment_tool appends an awkward '_tool' suffix, and get_entropy describes a domain-specific action rather than a clean action_object.

Tool Count5/5

Twelve tools is well-scoped for a domain covering onboarding, algorithm discovery, deal creation, sealed commitment/reveal, entropy finalization, and certificate verification. Each tool maps to a distinct workflow step, and none feel redundant or purely decorative.

Completeness4/5

The main path from create_key and list_algorithms through validate, commit, reveal, get_entropy, and certificate verification is fully covered, and VOID/EXPIRED states handle abandoned deals. Minor gaps include no explicit cancel/abort tool and no clear representation of public versus parties-only deals in the create_deal description.

Available Tools

12 tools
commit_inputAInspect

Commit your sealed input as a hash (sealed mode). Nobody — including redeal — can see your input until all parties have committed. After the last commitment the deal opens for reveals immediately.

Inputs: deal_id (required), commitment (required), invite_token (required), idempotency_key.

compute_commitment_toolAInspect

Compute a commitment string for (input, salt): sha256(JCS(input) ++ salt_bytes), prefixed 'sha256:'. Convenience only — the rule is public and you can compute it yourself.

Inputs: salt (required), input (required).

create_dealAInspect

Create a fairness deal. You are party 0 (initiator). Returns a deal id and one invite token per party — give each counterparty their own token. Sealed mode: everyone commits a hash, then reveals; certificate is issued automatically when the deal computes or goes VOID.

Inputs: api_key (required), algorithm (required), party_labels (required), commit_deadline (required), +9 more.

create_keyAInspect

Get a free redeal API key. No signup, no email — this is the entire onboarding. The key is shown once; store it. Use it as api_key in create_deal.

Inputs: no named parameters.

get_certificateAInspect

Fetch the signed fairness certificate for a finished deal (state CERTIFIED). Includes the labelled signature (es256 or ed25519) and transparency-log inclusion proof. Verify it with verify_certificate.

Inputs: deal_id (required), credential (required).

get_dealAInspect

Read a deal's public state: protocol state (OPEN/COMMITTING/REVEALING/CERTIFIED/VOID/EXPIRED), who has committed/revealed, deadlines, result, and certificate_id once issued. Inputs of other parties are never exposed.

Inputs: deal_id (required), credential (required).

get_entropyAInspect

Finish a random.v1 deal once every party has revealed: redeal fetches the deal's pre-declared drand round from the public League of Entropy beacon (fixed at creation, publicly cross-checkable), computes the draw, and issues the certificate. Call this after the last reveal_input; the deal rests in REVEALING until you do. Idempotent — safe to retry.

Inputs: deal_id (required), credential (required).

get_public_certificateAInspect

Fetch a certificate's full JSON (outcome included) by id. Works for public deals (the default). Parties-only deals and unknown ids both return NOT_FOUND. To re-verify the computation itself, use verify_certificate (checks) or the CLI re-runner with the parties' inputs.

Inputs: cert_id (required).

list_algorithmsAInspect

List redeal's algorithms (split.v1 fixed-budget fair division, random.v1 verifiable random selection, shapley.v1 Shapley shares, auction.v1 sealed-bid second-price auctions) with their input contracts and the published test vectors (served inline — the same fixtures the engine test suite runs). Read this before creating a deal.

Inputs: no named parameters.

reveal_inputAInspect

Reveal your committed input. It must hash to your earlier commitment. When the last party reveals, the deal computes and the fairness certificate is issued automatically — fetch it with get_certificate.

Inputs: input (required), deal_id (required), invite_token (required), salt, +1 more.

validate_inputAInspect

Validate your algorithm input against the deal's contract BEFORE you commit. A commitment binds the exact input bytes — a contract-violating input (e.g. split.v1 valuations not summing to exactly 1000) can never be corrected afterwards and the deal will VOID at the reveal deadline. Always validate first, then compute_commitment_tool, then commit_input. Read-only: nothing is stored or changed.

Inputs: input (required), deal_id (required), invite_token (required).

verify_certificateAInspect

Verify a redeal certificate by id: signature check (current or published legacy key) + transparency-log inclusion check, reported per check. Free, no credential required, always.

Inputs: cert_id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP hosts such as Claude or Cursor to run multilateral consensus among AI agents of rival owners, enforcing deterministic red lines and max-min decisions over masked verdicts. It also produces tamper-evident SHA-256 receipts that each party can verify and replay against their own private preferences.
      2
      3
      1
      Apache 2.0
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.