← shodai.network
INDIVIDUAL MCP TOOL
prepare_deployment_typed_data
Builds the exact EIP-712 payload that must be signed to authorize deployment of the given agreement JSON.
Input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent endpoint
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.shodai-network]
url = "https://shodai.network/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"shodai-network": {
"type": "http",
"url": "https://shodai.network/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: shodai-network
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": {
"shodai-network": {
"url": "https://shodai.network/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"shodai-network": {
"type": "http",
"url": "https://shodai.network/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "shodai-network",
"transport": "streamable-http",
"url": "https://shodai.network/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
list_agreements— Lists agreement summaries visible to the current API key.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.get_input_history— Returns recorded input submissions for an agreement, with pagination and filtering.validate_agreement— Checks only the authored agreement JSON document and returns participant variable keys, input IDs, state IDs, and warnings.preflight_deployment— Checks whether authored agreement JSON plus target chain, deployment values, participant wallet mappings, and observer context are ready for deployment.deploy_agreement— Deploys authored agreement JSON using an EIP-712 permit; the API submits the on-chain transaction and returns the deployed agreement record.