mcpbeat

Shodai Agreements MCP Server

network.shodai/agreements
not responding

Shodai Agreements is listed as active in the registry but did not answer our last check. It exposes 11 tools. Last commit 7 Jul 2026.

Author, validate, deploy, and operate Shodai on-chain agreements.

Uptime history 41 hours of history · worst hour 0%
41 hours agonow
0.0%
Uptime 24h
0 of 91 checks
11
Tools
read from the server
51 ms
Response time
average over 24h
2
Stars
last commit 7 Jul 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add agreements --transport http https://shodai.network/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "agreements": {
      "url": "https://shodai.network/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.agreements]
url = "https://shodai.network/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "agreements": {
      "url": "https://shodai.network/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "agreements": {
      "url": "https://shodai.network/mcp"
    }
  }
}

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

agreement
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. Use documentId from list_agreements/get_agreement or from prepare_deployment_typed_data.
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 (execution.states). Use this to poll for transitions after submitting an input.
prepare
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 (eth_signTypedData_v4 / viem signTypedData), then call deploy_agreement with signer, deadline, and the signature components. No transaction is sent and nothing is stored. Reads the signer nonce from the target chain.
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 by the input definition, then call submit_input with signer, deadline, and the signature components. No transaction is sent and nothing is stored. Reads the agreement record and signer nonce.
agreements
list_agreements
Lists agreement summaries visible to the current API key. Supports pagination (cursor + limit), filtering by chain and state, and sorting. Returns summaries only; use get_agreement for the full record.
deploy
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-signed permit (signer, deadline, signature), or call prepare_deployment_typed_data first to obtain the payload to sign. Always run preflight_deployment before deploying. Requires the agreements.write scope.
input
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 PENDING, MINED, or FAILED.
preflight
preflight_deployment
Checks whether authored agreement JSON plus target chain, deployment values, participant wallet mappings, and observer context are ready for deployment. This does not deploy the agreement and does not require a signature. Always run this before signing a deploy permit. Requires the agreements.write scope.
submit
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 the signer must be allowed by that input. Provide a pre-signed permit (signer, deadline, signature), or call prepare_input_typed_data first. Requires the agreements.write scope.
validate
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 values, participant wallet addresses, signer, or permit data — use preflight_deployment for that. Iterate on the agreement JSON until this returns no blocking warnings. Requires the agreements.write scope.

Endpoints

URLTransportStateLatencyChecked
https://shodai.network/mcp streamable-http answering 51 ms 3 min ago

Shodai Agreements — questions

Answers built from our own checks of this server.

What can Shodai Agreements do?
It exposes 11 tools, read directly from the server on our last check. Among them: deploy_agreement, get_agreement, get_agreement_document, get_agreement_state, get_input_history, list_agreements and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Shodai Agreements mostly used for?
Its tools cluster around agreement and prepare. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Shodai Agreements working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 51 ms. The bar chart above shows every period we have measured.
The registry lists Shodai Agreements as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Shodai Agreements?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Shodai Agreements need an API key?
No. Shodai Agreements completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.
Is Shodai Agreements open source?
Yes — it is published under the Apache-2.0 licence, written in TypeScript and 2 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.