Productivity

shodai.network

Manages and retrieves agreement records and their associated documents and states.

1 endpoint11 known toolsFirst detected June 27, 2026Last detected September 6, 2026

ENDPOINT 1

https://shodai.network/mcp

No auth detected

MCP server metadata

Name: agreements-mcp-server
Version: 0.1.0

Capabilities

tools.listChangedresources.listChangedprompts.listChanged

Server instructions

This server exposes the Shodai Agreements API: author, validate, deploy, and operate verifiable on-chain agreements. Authoring loop: read the simple/complex example resources to learn the agreement JSON shape, draft the document, then iterate with validate_agreement until it has no blocking warnings, and run preflight_deployment before any signing. Reads (list_agreements, get_agreement, get_agreement_state, get_input_history) require the agreements.read scope; validation tools require agreements.write. Hosted tool calls must include environment: "testnet" or "production"; API keys only work in the environment where they were created. For deployment, signing, and troubleshooting workflows beyond these tools, fetch the docs pages listed in the docs-index resource.

Known tools 11

list_agreements

Lists agreement summaries visible to the current API key.

Inferred read-only

get_agreement

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

Inferred read-only

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.

Inferred read-only

get_agreement_state

Returns the current state of an agreement.

Inferred read-only

get_input_history

Returns recorded input submissions for an agreement, with pagination and filtering.

Inferred read-only

validate_agreement

Checks only the authored agreement JSON document and returns participant variable keys, input IDs, state IDs, and warnings.

Inferred read-only

preflight_deployment

Checks whether authored agreement JSON plus target chain, deployment values, participant wallet mappings, and observer context are ready for deployment.

Inferred read-only

deploy_agreement

Deploys authored agreement JSON using an EIP-712 permit; the API submits the on-chain transaction and returns the deployed agreement record.

Inferred read-only

submit_input

Submits a signed input to a deployed agreement, advancing its on-chain lifecycle.

Inferred read-only

prepare_deployment_typed_data

Builds the exact EIP-712 payload that must be signed to authorize deployment of the given agreement JSON.

Inferred read-only

prepare_input_typed_data

Builds the exact EIP-712 payload that must be signed to authorize submitting an input to a deployed agreement.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.agreements-mcp-server]
url = "https://shodai.network/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: agreements-mcp-server
Remote MCP URL: https://shodai.network/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "agreements-mcp-server": {
      "url": "https://shodai.network/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "agreements-mcp-server",
  "transport": "streamable-http",
  "url": "https://shodai.network/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.