Redeal MCP server

• Registry namedev.redeal/redealverified in the MCP registry

The registry name sits under redeal.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-26
• Tools12
• Server calls itselfredeal
• Server version0.7.0
• Protocol version2025-11-25

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 488 ms.

• Its tools do every use case we checked: split a shared cost between parties by fixed budget; pick one party at random with verifiable entropy.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP score76 of 100answers 100 · does the job 100 · definitions 78 · context 100 · connects 100 · lowered by the warning signs below
• What an agent can do with it2 of 2 use cases
• Answered100% of days9 of 9 daily checks
• Median first answer530 ms
• Space in an agent's context≈ 2,535 tokensthe definitions of all its tools (12), which an agent carries on every turn
• Tool definitionsB · 78 of 100
• Typed results0 of 12 toolsdeclared outputSchema: results come typed, read once

• Parameters without a type: in 4 of 12
• Not saying whether it only reads or can destroy: 12 of 12

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• commit_input

  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.

• compute_commitment_tool

  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.

• create_deal

  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…

• create_key

  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.

• get_certificate

  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.

• get_deal

  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.

• get_entropy

  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…

• get_public_certificate

  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…

• list_algorithms

  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…

• reveal_input

  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.

• validate_input

  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…

• verify_certificate

  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.