MCP server that wraps the Dagster GraphQL API — manage runs, assets, schedules, sensors, and backfills from any MCP client
Nothing to run from here
Redeal is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
12
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Neutral fairness computation for agents: fair division, verifiable random, Shapley shares.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http redeal-mcp https://api.redeal.dev/mcp
# 2 — ask your agent for something these tools do
# commit_input, compute_commitment_tool, create_deal and 9 more
Redeal costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
REAll 1 server
redeal1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http redeal-mcp https://api.redeal.dev/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| commitment | string | yes | "sha256:" + hex of sha256(JCS(your input JSON) ++ your salt bytes). Compute it locally; the server sees only this hash until everyone has committed. |
| deal_id | string | yes | The deal id (d_...). |
| idempotency_key | string/null | no | Optional: retries with the same key + same arguments replay the original response. |
| invite_token | string | yes | The invite token for YOUR party, from create_deal's response. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| input | yes | Your algorithm input (any JSON value). | |
| salt | string | yes | Your hex salt (even length, e.g. 32+ random bytes hex-encoded). Keep it secret until reveal. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| algorithm | string | yes | Algorithm id from list_algorithms: "split.v1" (fixed 1,000-point budget) | "random.v1" | "shapley.v1" | "auction.v1". |
| algorithm_params | no | Algorithm-specific params from list_algorithms. split.v1: {"items": [...]}; random.v1: {"drand_round": N}; shapley.v1: {"coalition_values": {...}}; auction.v1: {"item": "...", "unit": "GBP", "reserve" | |
| api_key | string | yes | Your redeal API key (get one free with create_key — no signup form). |
| commit_deadline | integer | yes | Commit deadline as unix seconds UTC. Missed → deal EXPIRES (no certificate). |
| external_ref | string/null | no | Optional: your own identifier for this deal, e.g. "campaign-4821" (echoed into the certificate). |
| idempotency_key | string/null | no | Optional: retries with the same key + same arguments replay the original response. |
| mode | string/null | no | "sealed" (default, commit/reveal) or "open" (single round trip, low stakes). |
| party_labels | array | yes | One label per party, e.g. ["alice", "bob"] — or objects {"label", "weight"?, "statement_hash"?} (weight defaults to 1; statement_hash is "sha256:<hex>" of a declaration you want bound into the certifi |
| retention | string/null | no | "standard" (inputs retained encrypted) or "purge" (destroyed 7 days after certification). |
| reveal_deadline | integer | yes | Reveal deadline as unix seconds UTC (after commit_deadline). Missed → deal goes VOID and a non-participation certificate names whoever didn't reveal. |
| supersedes | string/null | no | Optional: certificate id (c_<16 hex>) this deal's certificate replaces (re-draw after VOID etc.). |
| terms_hash | string/null | no | Optional: "sha256:<hex>" of the deal's terms (echoed into the certificate; we never see the terms). |
| visibility | string/null | no | Optional: "public" (default — anyone can fetch the certificate at its id) or "parties" (only you and your invite-token holders). Certificates never contain inputs, only the outcome; choose "parties" w |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credential | string | yes | Your API key (initiator) or any party's invite token for this deal. |
| deal_id | string | yes | The deal id (d_...). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credential | string | yes | Your API key (initiator) or any party's invite token for this deal. |
| deal_id | string | yes | The deal id (d_...). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credential | string | yes | Your API key (initiator) or any party's invite token for this deal. |
| deal_id | string | yes | The deal id (d_...). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cert_id | string | yes | The certificate id (c_...). Verification is free and always will be. |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| deal_id | string | yes | The deal id (d_...). |
| idempotency_key | string/null | no | Optional: retries with the same key + same arguments replay the original response. |
| input | yes | Your algorithm input exactly as committed (any JSON value). split.v1: {"valuations": {...}} — your valuations must sum to exactly 1000; random.v1: {"nonce": "<hex>"}; shapley.v1: {"accept": true|false | |
| invite_token | string | yes | The invite token for YOUR party, from create_deal's response. |
| salt | string/null | no | Your hex salt from commitment time. Omit (or empty) for open-mode deals. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| deal_id | string | yes | The deal id (d_...). |
| input | yes | The algorithm input you plan to commit (e.g. {"valuations": {"<item_id>": <points>}} for split.v1 — every party's valuations must sum to exactly 1000). Validated against the deal's algorithm and decla | |
| invite_token | string | yes | The invite token for YOUR party, from create_deal's response. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cert_id | string | yes | The certificate id (c_...). Verification is free and always will be. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Redeal or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.7.0.
0.7.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Redeal can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.