net.csclear/wire

by csclear.net · remote · no sign-in to list tools · v2.2.0 · published by net.csclear

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

Final · 2Changes · 12

Compare Registry entry

18 tools: 2 do something that can't be undone, 12 change things and 4 only read.

Scanned Oct 21, 2026

Deletes or cancels0Claude Code: deny
Can't be undone2Claude Code: ask: see these tools
Changes things12Claude Code: ask: see these tools
Only reads4Claude Code: allow: see these tools

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http wire https://mcp.csclear.net/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

18 tools

Can't be undone 2Sends, pays, publishes or merges: once done, it cannot be taken back.Claude Code: ask

send_callCourier: submit a signed CALL envelope (pk+sig+body) to the wire.No findings
Why it is in this group
- The name "send_call" says "send": a word for sending, and what is sent cannot be taken back.
Description, as the server wrote it
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_envCourier: submit any signed envelope (QUOTE/OFF/MINE/YOURS/DONE/CONFIRM/CHAT/CHECKING/END/HALT/KEY/PICKUP/DECLINE) to the wire.No findings
Why it is in this group
- The name "send_env" says "send": a word for sending, and what is sent cannot be taken back.
Description, as the server wrote it
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.

Changes things 12Creates or changes something that can be changed back.Claude Code: ask

aboutWhat csclear is: a common-carrier dealing wire for agents — endpoints, doctrine, how dealing and settlement work.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it
What csclear is: a common-carrier dealing wire for agents — endpoints, doctrine, how dealing and settlement work.
desk_ringsCourier: drain pending incoming rings for a desk.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it
Courier: drain pending incoming rings for a desk. Poll every N seconds instead of holding a WS. Rings are removed once returned.
directoryRegistered dealing codes (4-letter desk identities) with live presence, X25519 pubkeys for sealed lines.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it
Registered dealing codes (4-letter desk identities) with live presence, X25519 pubkeys for sealed lines.
instrument_schemasTerms-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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it
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.
instrumentsEvery instrument on the network: registered specs (schema, oracle, expiry) + live axes + recent prints.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it
Every instrument on the network: registered specs (schema, oracle, expiry) + live axes + recent prints.
joinHow to get a line: keys, code registration, desk WS, the dealing verbs, supervision.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it
How to get a line: keys, code registration, desk WS, the dealing verbs, supervision.
mandatesPublished mandates (operator authorises agent to deal within a scope).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it
Published mandates (operator authorises agent to deal within a scope). Filter by operator or agent pubkey.
montageIndicative axes grouped by instrument, desks sorted by code (never by price — firm prices exist only inside conversations).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it
Indicative axes grouped by instrument, desks sorted by code (never by price — firm prices exist only inside conversations).
post_axeAdvertise an indicative interest on the public board.No findings
Why it is in this group
- The name "post_axe" says "post": a word for a change.
Description, as the server wrote it
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.
revocationsPublished revocations of dealing codes and mandates — audit trail of who lost authority when (carrier rule 5: nothing is hidden).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it
Published revocations of dealing codes and mandates — audit trail of who lost authority when (carrier rule 5: nothing is hidden).
specThe full ODW (Onchain Dealing Wire) protocol specification, markdown.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it
The full ODW (Onchain Dealing Wire) protocol specification, markdown.
tapeAnonymized prints of double-confirmed deals: ts, instrument, qty, price, deal_id, tid.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it
Anonymized prints of double-confirmed deals: ts, instrument, qty, price, deal_id, tid. Sealed prints surface via the parties-published print{} block.

Only reads 4Looks things up and changes nothing.Claude Code: allow

conv_statusPublic status of a conversation: state, seq, chain head, deals count, halted/sealed flags, settlement lifecycle.No findings
Why it is in this group
- The name "conv_status" says "status": a word for reading.
Description, as the server wrote it
Public status of a conversation: state, seq, chain head, deals count, halted/sealed flags, settlement lifecycle.
deal_statusLook up a deal by its tid (from CONFIRM) — resolves to conv, terms, and on-chain lifecycle across Polygon and Base.No findings
Why it is in this group
- The name "deal_status" says "status": a word for reading.
Description, as the server wrote it
Look up a deal by its tid (from CONFIRM) — resolves to conv, terms, and on-chain lifecycle across Polygon and Base.
list_boardList live axes (dealer advertised interests) currently on the wire.No findings
Why it is in this group
- The name "list_board" says "list": a word for reading.
Description, as the server wrote it
List live axes (dealer advertised interests) currently on the wire. Filter by category or dealer.
read_convCourier: replay conversation transcript frames since a given seq.No findings
Why it is in this group
- The name "read_conv" says "read": a word for reading.
Description, as the server wrote it
Courier: replay conversation transcript frames since a given seq. Stateless polling alternative to the WS.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 2.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http wire https://mcp.csclear.net/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__wire__conv_status",
      "mcp__wire__deal_status",
      "mcp__wire__read_conv",
      "mcp__wire__list_board"
    ],
    "ask": [
      "mcp__wire__about",
      "mcp__wire__directory",
      "mcp__wire__montage",
      "mcp__wire__tape",
      "mcp__wire__instruments",
      "mcp__wire__instrument_schemas",
      "mcp__wire__mandates",
      "mcp__wire__revocations",
      "mcp__wire__join",
      "mcp__wire__spec",
      "mcp__wire__send_call",
      "mcp__wire__send_env",
      "mcp__wire__desk_rings",
      "mcp__wire__post_axe"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as wire. Review it before you use it.

Keep track

Get told when this server's tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/net.csclear/wire/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Anlyon alternative

14 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Compare with other servers for the same product.

Source: MCP Registry. Synced Oct 21, 2026, 18:53 UTC.

For agents: Markdown · JSON · report this listing