Is the Bsv Cx MCP server down?

mcp-registry/cx.bsv/bsv-cx · v0.1.1

healthy
Last checked 2026-10-24 20:52 UTC · handshake 574ms

As of 2026-10-24 20:52 UTC, the Bsv Cx MCP server is up with a Glimind reliability score of 79/100 (grade B). Over the last 30 days it answered 99.3% of Glimind's liveness checks. It had 55 outages in 90 days, with a median recovery of 8 minutes.

uptime (30d checks)
99.3%
checks observed
4,495
outages (90d)
55
tools
9

Timestamp & verify evidence on-chain, free. Proofpack: a portable BEEF+BUMP proof bundle per txid.

Install Bsv Cx MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http bsv-cx-mcp-server https://bsv.cx/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "bsv-cx-mcp-server": {
      "type": "http",
      "url": "https://bsv.cx/mcp"
    }
  }
}

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

Agent-readiness: B (82/100)

B (82/100): 0 error(s), 2 warning(s) across 9 tool(s); ~1,569 tokens of tool definitions.
Scores higher than 36% of 15,657 MCP servers Glimind has audited.
Its tool list costs an agent ~1,569 tokens per session — lighter than 60% of servers.
81 → 82 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints11
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (3)

9 of 9 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: archive_url, batch_timestamp, get_archive, notarize_hash, proofpack and 4 more

1 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: archive_url

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: 6 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcx.bsv%2Fbsv-cx/fixes

archive_url 1 change
{
  "name": "archive_url",
  "description": "Capture a web page as it looks right now — screenshot and text — and anchor a hash of that capture on-chain. Use this before relying on a page you cite, so a later edit or deletion cannot be denied. Free.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "url"
    ],
    "properties": {
      "url": {
        "type": "string",
        "format": "uri",
        "description": "the page to capture"
      },
      "thorough": {
        "type": "boolean",
        "description": "wait for lazy-loaded content; slower but better for long or image-heavy pages"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": true
  },
  "title": "Archive a web page with an on-chain timestamp"
}
get_archive 1 change
{
  "name": "get_archive",
  "description": "Fetch the manifest for a previous archive_url capture: when it was taken, and its proof. Free.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "hash"
    ],
    "properties": {
      "hash": {
        "type": "string",
        "pattern": "^[0-9a-fA-F]{64}$",
        "description": "the capture hash returned by archive_url"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": true
  },
  "title": "Retrieve an archived page capture"
}
proofpack 1 change
{
  "name": "proofpack",
  "description": "For any CONFIRMED BSV transaction id, get a freshly SPV-verified bundle: BEEF (BRC-62) and BUMP (BRC-74) plus bsv.cx's own self-synced header-tip attestation. bsv.cx fetches the Merkle proof and folds it against block headers it syncs over the BSV P2P network BEFORE serving, so you receive a bundle that already confirms — verifiable by any @bsv/sdk client with no bsv.cx-specific code. Verification itself is free at /spv/verify; this does the fetch + fold + package for you and is priced per call ",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "txid"
    ],
    "properties": {
      "txid": {
        "type": "string",
        "pattern": "^[0-9a-fA-F]{64}$",
        "description": "the confirmed transaction id to package a proof bundle for"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Get a portable, pre-verified proof bundle for a transaction"
}

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/cx.bsv/bsv-cx"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/cx.bsv/bsv-cx"}) 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%2Fcx.bsv%2Fbsv-cx.svg)](https://glimind.com/server/mcp-registry%2Fcx.bsv%2Fbsv-cx?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcx.bsv%2Fbsv-cx?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcx.bsv%2Fbsv-cx.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcx.bsv%2Fbsv-cx.svg
   :target: https://glimind.com/server/mcp-registry%2Fcx.bsv%2Fbsv-cx?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:6f5392afd003abc7…, first seen 2026-10-17, included at leaf 1265 of 61,224. Version history · verify what your client received.

Tools (9)

Compare: most reliable web servers · most reliable security servers · most reliable other servers · most reliable devops 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 Bsv Cx MCP server down right now?

As of 2026-10-24 20:52 UTC, the Bsv Cx MCP server is up with a Glimind reliability score of 79/100 (grade B). Over the last 30 days it answered 99.3% of Glimind's liveness checks. It had 55 outages in 90 days, with a median recovery of 8 minutes.

How many tools does Bsv Cx MCP server provide?

Bsv Cx MCP server advertises 9 tools, including archive_url, batch_timestamp, get_archive, notarize_hash, proofpack.

How do I install Bsv Cx MCP server?

Point your MCP client at this streamable-http endpoint: https://bsv.cx/mcp

Is the Bsv Cx MCP server safe to connect to an AI agent?

Glimind scanned all 9 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 Bsv Cx 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