Is the Bitcoincreditstack MCP server down?

mcp-registry/com.bitcoincreditstack/mcp · v0.2.0

healthy
Last checked 2026-10-23 01:53 UTC · handshake 596ms

As of 2026-10-23 01:53 UTC, the Bitcoincreditstack MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 5 minutes.

uptime (30d checks)
100%
checks observed
4,418
outages (90d)
3
tools
28

The Bitcoin credit markets, measured. Cross-venue rates, venue criteria, chain indicators.

Install Bitcoincreditstack MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http bitcoincreditstack-mcp-server https://mcp.bitcoincreditstack.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "bitcoincreditstack-mcp-server": {
      "type": "http",
      "url": "https://mcp.bitcoincreditstack.com/mcp"
    }
  }
}

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

Agent-readiness: B (80/100)

B (80/100): 0 error(s), 2 warning(s) across 28 tool(s); ~8,557 tokens of tool definitions.
Scores higher than 33% of 15,587 MCP servers Glimind has audited.
Its tool list costs an agent ~8,557 tokens per session — more than 65% of servers.
80 → 80 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability85
Stability20

What to fix (4)

28 of 28 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: compare_venues, get_balance_sheet, get_chain_series, get_chart, get_corporate_instruments and 23 more

Handshake + tools/list takes ~1,552 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

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 →

In the last 30 days: 0 tool(s) removed and 23 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Auto-fix: 28 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%2Fcom.bitcoincreditstack%2Fmcp/fixes

compare_venues 1 change
{
  "name": "compare_venues",
  "description": "What does credit at this tenor and LTV cost across every venue Aletheia covers? One row per venue in coverage-matrix order — no ranking, no default sort, no \"best\".\n\nStandard questions this tool answers (get_guide with question): SQ-C2.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "ltv": {
        "type": "number",
        "maximum": 1,
        "minimum": 0,
        "description": "Loan-to-value as a decimal 0–1, not a percentage."
      },
      "side": {
        "enum": [
          "borrow",
          "lend"
        ],
        "type": "string",
        "description": "'borrow' (what a borrower pays, the default) or 'lend' (what a capital provider earns)."
      },
      "class": {
        "enum": [
          "algorithmic",
          "minted",
          "auction",
          "posted-card",
          "corporate"
        ],
        "type": "string",
        "description": "Restrict to one credit class. The whole matrix is every venue in the registry; one class is a fraction of it."
      },
      "venues": {
        "type": "string",
        "description": "Comma-separated registry ids to restrict the rows to, e.g. 'aave_v3_ethereum,cefi_ledn'."
      },
      "collateral": {
        "enum": [
          "btc",
          "eth"
        ],
        "type": "string",
        "description": "Bitcoin by default; pass collateral: 'eth' for credit secured by ether (ether, staking and restaking tokens at their own contract rates), measured the same way and never added to bitcoin."
      },
      "tenor_days": {
        "type": "number",
        "description": "Loan term in days to compare at.",
        "exclusiveMinimum": 0
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Credit cost across venues"
}
get_balance_sheet 1 change
{
  "name": "get_balance_sheet",
  "description": "Who holds the mined bitcoin, as each holder states it, and how much of it is pledged, wrapped or lent out. One line per holder (companies, spot funds, wrapped-token reserves, custodians, exchanges, governments), each with its figure or a range, its date, its source and a grade (A stated units; B units by a stated rule; C the holder's own unchecked statement; D inferred outside primary sources), or an absence with its reason, never zero. A coin is counted once, at its owner: what a custodian hold",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "as_of": {
        "type": "string",
        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
        "description": "A date the sheet was written (YYYY-MM-DD); the latest by default"
      },
      "quarter": {
        "type": "string",
        "pattern": "^\\d{4}-Q[1-4]$",
        "description": "A quarter (YYYY-Qn): the sheet of that quarter's last day"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Balance sheet of the mined bitcoin"
}
get_chain_series 1 change
{
  "name": "get_chain_series",
  "description": "Returns one series from Aletheia's vintage store, by id (see list_chain_series): every value with its date and kind, the series' unit, source and limitation, and the vintages the values came from. With as_known_on, returns the series exactly as the store held it at the end of that day (UTC), so a past answer can be reproduced.\n\nChain series reach back to 2009 and are day-granular. Priced values (realised value, MVRV, SOPR, hashprice in USD) value each coin at the price of the day it was created:",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string",
        "description": "Series id, e.g. chain.cohort.supply_btc, chain.cohort.mvrv, miner.hpx_btc, price.btc_in_basket, fx.eur"
      },
      "to": {
        "type": "string",
        "description": "Last date, YYYY-MM-DD"
      },
      "from": {
        "type": "string",
        "description": "First date, YYYY-MM-DD"
      },
      "as_known_on": {
        "type": "string",
        "description": "YYYY-MM-DD: the series as the store held it at the end of that day (UTC)"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "One chain, miner or price series through time"
}

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/com.bitcoincreditstack/mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.bitcoincreditstack/mcp"}) 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%2Fcom.bitcoincreditstack%2Fmcp.svg)](https://glimind.com/server/mcp-registry%2Fcom.bitcoincreditstack%2Fmcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.bitcoincreditstack%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.bitcoincreditstack%2Fmcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.bitcoincreditstack%2Fmcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.bitcoincreditstack%2Fmcp?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:0747c04267e17b52…, first seen 2026-10-22, included at leaf 45198 of 49,340. Version history · verify what your client received.

Tools (28)

Compare: most reliable data servers · most reliable retrieval servers · most reliable finance servers · most reliable media servers · most reliable knowledge 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 Bitcoincreditstack MCP server down right now?

As of 2026-10-23 01:53 UTC, the Bitcoincreditstack MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 5 minutes.

How many tools does Bitcoincreditstack MCP server provide?

Bitcoincreditstack MCP server advertises 28 tools, including compare_venues, get_balance_sheet, get_chain_series, get_chart, get_corporate_instruments.

How do I install Bitcoincreditstack MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.bitcoincreditstack.com/mcp

Is the Bitcoincreditstack MCP server safe to connect to an AI agent?

Glimind scanned all 28 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 Bitcoincreditstack 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