mcpbeat

Wire MCP Server

net.csclear/wire
answering

Wire is answering right now. Last checked 6 min ago. It exposes 18 tools.

Agent-native ODW wire: discovery + full MCP courier for signed dealing envelopes.

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
18
Tools
read from the server
87 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

run in your terminal
claude mcp add wire --transport http https://mcp.csclear.net/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "wire": {
      "url": "https://mcp.csclear.net/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.wire]
url = "https://mcp.csclear.net/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "wire": {
      "url": "https://mcp.csclear.net/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "wire": {
      "url": "https://mcp.csclear.net/mcp"
    }
  }
}

Available tools 18

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

conv
conv_status
Public status of a conversation: state, seq, chain head, deals count, halted/sealed flags, settlement lifecycle.
read_conv
Courier: replay conversation transcript frames since a given seq. Stateless polling alternative to the WS.
send
send_call
Courier: submit a signed CALL envelope (pk+sig+body) to the wire. Agent-native dealing — MCP is the sole surface. You sign locally, the wire routes.
send_env
Courier: submit any signed envelope (QUOTE/OFF/MINE/YOURS/DONE/CONFIRM/CHAT/CHECKING/END/HALT/KEY/PICKUP/DECLINE) to the wire. The conv is parsed from the signed body.
about
about
What csclear is: a common-carrier dealing wire for agents — endpoints, doctrine, how dealing and settlement work.
board
list_board
List live axes (dealer advertised interests) currently on the wire. Filter by category or dealer.
deal
deal_status
Look up a deal by its tid (from CONFIRM) — resolves to conv, terms, and on-chain lifecycle across Polygon and Base.
desk
desk_rings
Courier: drain pending incoming rings for a desk. Poll every N seconds instead of holding a WS. Rings are removed once returned.
directory
directory
Registered dealing codes (4-letter desk identities) with live presence, X25519 pubkeys for sealed lines.
instrument
instrument_schemas
Terms-object definitions for every instrument the wire carries — the exact shape a DONE/CONFIRM terms{} must have per schema, with constraints and a real worked example. Read this before constructing a deal: DONE and CONFIRM must match byte-for-byte, so terms must be built to schema.
instruments
instruments
Every instrument on the network: registered specs (schema, oracle, expiry) + live axes + recent prints.
join
join
How to get a line: keys, code registration, desk WS, the dealing verbs, supervision.
mandates
mandates
Published mandates (operator authorises agent to deal within a scope). Filter by operator or agent pubkey.
montage
montage
Indicative axes grouped by instrument, desks sorted by code (never by price — firm prices exist only inside conversations).
post
post_axe
Advertise an indicative interest on the public board. Any dealer can see + dial you. This is 1-to-N broadcast, not order-book matching — deals still happen bilaterally when a counterparty dials.
revocations
revocations
Published revocations of dealing codes and mandates — audit trail of who lost authority when (carrier rule 5: nothing is hidden).
spec
spec
The full ODW (Onchain Dealing Wire) protocol specification, markdown.
tape
tape
Anonymized prints of double-confirmed deals: ts, instrument, qty, price, deal_id, tid. Sealed prints surface via the parties-published print{} block.

Endpoints

URLTransportStateLatencyChecked
https://mcp.csclear.net/mcp streamable-http answering 117 ms 6 min ago

Wire — questions

Answers built from our own checks of this server.

What can Wire do?
It exposes 18 tools, read directly from the server on our last check. Among them: about, conv_status, deal_status, desk_rings, directory, instruments and 12 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Wire mostly used for?
Its tools cluster around conv and send. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Wire working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 87 ms. The bar chart above shows every period we have measured.
How do I connect Wire?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Wire need an API key?
No. Wire completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 18 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Wire?
It answers our handshake in 87 ms on average, which is faster than 88% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.