Is the Redeal MCP server down?

mcp-registry/dev.redeal/redeal · v0.7.0

healthy
Last checked 2026-10-22 10:24 UTC · handshake 483ms

As of 2026-10-22 10:24 UTC, the Redeal MCP server is up with a Glimind reliability score of 75/100 (grade B). Over the last 30 days it answered 99.4% of Glimind's liveness checks. It had 57 outages in 90 days, with a median recovery of 6 minutes.

uptime (30d checks)
99.4%
checks observed
4,270
outages (90d)
57
tools
12

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

Install Redeal MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http redeal-mcp-server https://api.redeal.dev/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "redeal-mcp-server": {
      "type": "http",
      "url": "https://api.redeal.dev/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (76/100)

C (76/100): 0 error(s), 4 warning(s) across 12 tool(s); ~2,815 tokens of tool definitions.
Scores higher than 13% of 15,523 MCP servers Glimind has audited.
Its tool list costs an agent ~2,815 tokens per session — more than 50% of servers.
76 → 76 since 2026-10-17
no tool-poisoning patterns
Schemas73
Descriptions100
Safety hints7
Token cost100
Client compatibility70
Protocol100
Reliability85
Stability100

What to fix (5)

12 of 12 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: commit_input, compute_commitment_tool, create_deal, create_key, get_certificate and 7 more

4 tool(s) have parameters with no type (no type/enum/anyOf/$ref).

Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →

Tools: compute_commitment_tool, create_deal, reveal_input, validate_input

2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: create_deal, create_key

Handshake + tools/list takes ~1,675 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 10 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fdev.redeal%2Fredeal/fixes

compute_commitment_tool 1 change
{
  "name": "compute_commitment_tool",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "input",
      "salt"
    ],
    "properties": {
      "salt": {
        "type": "string",
        "description": "Your hex salt (even length, e.g. 32+ random bytes hex-encoded). Keep it secret until reveal."
      },
      "input": {
        "description": "Your algorithm input (any JSON value).",
        "type": "string"
      }
    }
  }
}
create_deal 2 changes
{
  "name": "create_deal",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "api_key",
      "algorithm",
      "party_labels",
      "commit_deadline",
      "reveal_deadline"
    ],
    "properties": {
      "mode": {
        "type": [
          "string",
          "null"
        ],
        "description": "\"sealed\" (default, commit/reveal) or \"open\" (single round trip, low stakes)."
      },
      "api_key": {
        "type": "string",
        "description": "Your redeal API key (get one free with create_key — no signup form)."
      },
      "algorithm": {
        "type": "string",
        "description": "Algorithm id from list_algorithms: \"split.v1\" (fixed 1,000-point budget) | \"random.v1\" | \"shapley.v1\" | \"auction.v1\"."
      },
      "retention": {
        "type": [
          "string",
          "null"
        ],
        "description": "\"standard\" (inputs retained encrypted) or \"purge\" (destroyed 7 days after certification)."
      },
      "supersedes": {
        "type": [
          "string",
          "null"
        ],
        "description": "Optional: certificate id (c_<16 hex>) this deal's certificate replaces (re-draw after VOID etc.)."
      },
      "terms_hash": {
        "type": [
          "string",
          "null"
        ],
        "description": "Optional: \"sha256:<hex>\" of the deal's terms (echoed into the certificate; we never see the terms)."
      },
      "visibility": {
        "type": [
          "string",
          "null"
        ],
        "description": "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\" when the outcome itself is sensitive."
      },
      "external_ref": {
        "type": [
          "string",
          "null"
        ],
        "description": "Optional: your own identifier for this deal, e.g. \"campaign-4821\" (echoed into the certificate)."
      },
      "party_labels": {
        "type": "array",
        "items": true,
        "description": "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 certificate). Party 0 is you (the initiator). Labels go on the public certificate permanently: use nicknames, never real names or emails."
      },
      "commit_deadline": {
        "type": "integer",
        "format": "int64",
        "description": "Commit deadline as unix seconds UTC. Missed → deal EXPIRES (no certificate)."
      },
      "idempotency_key": {
        "type": [
          "string",
          "null"
        ],
        "description": "Optional: retries with the same key + same arguments replay the original response."
      },
      "reveal_deadline": {
        "type": "integer",
        "format": "int64",
        "description": "Reveal deadline as unix seconds UTC (after commit_deadline). Missed → deal goes VOID and a non-participation certificate names whoever didn't reveal."
      },
      "algorithm_params": {
        "description": "Algorithm-specific params from list_algorithms. split.v1: {\"items\": [...]}; random.v1: {\"drand_round\": N}; shapley.v1: {\"coalition_values\": {...}}; auction.v1: {\"item\": \"...\", \"unit\": \"GBP\", \"reserve\": N}.",
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
create_key 1 change
{
  "name": "create_key",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/dev.redeal/redeal"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/dev.redeal/redeal"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.redeal%2Fredeal.svg)](https://glimind.com/server/mcp-registry%2Fdev.redeal%2Fredeal?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fdev.redeal%2Fredeal?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.redeal%2Fredeal.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.redeal%2Fredeal.svg
   :target: https://glimind.com/server/mcp-registry%2Fdev.redeal%2Fredeal?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:ca19716ace87b234…, first seen 2026-10-17, included at leaf 8208 of 45,401. Version history · verify what your client received.

Tools (12)

Compare: most reliable other servers · most reliable security servers · most reliable retrieval servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Redeal MCP server down right now?

As of 2026-10-22 10:24 UTC, the Redeal MCP server is up with a Glimind reliability score of 75/100 (grade B). Over the last 30 days it answered 99.4% of Glimind's liveness checks. It had 57 outages in 90 days, with a median recovery of 6 minutes.

How many tools does Redeal MCP server provide?

Redeal MCP server advertises 12 tools, including commit_input, compute_commitment_tool, create_deal, create_key, get_certificate.

How do I install Redeal MCP server?

Point your MCP client at this streamable-http endpoint: https://api.redeal.dev/mcp

Is the Redeal MCP server safe to connect to an AI agent?

Glimind scanned all 12 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Redeal MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve