# Shodai Agreements MCP server

Source: https://glimind.com/server/mcp-registry%2Fnetwork.shodai%2Fagreements
Registry id: `mcp-registry/network.shodai/agreements`
Status: auth-required (checked 2026-10-27T13:25:54.121Z)

## Verdict

Shodai Agreements MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 282 ms median handshake and 0 outages in 90 days. Its agent-readiness grade is A (96/100) across 11 tools, costing an agent about 4,458 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 282 ms | 63% of MCP servers |
| p95 handshake latency | 466 ms | — |
| Checks in 30 days | 225 | — |
| Outages, 90 days | 0 | — |
| Median recovery | — | — |
| Agent-readiness score | 96/100 (A) | 82% of MCP servers |
| Tools | 11 | — |
| Tool-list size for an agent | ~4,458 tokens | 40% of MCP servers |
| Days observed | 28 | — |

## Install

```json
{
  "mcpServers": {
    "shodai-agreements-mcp-server": {
      "type": "http",
      "url": "https://shodai.network/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http shodai-agreements-mcp-server https://shodai.network/mcp
```

## Tools (11)

- `deploy_agreement`: Deploys authored agreement JSON using an EIP-712 permit; the API submits the on-chain transaction and returns the deployed agreement record. Provide a pre-signe
- `get_agreement`: Returns a single agreement record, including the full authored agreement JSON and hosted record context (participants, observers, owner, deployment address).
- `get_agreement_document`: Returns the rendered hosted prose document for an agreement by documentId, including content type, display name, chain, docUri, and agreement record references.
- `get_agreement_state`: Returns the current state of an agreement. For deployed agreements, interpret the state against the states defined in the authored agreement lifecycle (executio
- `get_input_history`: Returns recorded input submissions for an agreement, with pagination and filtering. Use this to inspect which events have been submitted and whether each is PEN
- `list_agreements`: Lists agreement summaries visible to the current API key. Supports pagination (cursor + limit), filtering by chain and state, and sorting. Returns summaries onl
- `preflight_deployment`: Checks whether authored agreement JSON plus target chain, deployment values, participant wallet mappings, and observer context are ready for deployment. This do
- `prepare_deployment_typed_data`: Builds the exact EIP-712 payload that must be signed to authorize deployment of the given agreement JSON. Sign the returned typedData with the deploying wallet 
- `prepare_input_typed_data`: Builds the exact EIP-712 payload that must be signed to authorize submitting an input to a deployed agreement. Sign the returned typedData with a wallet allowed
- `submit_input`: Submits a signed input to a deployed agreement, advancing its on-chain lifecycle. The input ID and values must match an input defined by the agreement JSON, and
- `validate_agreement`: Checks only the authored agreement JSON document and returns participant variable keys, input IDs, state IDs, and warnings. This does not validate deployment va

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.