Server data from the Official MCP Registry
Author, validate, deploy, and operate Shodai on-chain agreements.
Author, validate, deploy, and operate Shodai on-chain agreements.
Remote endpoints: streamable-http: https://shodai.network/mcp
Valid MCP server (2 strong, 0 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.
11 tools verified · Open access · No issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"network-shodai-agreements": {
"url": "https://shodai.network/mcp"
}
}
}From the project's GitHub README.
Open-source home for the TypeScript client for the Agreements API and the reference playground app built on top of it.
Most consumers should install the published npm package rather than this monorepo:
npm install @cns-labs/agreements-api-client
Add viem if you want to use the built-in permit-signing helpers for deploy and input submission:
npm install @cns-labs/agreements-api-client viem
packages/agreements-api-client: publishable npm package @cns-labs/agreements-api-clientapps/agreements-api-playground: reference Vite app for validating agreements, deploying with permits, inspecting state, and submitting inputspackages/agreements-api-client/README.mdapps/agreements-api-playground/README.mdapps/agreements-api-playground/src/App.tsxThe SDK now prefers a named environment instead of a raw host:
const client = new ApiClient({
environment: 'testnet',
apiKey: process.env.AGREEMENTS_API_KEY,
});
Built-in mappings:
testnet -> https://test-api.shodai.networkproduction -> https://api.shodai.networkThe client still supports baseUrl as an advanced override for local proxies, internal gateways, or non-standard deployments. It continues to add /v0/* automatically.
# from the repository root
pnpm install
pnpm build
pnpm dev:playground
The playground defaults to http://localhost:5176.
If that port is already in use, start the playground on another port:
pnpm --filter agreements-api-playground exec vite --host 127.0.0.1 --port 4176
For local browser development, the playground is environment-first and defaults to testnet.
Use the in-app environment selector to switch between hosted testnet and production API targets.
See apps/agreements-api-playground/README.md for the full environment configuration.
packages/agreements-api-client.packages/agreements-api-client/DEVELOPMENT.md.Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.