Finance · Remote MCP server
Shodai Agreements
Author, validate, deploy, and operate Shodai on-chain agreements.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
network.shodai/agreements- Version
- 0.1.0
- Status
- Active
- Category
- finance
- Transport
- Streamable HTTP
- Published
- 2026-06-25
- Updated
- 2026-06-25
- Publisher
- network.shodai
- Namespace
- Namespace verified by the MCP Registry via the domain shodai.network · how
- Repository
- github.com/CNSLabs/agreements-api-sdk (folder packages/agreements-mcp-server)
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://shodai.network/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Shodai Agreements
Shodai Agreements is a remote MCP server: there is nothing to install. Its endpoint is https://shodai.network/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More finance servers
| Server | Runs |
|---|---|
| SherwebMCP server for Sherweb - billing, subscriptions, customers, and product catalog. | Local · stdio |
| ShieldZCash MCPKeyless non-custodial crypto payments for AI agents: payment links and tip jars, no API key. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| ShingouHourly crypto news sentiment and typed market events, with sources on every signal. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Shiwake MCPJournal entry testing (JET) for accounting audits. 15 screening rules, zero dependencies. | Local · stdio |
| shumi.aiCrypto market intelligence: prices, funding rates, narratives, regime, and delta-neutral research. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| ShurqAmazon seller analytics and PPC automation: true profit per product, bids, budgets and keywords. | Remote · HTTPLive check: sign-in required |
| Sicoob MCPConnect your Sicoob account to AI via Brazil's Open Finance: balances, statements, cards, investment. | Remote · HTTPLive check: ✓ handshake |
| Sicredi MCPConnect your Sicredi account to AI via Brazil's Open Finance: balances, statements, cards, investmen. | Remote · HTTPLive check: ✓ handshake |