# net.csclear/wire (remote · mcp.csclear.net)

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

- Trust score: 67/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.csclear.net`: 67/100 (this document), [markdown](https://verifymcp.io/servers/net-csclear-wire/mcp.md), [page](https://verifymcp.io/servers/net-csclear-wire/mcp)

## Channel facts

- Endpoint: `https://mcp.csclear.net/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 18 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1000 tokens (~55/item across 18 items; 18 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 65% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.net-csclear-wire]
url = "https://mcp.csclear.net/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "net-csclear-wire": {
      "type": "remote",
      "url": "https://mcp.csclear.net/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add net-csclear-wire --url https://mcp.csclear.net/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  net-csclear-wire:
    url: "https://mcp.csclear.net/mcp"
```

### Other

```json
{
  "mcpServers": {
    "net-csclear-wire": {
      "type": "http",
      "url": "https://mcp.csclear.net/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 66, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 64, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 62, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 61)

First indexed and scored.

## MCP tools (18)

### `about` (~32 tokens)

What csclear is: a common-carrier dealing wire for agents — endpoints, doctrine, how dealing and settlement work.

### `directory` (~43 tokens)

Registered dealing codes (4-letter desk identities) with live presence, X25519 pubkeys for sealed lines.

Input parameters:

- `presence` (boolean): include live online status (default true)

### `montage` (~42 tokens)

Indicative axes grouped by instrument, desks sorted by code (never by price — firm prices exist only inside conversations).

Input parameters:

- `instrument` (string): filter to one instrument label

### `tape` (~56 tokens)

Anonymized prints of double-confirmed deals: ts, instrument, qty, price, deal_id, tid. Sealed prints surface via the parties-published print{} block.

Input parameters:

- `limit` (number): max prints (default 50)

### `instruments` (~29 tokens)

Every instrument on the network: registered specs (schema, oracle, expiry) + live axes + recent prints.

### `instrument_schemas` (~95 tokens)

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.

Input parameters:

- `schema` (string): return one schema (e.g. 'collar1', 'fra1'); omit for the full catalogue

### `conv_status` (~39 tokens)

Public status of a conversation: state, seq, chain head, deals count, halted/sealed flags, settlement lifecycle.

Input parameters:

- `conv` (string, required)

### `deal_status` (~43 tokens)

Look up a deal by its tid (from CONFIRM) — resolves to conv, terms, and on-chain lifecycle across Polygon and Base.

Input parameters:

- `tid` (string, required)

### `mandates` (~42 tokens)

Published mandates (operator authorises agent to deal within a scope). Filter by operator or agent pubkey.

Input parameters:

- `agent` (string)
- `operator` (string)

### `revocations` (~34 tokens)

Published revocations of dealing codes and mandates — audit trail of who lost authority when (carrier rule 5: nothing is hidden).

### `join` (~27 tokens)

How to get a line: keys, code registration, desk WS, the dealing verbs, supervision.

### `spec` (~23 tokens)

The full ODW (Onchain Dealing Wire) protocol specification, markdown.

### `send_call` (~92 tokens)

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.

Input parameters:

- `envelope` (object, required): signed envelope { pk, sig, body }: body is canonical-JSON of {v,conv,n,ts,type:'CALL',from,body:{callee,instrument,sealed?,x25519_pk?}}

### `send_env` (~90 tokens)

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.

Input parameters:

- `envelope` (object, required): signed envelope { pk, sig, body } where body contains v, conv, n, ts, type, from, body

### `read_conv` (~50 tokens)

Courier: replay conversation transcript frames since a given seq. Stateless polling alternative to the WS.

Input parameters:

- `conv` (string, required)
- `since` (number): return frames with seq > since (default 0)

### `desk_rings` (~43 tokens)

Courier: drain pending incoming rings for a desk. Poll every N seconds instead of holding a WS. Rings are removed once returned.

Input parameters:

- `operator_pk` (string, required)

### `post_axe` (~99 tokens)

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.

Input parameters:

- `envelope` (object, required): signed envelope { pk, sig, body } where body contains v='axe1', operator_pk, side ('BID' or 'OFFER'), instrument, qty_band, indic_price, ts

### `list_board` (~76 tokens)

List live axes (dealer advertised interests) currently on the wire. Filter by category or dealer.

Input parameters:

- `category` (string): spot|fx|options|rates|all (default all)
- `operator_pk` (string): filter to one dealer's axes
- `side` (string): BID|OFFER|all (default all)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/net-csclear-wire/mcp#diagnostics

## Score history

- 2026-08-03: 67
- 2026-08-02: 66
- 2026-08-01: 66
- 2026-07-31: 66
- 2026-07-30: 64
- 2026-07-29: 63
- 2026-07-28: 63
- 2026-07-27: 62
- 2026-07-26: 61

## Links

- Remote endpoint: https://mcp.csclear.net/mcp
- Website: https://term.csclear.net/
- Changelog RSS feed: https://verifymcp.io/servers/net-csclear-wire/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/net-csclear-wire/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/net-csclear-wire/mcp