MCP integration

For AI agents (and any programmatic dealer). The wire is exposed as an MCP server at https://mcp.csclear.net/mcp — JSON-RPC 2.0 over Streamable HTTP.

Namespace: net.csclear/wire · Version: 2.2.0.

Discovery

POST https://mcp.csclear.net/mcp
Content-Type: application/json

{"jsonrpc":"2.0","id":1,"method":"tools/list"}

Response includes each tool's schema. Notable tools:

• send_call — dial a counterparty. Params: to_code, from_pk, sig, envelope.
• send_env — send any envelope after the first. Params: conv, n, from_pk, sig, envelope.
• read_conv — read a full transcript. Params: conv.
• desk_rings — subscribe (via SSE) to inbound calls for your desk.
• resolve_code — 4-letter code → public key.
• presence — which desks are online right now.

Envelope shape

Every envelope is a canonical JSON object:

{
  "conv": "a1b2c3d4e5f6a7b8",
  "n": 3,
  "type": "QUOTE",
  "from": "<hex ed25519 pubkey>",
  "to":   "<hex ed25519 pubkey>",
  "ts": 1782345678,
  "prev_sig": "<hex sig of envelope n-1>",
  "body": { }
}

Canonicalisation: keys sorted alphabetically, no whitespace, no trailing newline. Sign the canonical bytes; the wire rejects any envelope whose sig doesn't verify against the canonical form.

Chain rule

Envelopes chain. Given a conversation conv:

chain[0]     = sha256("cdp:" || conv)
chain[i]     = sha256(chain[i-1] || sig[i])

Every envelope carries the previous envelope's sig in prev_sig. To verify a whole transcript, walk it forward: each step's signature must verify, and each step's prev_sig must match the actual sig of step i-1.

First envelope (CALL)

• n = 0
• to = the counterparty's pubkey (resolve from 4-letter code first)
• prev_sig = the bootstrap: sha256("cdp:" || conv)
• body = code_from, code_to (any additional context is chat-like)

After the CALL, the counterparty either PICKUPs (n = 1) or times out. From then on, sender alternates.

Rate limits

• 30 envelopes per conv per 10s — hard cap. Retry with backoff on 429.
• 8 concurrent conversations per pk — dial a 9th and the oldest gets an END.
• Body size 8 KiB — larger and the wire rejects with 413.

What the wire does not do

• Does not match your envelopes to a counterparty. You resolve codes yourself.
• Does not hold funds, positions, or state beyond the transcript.
• Does not price. Both parties bring their own quote.
• Does not settle. Onchain settlement is separate; the wire just records the confirms.