# Shodai Agreements (remote · shodai.network)

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

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `shodai.network`: 70/100 (this document), [markdown](https://verifymcp.io/servers/network-shodai-agreements/shodai.md), [page](https://verifymcp.io/servers/network-shodai-agreements/shodai)

## Channel facts

- Endpoint: `https://shodai.network/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (deploy_agreement).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2436 tokens (~162/item across 15 items; 11 tools + 4 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.network-shodai-agreements]
url = "https://shodai.network/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "network-shodai-agreements": {
      "type": "remote",
      "url": "https://shodai.network/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add network-shodai-agreements --url https://shodai.network/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  network-shodai-agreements:
    url: "https://shodai.network/mcp"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 69, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 66)

First indexed and scored.

## MCP tools (11)

### `list_agreements` (~262 tokens)

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.

Input parameters:

- `chainId` (integer): Filter by EVM chain ID (e.g. 59141 for Linea Sepolia).
- `createdAfter` (string): ISO 8601 timestamp; only agreements created at or after this time.
- `createdBefore` (string): ISO 8601 timestamp; only agreements created at or before this time.
- `cursor` (string): Opaque pagination cursor from a previous response (pageInfo.nextCursor).
- `environment` (string, required): Agreements API environment for this tool call. API keys only work in the environment where they were created.
- `limit` (integer): Page size (max 100).
- `sortBy` (string): Sort field (single field only).
- `sortDirection` (string): Sort direction; defaults to desc.
- `state` (string): Filter by current lifecycle state ID.
- `updatedAfter` (string): ISO 8601 timestamp; only agreements updated at or after this time.
- `updatedBefore` (string): ISO 8601 timestamp; only agreements updated at or before this time.

### `get_agreement` (~85 tokens)

Get agreement

Returns a single agreement record, including the full authored agreement JSON and hosted record context (participants, observers, owner, deployment address).

Input parameters:

- `agreementId` (string, required): Agreement record ID, as returned by list_agreements (not the on-chain address).
- `environment` (string, required): Agreements API environment for this tool call. API keys only work in the environment where they were created.

### `get_agreement_document` (~114 tokens)

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.

Input parameters:

- `documentId` (string, required): Hosted agreement document ID, as returned by list_agreements/get_agreement or prepare_deployment_typed_data.
- `environment` (string, required): Agreements API environment for this tool call. API keys only work in the environment where they were created.

### `get_agreement_state` (~99 tokens)

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.

Input parameters:

- `agreementId` (string, required): Agreement record ID, as returned by list_agreements (not the on-chain address).
- `environment` (string, required): Agreements API environment for this tool call. API keys only work in the environment where they were created.

### `get_input_history` (~159 tokens)

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.

Input parameters:

- `agreementId` (string, required): Agreement record ID, as returned by list_agreements (not the on-chain address).
- `cursor` (string): Opaque pagination cursor from a previous response (pageInfo.nextCursor).
- `environment` (string, required): Agreements API environment for this tool call. API keys only work in the environment where they were created.
- `inputId` (string): Filter by input ID as defined in the agreement JSON (execution.inputs).
- `limit` (integer): Page size (max 100).
- `status` (string): Filter by submission status.

### `validate_agreement` (~134 tokens)

Validate agreement structure

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.

Input parameters:

- `agreement` (object, required): Complete authored agreement JSON document with metadata, variables, content, and execution sections. See the simple/complex example resources for the authoritative shape.
- `environment` (string, required): Agreements API environment for this tool call. API keys only work in the environment where they were created.

### `preflight_deployment` (~181 tokens)

Preflight deployment request

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.

Input parameters:

- `agreement` (object, required): Complete authored agreement JSON document with metadata, variables, content, and execution sections. See the simple/complex example resources for the authoritative shape.
- `chainId` (integer): Target EVM chain ID for deployment.
- `environment` (string, required): Agreements API environment for this tool call. API keys only work in the environment where they were created.
- `initValues` (object): Deployment-time values for variables referenced by execution.initialize.data.
- `observers` (array): Observer email addresses for the deployed agreement.
- `participants` (array): Wallet mappings for participant variables.

### `deploy_agreement` (~346 tokens)

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 parameters:

- `agreement` (object, required): Complete authored agreement JSON document with metadata, variables, content, and execution sections.
- `chainId` (integer): Target EVM chain ID (e.g. 59141 for Linea Sepolia).
- `deadline` (integer): Permit deadline in unix seconds. Must match the signed payload.
- `displayName` (string, required): Human-readable name for the deployed agreement record.
- `docUri` (string): Optional document URI recorded on-chain with the agreement.
- `documentId` (string): Optional hosted document ID paired with docUri for GET /v0/agreements/documents/{documentId}.
- `environment` (string, required): Agreements API environment for this tool call. API keys only work in the environment where they were created.
- `initValues` (object): Deployment-time values for variables referenced by execution.initialize.data.
- `observers` (array): Observer email addresses.
- `participants` (array): Wallet mappings for participant variables.
- `signatureR` (string): Permit signature r component (0x... 32 bytes).
- `signatureS` (string): Permit signature s component (0x... 32 bytes).
- `signatureV` (integer): Permit signature v component (27 or 28).
- `signer` (string): Wallet address (0x...) that signed the permit.

### `submit_input` (~244 tokens)

Submit input with permit

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.

Input parameters:

- `agreementId` (string, required): Agreement record ID of a deployed agreement.
- `deadline` (integer): Permit deadline in unix seconds. Must match the signed payload.
- `environment` (string, required): Agreements API environment for this tool call. API keys only work in the environment where they were created.
- `inputId` (string, required): Input ID defined by the agreement JSON (execution.inputs).
- `signatureR` (string): Permit signature r component (0x... 32 bytes).
- `signatureS` (string): Permit signature s component (0x... 32 bytes).
- `signatureV` (integer): Permit signature v component (27 or 28).
- `signer` (string): Wallet address (0x...) that signed the permit.
- `values` (object, required): Values matching the input schema defined by the agreement JSON.

### `prepare_deployment_typed_data` (~299 tokens)

Prepare deployment permit 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.

Input parameters:

- `agreement` (object, required): Complete authored agreement JSON document with metadata, variables, content, and execution sections.
- `chainId` (integer, required): Target EVM chain ID (e.g. 59141 for Linea Sepolia).
- `deadline` (integer): Permit deadline in unix seconds; defaults to one hour from now.
- `docUri` (string): Document URI (must match the later deploy_agreement call).
- `documentId` (string): Hosted document ID. If omitted with docUri, no hosted document ID is stored; if both are omitted, the server generates both values.
- `environment` (string, required): Agreements API environment for this tool call. API keys only work in the environment where they were created.
- `initValues` (object): Deployment-time init values (must match the later deploy_agreement call).
- `observers` (array): Observer email addresses.
- `participants` (array): Wallet mappings for participant variables.
- `signerAddress` (string, required): Wallet address (0x...) that will sign and own the deployment.

### `prepare_input_typed_data` (~196 tokens)

Prepare input permit 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.

Input parameters:

- `agreementId` (string, required): Agreement record ID of a deployed agreement.
- `deadline` (integer): Permit deadline in unix seconds; defaults to one hour from now.
- `environment` (string, required): Agreements API environment for this tool call. API keys only work in the environment where they were created.
- `inputId` (string, required): Input ID defined by the agreement JSON (execution.inputs).
- `signerAddress` (string, required): Wallet address (0x...) that will sign the input permit.
- `values` (object, required): Values matching the input schema (must match the later submit_input call).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/network-shodai-agreements/shodai#diagnostics

## Score history

- 2026-08-03: 70
- 2026-08-02: 69
- 2026-08-01: 69
- 2026-07-31: 69
- 2026-07-30: 68
- 2026-07-29: 68
- 2026-07-28: 67
- 2026-07-27: 66
- 2026-07-26: 66

## Links

- Remote endpoint: https://shodai.network/mcp
- Authorisation metadata: https://shodai.network/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/CNSLabs/agreements-api-sdk
- Changelog RSS feed: https://verifymcp.io/servers/network-shodai-agreements/shodai/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/network-shodai-agreements/shodai/changelog.json
- HTML version of this page: https://verifymcp.io/servers/network-shodai-agreements/shodai