mcpbeat Sign in

Bitcoincreditstack MCP Server

by bitcoincreditstack Your server? Claim it
answering

Bitcoincreditstack is answering right now. Last checked 3 min ago. It exposes 13 tools. Last commit 16 Sep 2026.

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

Uptime history 25 days of history
25 days agonow
100.0%
Uptime 24h
91 of 91 checks
13
Tools
read from the server
59 ms
Response time
average over 24h
0
Stars
last commit 16 Sep 2026

What changed 6

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 31 August 2026. No other catalogue keeps this.

16 Sep a tool changed the parameters it asks for compare_venues
31 Aug 2 tool descriptions were rewritten get_indicator, list_indicators
31 Aug 2 tools changed the parameters they ask for get_indicator, get_mvrv
31 Aug a tool appeared get_lens

Nothing serious here today

Today is the operative word: we check Bitcoincreditstack every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add mcp --transport http https://mcp.bitcoincreditstack.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.bitcoincreditstack.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.bitcoincreditstack.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.bitcoincreditstack.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.bitcoincreditstack.com/mcp"
    }
  }
}

Available tools 13

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

credit
get_credit_state
What does Bitcoin-collateralised credit cost and how much of it is outstanding, across the venues this dataset covers? One reading aggregated over the venue universe, not any single venue's book. Carries the term structure, outstanding quantity, valuation, collateral mix and quality composition, with the coverage block stating how many venues contributed and naming the ones that did not. No venue is weighted up, floated or reported under its own heading. ⚠ Read coverage before reading the figures. A venue absent from this reading is a declared gap, not a zero, and the rows it would have contributed are counted separately as unavailable.
get_credit_state_history
How has the Bitcoin credit surface moved? The same cross-venue reading as get_credit_state, as a daily series. Each point carries the coverage that produced it, so a change in the series and a change in which venues were observable can be told apart. This is descriptive data; it does not forecast and it does not characterise a trend. ⚠ Coverage is not constant through the series. A move in a figure may be a move in the market or a venue entering or leaving observation — the per-point coverage is what distinguishes them.
market
get_market_composition
What kinds of credit make up this market, and in what proportions? ⚠ These series are computed from MORPHO BLUE ONLY, on Ethereum and Base. They are not market-wide. Composition by rate type, recourse and instrument, reported as observed shares with the scope that produced them. There is no ranking of venues or instrument types and no judgement about which composition is preferable. ⚠ The scope block names the contributing venues and states why the others are absent — Aave v3 is mid-backfill, Compound v3 and Sky are not yet ingested. Read it before quoting any share. A percentage from this tool describes one venue family, not Bitcoin-collateralised credit.
get_market_flows
How much credit was created and retired, and over what period? Latest, trailing 30 days, and since inception. ⚠ These series are computed from MORPHO BLUE ONLY, on Ethereum and Base. They are not market-wide. Counts and amounts as observed, with the scope, coverage and validation state that produced them. Not a forecast, not a momentum signal, and not a characterisation of demand. ⚠ Creation and retirement are GROSS and are never netted into one signed series: a day of heavy churn and a quiet day can net to the same number and are not the same market. USD-denominated debt only.
compare
compare_venues
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".
indicator
get_indicator
Returns the current value of a single Aletheia indicator by id, with its methodology reference. This server serves the venue-independent indicator set; an indicator anchored on a single venue's own rate is served by that venue's own MCP and answers here with a pointer to it. Call list_indicators first to discover valid ids. Optionally returns the historical series instead of the current value (set include_history). History is free and unmetered on the same terms as the current value. This is descriptive data; no recommendation is provided. An indicator that has no reading on this network says so explicitly rather than returning a null or a zero that could be mistaken for a value.
indicators
list_indicators
Returns the catalogue of Aletheia indicators measured across the Bitcoin-collateralised credit markets and the Bitcoin chain: id, name, family, units, description, and whether the indicator is currently live on this network. Three families: 'credit' (credit-market assessments), 'onchain' (commodity chain metrics such as MVRV and SOPR), and 'market' (external context — DeFi rates, stablecoin supply, macro). Use this to discover what is available, then call get_indicator with an id. This tool returns a catalogue; it does not rank indicators or advise which to use. Indicators anchored on a single venue's own rate are not served here; they are listed as withheld, with the server that serves them.
lens
get_lens
Returns a READING LENS: a presentation procedure for this dataset, written for a particular kind of reader. A lens selects which tools to use and frames how their output is presented; it never concludes, never ranks, and carries no write tool — this server has none. Call with no argument to list the lenses. Call with one to get its full procedure: what to lead with, the tools in its scope, and — the part that matters most — what that lens explicitly does not do. Reading a lens before presenting anything from this dataset is the intended use. It is guidance for presentation, not data about the market, and it adds no figures of its own.
mvrv
get_mvrv
Returns the current Bitcoin MVRV ratio: market capitalisation divided by realised capitalisation, where realised cap values each coin at the price it last moved. MVRV is therefore an identity on observed chain data. It states the aggregate unrealised position of the supply — how far the market values coins above or below what was last paid for them — and nothing about what follows from that. This tool returns data; it does not advise, forecast, or characterise the market. Computed nightly from Aletheia's own full node and UTXO set. 'mvrv_z_score' is returned alongside it: the same numerator measured in standard deviations of the historical market-cap series. Returns: { value, mvrv_z_score, as_of, inputs: { market_cap_usd, realised_cap_usd, realised_price_usd, spot_price_usd }, methodology, disclaimer }.
onchain
list_onchain_indicators
Returns the catalog of available on-chain indicator tools, including tool name, indicator name, brief description, units, an example invocation, and current readiness status ('live' or 'pending'). Use this when you need to discover which tools are available for on-chain analysis without inspecting every tool definition.
venue
get_venue
What is known about this venue, criterion by criterion? The three pillars — Price, Quality, Composition — each cell with its value and the source it came from. The criteria are published and versioned before any venue is measured against them, applied evenly to every row, and the spec version rides in this payload. There is no composite score, no stars and no reliability index: a reader weighs the criteria, and this server does not weigh them for the reader. ⚠ 'unknown' is a value, not an omission — a criterion that cannot be established from public sources says so with its reason. A class-specific 'not_applicable' and an unresearched 'unknown' are different answers and are never conflated.
venues
list_venues
Which credit venues does this dataset cover, and what is known about each? Returns the registry rows matching the filters you supply. One row per venue across four classes — on-chain protocols, CeFi desks, the corporate layer, and auction venues — each carrying its coverage state per pillar and how many of its criteria cells have been researched. Does not rank, score or order by any rate: rows are returned in the registry's own order. All filters are optional and unspecified means no constraint. ⚠ A venue's presence is not a statement about it. Coverage 'none' means nothing is ingested yet, which is a declared gap, not an observation about the venue.
verification
get_verification_bundle
What can be checked about the contracts, and what did the last check return? Observations with their block heights; the verdict is the reader's. Contract addresses and their implementations, the bytecode hash of each, the upgradeability position, the privileged-function map with whether each can touch user funds, the audit reference, and five structural promises — each with the check that would falsify it and what that check returned. ⚠ Read the fields, not the impression. 'match' is "unchecked" where Aletheia has not compared deployed bytecode against verified source; a promise that did not settle says so; and mainnet and testnet return different answers because they run different builds. There is no safety score, rating or verified badge in this payload, and none will be added.

Endpoints

URLTransportStateLatencyChecked
https://mcp.bitcoincreditstack.com/mcp streamable-http answering 75 ms 3 min ago

Alternatives to Bitcoincreditstack

same job, measured the same way
Blockchainacademics
by blockchainacademics

Crypto MCP — 99 tools across news, market, on-chain, sentiment, indicators, agent generation.

63 installs/wk local only
LastLook Data
by zev-lll

FRED macro data, Treasury yields, FX rates & macro indicators for AI agents. Pay-per-query via x402.

24 tools answering
CNN Fear & Greed Index
by wildsurfer

CNN's Fear & Greed index for the US stock market: score, rating, indicators and daily history.

local only
Polymarket Kalshi Trading
by oddsrail

Cross-venue prediction markets for AI agents: Polymarket + Kalshi, costed and attributed

answering
Market Spread
by pipeworx-io

market-spread MCP — cross-venue prediction-market landscape scanner.

33 tools answering
ClearMarket
by clearmarket

Reference data for prediction markets: graded resolution clarity, cross-venue links, provenance.

6 tools answering
Mantis
by alfred768

Cross-venue prediction market routing for AI agents with arbitrage, quotes, history, and signals.

6 tools answering
RAVN
by ravn

Cross-chain swap aggregator across 16+ chains, incl. native Bitcoin/Solana. 0% fees, non-custodial.

10 tools answering

Bitcoincreditstack — questions

Answers built from our own checks of this server.

What can Bitcoincreditstack do?
It exposes 13 tools, read directly from the server on our last check. Among them: compare_venues, get_credit_state, get_credit_state_history, get_indicator, get_lens, get_market_composition and 7 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Bitcoincreditstack mostly used for?
Its tools cluster around credit and market. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Bitcoincreditstack working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 59 ms. The bar chart above shows every period we have measured.
How do I connect Bitcoincreditstack?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Bitcoincreditstack need an API key?
No. Bitcoincreditstack completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 13 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Bitcoincreditstack?
It answers our handshake in 59 ms on average, which is faster than 98% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Bitcoincreditstack open source?
We cannot say either way: written in TypeScript and 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.