Shodai Agreements

REMOTE · SHODAI.NETWORK · SCANNED AUG 3

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

Available components

+4 this week 70 70 Trust /100

Trust breakdown (6 categories)

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. How we score →

Endpoint Security63

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (deploy_agreement). See how to fix → View diagnostics → Fail
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability79

100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
AI-judged instruction clarity (excellent).Pass
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. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · shodai.network

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.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
    }
  }
}

# add to OpenClaw

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

# ~/.hermes/config.yaml

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

// mcp.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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

3 Aug 26 +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.
31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 26 +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.
28 Jul 26 +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.
27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 66

First indexed and scored.

Show 5 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://shodai.network/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=shodai.network	CN=YR2,O=Let's Encrypt,C=US	11 Jul 2026	9 Oct 2026	RSA 2048	SHA256-RSA	50ab0f5fc8f7b4eb3cc96966535383e0812
SANs: shodai.network
CN=YR2,O=Let's Encrypt,C=US (CA)	CN=Root YR,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	RSA 2048	SHA256-RSA	4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA)	CN=ISRG Root X1,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	RSA 4096	SHA256-RSA	f24b6d17f9d9ad7cb1c9fea78782699f

DNSSEC insecure

Validation of shodai.network. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
network.	present	40414	8	Verified
shodai.network.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Header	Value
strict-transport-security	max-age=63072000

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://shodai.network/mcp	Verified	200
http (plaintext)	http://shodai.network/mcp	HTTPS enforced	308	https://shodai.network/mcp

MCP tools — 11 exposed · ~2,119 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

deploy_agreement Deploy agreement ~346

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 Output Examples

Name	Type	Req	Description
agreement	object	yes	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	yes	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	yes	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.

No output schema declared.

No examples provided.

get_agreement Get agreement ~85

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

Input Output Examples

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

No output schema declared.

No examples provided.

get_agreement_document Get agreement document ~114

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 Output Examples

Name	Type	Req	Description
documentId	string	yes	Hosted agreement document ID, as returned by list_agreements/get_agreement or prepare_deployment_typed_data.
environment	string	yes	Agreements API environment for this tool call. API keys only work in the environment where they were created.

No output schema declared.

No examples provided.

get_agreement_state Get agreement state ~99

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 Output Examples

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

No output schema declared.

No examples provided.

get_input_history Get input history ~159

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 Output Examples

Name	Type	Req	Description
agreementId	string	yes	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	yes	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.

No output schema declared.

No examples provided.

list_agreements List agreements ~262

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 Output Examples

Name	Type	Req	Description
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	yes	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.

No output schema declared.

No examples provided.

preflight_deployment Preflight deployment request ~181

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 Output Examples

Name	Type	Req	Description
agreement	object	yes	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	yes	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.

No output schema declared.

No examples provided.

prepare_deployment_typed_data Prepare deployment permit typed data ~299

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 Output Examples

Name	Type	Req	Description
agreement	object	yes	Complete authored agreement JSON document with metadata, variables, content, and execution sections.
chainId	integer	yes	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	yes	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	yes	Wallet address (0x...) that will sign and own the deployment.

No output schema declared.

No examples provided.

prepare_input_typed_data Prepare input permit typed data ~196

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 Output Examples

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

No output schema declared.

No examples provided.

submit_input Submit input with permit ~244

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 Output Examples

Name	Type	Req	Description
agreementId	string	yes	Agreement record ID of a deployed agreement.
deadline	integer	—	Permit deadline in unix seconds. Must match the signed payload.
environment	string	yes	Agreements API environment for this tool call. API keys only work in the environment where they were created.
inputId	string	yes	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	yes	Values matching the input schema defined by the agreement JSON.

No output schema declared.

No examples provided.

validate_agreement Validate agreement structure ~134

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 Output Examples

Name	Type	Req	Description
agreement	object	yes	Complete authored agreement JSON document with metadata, variables, content, and execution sections. See the simple/complex example resources for the authoritative shape.
environment	string	yes	Agreements API environment for this tool call. API keys only work in the environment where they were created.

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	66
27 Jul	66
28 Jul	67
29 Jul	68
30 Jul	68
31 Jul	69
1 Aug	69
2 Aug	69
3 Aug	70