Is the Csclear Wire MCP server down?

mcp-registry/net.csclear/wire · v2.0.0

Also listed as mcp-registry/net.csclear/venue · primary listing: mcp-registry/net.csclear/venue

healthy
Last checked 2026-10-19 23:13 UTC · handshake 90ms

As of 2026-10-19 23:13 UTC, the Csclear Wire MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
3,880
outages (90d)
0
tools
18

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

Install Csclear Wire MCP server

Add to Cursor Add to VS Code

Claude Code

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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (76/100)

C (76/100): 0 error(s), 3 warning(s) across 18 tool(s); ~1,484 tokens of tool definitions.
Scores higher than 13% of 15,377 MCP servers Glimind has audited.
Its tool list costs an agent ~1,484 tokens per session — lighter than 60% of servers.
74 → 76 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions71
Safety hints7
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (4)

18 of 18 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: about, conv_status, deal_status, desk_rings, directory and 13 more

6 parameter(s) across 5 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: conv_status, deal_status, desk_rings, mandates, read_conv

3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: post_axe, send_call, send_env

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 7 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 5 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fnet.csclear%2Fwire/fixes

conv_status 1 change 
{
  "name": "conv_status",
  "description": "Public status of a conversation: state, seq, chain head, deals count, halted/sealed flags, settlement lifecycle.",
  "inputSchema": {
    "type": "object",
    "required": [
      "conv"
    ],
    "properties": {
      "conv": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
deal_status 1 change 
{
  "name": "deal_status",
  "description": "Look up a deal by its tid (from CONFIRM) — resolves to conv, terms, and on-chain lifecycle across Polygon and Base.",
  "inputSchema": {
    "type": "object",
    "required": [
      "tid"
    ],
    "properties": {
      "tid": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
list_board 1 change 
{
  "name": "list_board",
  "description": "List live axes (dealer advertised interests) currently on the wire. Filter by category or dealer.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "side": {
        "type": "string",
        "description": "BID|OFFER|all (default all)"
      },
      "category": {
        "type": "string",
        "description": "spot|fx|options|rates|all (default all)"
      },
      "operator_pk": {
        "type": "string",
        "description": "filter to one dealer's axes"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/net.csclear/wire"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/net.csclear/wire"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fnet.csclear%2Fwire.svg)](https://glimind.com/server/mcp-registry%2Fnet.csclear%2Fwire?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fnet.csclear%2Fwire?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fnet.csclear%2Fwire.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fnet.csclear%2Fwire.svg
   :target: https://glimind.com/server/mcp-registry%2Fnet.csclear%2Fwire?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:b6ddc67f9b06d419…, first seen 2026-10-17, included at leaf 999 of 29,371. Version history · verify what your client received.

Tools (18)

Compare: most reliable knowledge servers · most reliable data servers · most reliable other servers · most reliable communication servers · most reliable database servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Csclear Wire MCP server down right now?

As of 2026-10-19 23:13 UTC, the Csclear Wire MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Csclear Wire MCP server provide?

Csclear Wire MCP server advertises 18 tools, including about, conv_status, deal_status, desk_rings, directory.

How do I install Csclear Wire MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.csclear.net/mcp

Is the Csclear Wire MCP server safe to connect to an AI agent?

Glimind scanned all 18 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Csclear Wire MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve