net.csclear/wire
REMOTE · MCP.CSCLEAR.NET · SCANNED SEP 20
Agent-native ODW wire: discovery + full MCP courier for signed dealing envelopes.
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1000 tokens (~55/item across 18 items; 18 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 65% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_call" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the net.csclear/wire MCP server?
net.csclear/wire is a hosted endpoint at https://mcp.csclear.net/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.csclear.net
claude mcp add --transport http net-csclear-wire 'https://mcp.csclear.net/mcp'
{
"mcpServers": {
"net-csclear-wire": {
"url": "https://mcp.csclear.net/mcp"
}
}
} {
"servers": {
"net-csclear-wire": {
"type": "http",
"url": "https://mcp.csclear.net/mcp"
}
}
} [mcp_servers.net-csclear-wire] url = "https://mcp.csclear.net/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"net-csclear-wire": {
"type": "remote",
"url": "https://mcp.csclear.net/mcp",
"enabled": true
}
}
} openclaw mcp add net-csclear-wire --url 'https://mcp.csclear.net/mcp' --transport streamable-http
mcp_servers:
net-csclear-wire:
url: "https://mcp.csclear.net/mcp" {
"McpServers": {
"net-csclear-wire": {
"Transport": "http",
"Url": "https://mcp.csclear.net/mcp"
}
}
} assistant mcp add net-csclear-wire -t streamable-http -u 'https://mcp.csclear.net/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.csclear.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=csclear.net | CN=WE1,O=Google Trust Services,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | b56f81f41cd9c291133d76ce4062c18d |
| SANs: csclear.net, mcp.csclear.net, *.mcp.csclear.net | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.csclear.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| csclear.net. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'none'; frame-ancestors 'none'; base-uri 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.csclear.net/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.csclear.net/mcp | HTTPS enforced | 301 | https://mcp.csclear.net/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
about ~32
What csclear is: a common-carrier dealing wire for agents — endpoints, doctrine, how dealing and settlement work.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
conv_status ~39
Public status of a conversation: state, seq, chain head, deals count, halted/sealed flags, settlement lifecycle.
| Name | Type | Req | Description |
|---|---|---|---|
| conv | string | yes | – |
No output schema declared.
No examples provided.
deal_status ~43
Look up a deal by its tid (from CONFIRM) — resolves to conv, terms, and on-chain lifecycle across Polygon and Base.
| Name | Type | Req | Description |
|---|---|---|---|
| tid | string | yes | – |
No output schema declared.
No examples provided.
desk_rings ~43
Courier: drain pending incoming rings for a desk. Poll every N seconds instead of holding a WS. Rings are removed once returned.
| Name | Type | Req | Description |
|---|---|---|---|
| operator_pk | string | yes | – |
No output schema declared.
No examples provided.
directory ~43
Registered dealing codes (4-letter desk identities) with live presence, X25519 pubkeys for sealed lines.
| Name | Type | Req | Description |
|---|---|---|---|
| presence | boolean | – | include live online status (default true) |
No output schema declared.
No examples provided.
instrument_schemas ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| schema | string | – | return one schema (e.g. 'collar1', 'fra1'); omit for the full catalogue |
No output schema declared.
No examples provided.
instruments ~29
Every instrument on the network: registered specs (schema, oracle, expiry) + live axes + recent prints.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
join ~27
How to get a line: keys, code registration, desk WS, the dealing verbs, supervision.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_board ~76
List live axes (dealer advertised interests) currently on the wire. Filter by category or dealer.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
mandates ~42
Published mandates (operator authorises agent to deal within a scope). Filter by operator or agent pubkey.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | – |
| operator | string | – | – |
No output schema declared.
No examples provided.
montage ~42
Indicative axes grouped by instrument, desks sorted by code (never by price — firm prices exist only inside conversations).
| Name | Type | Req | Description |
|---|---|---|---|
| instrument | string | – | filter to one instrument label |
No output schema declared.
No examples provided.
post_axe ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| envelope | object | yes | signed envelope { pk, sig, body } where body contains v='axe1', operator_pk, side ('BID' or 'OFFER'), instrument, qty_band, indic_price, ts |
No output schema declared.
No examples provided.
read_conv ~50
Courier: replay conversation transcript frames since a given seq. Stateless polling alternative to the WS.
| Name | Type | Req | Description |
|---|---|---|---|
| conv | string | yes | – |
| since | number | – | return frames with seq > since (default 0) |
No output schema declared.
No examples provided.
revocations ~34
Published revocations of dealing codes and mandates — audit trail of who lost authority when (carrier rule 5: nothing is hidden).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
send_call ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| envelope | object | yes | signed envelope { pk, sig, body }: body is canonical-JSON of {v,conv,n,ts,type:'CALL',from,body:{callee,instrument,sealed?,x25519_pk?}} |
No output schema declared.
No examples provided.
send_env ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| envelope | object | yes | signed envelope { pk, sig, body } where body contains v, conv, n, ts, type, from, body |
No output schema declared.
No examples provided.
spec ~23
The full ODW (Onchain Dealing Wire) protocol specification, markdown.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tape ~56
Anonymized prints of double-confirmed deals: ts, instrument, qty, price, deal_id, tid. Sealed prints surface via the parties-published print{} block.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | max prints (default 50) |
No output schema declared.
No examples provided.
What is the net.csclear/wire MCP server?
net.csclear/wire is an MCP server listed in the public MCP registry as net.csclear/wire. Agent-native ODW wire: discovery + full MCP courier for signed dealing envelopes. This page covers its hosted endpoint (https://mcp.csclear.net/mcp).
Is the net.csclear/wire MCP server safe to use?
net.csclear/wire scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the net.csclear/wire MCP server expose?
net.csclear/wire exposes 18 tools: about, directory, montage, tape, instruments, and 13 more. Their descriptions and schemas cost roughly 955 tokens of context every time the server is loaded.
Does the net.csclear/wire MCP server require authentication?
No. We connected to net.csclear/wire without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the net.csclear/wire MCP server still maintained?
net.csclear/wire is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.