com.bitcoincreditstack/mcp
REMOTE · MCP.BITCOINCREDITSTACK.COM · SCANNED SEP 20
The Bitcoin credit markets, measured. Cross-venue rates, venue criteria, chain indicators.
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 Security57
- 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 13 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2771 tokens (~197/item across 14 items; 13 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 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 com.bitcoincreditstack/mcp server?
com.bitcoincreditstack/mcp is a hosted endpoint at https://mcp.bitcoincreditstack.com/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.bitcoincreditstack.com
claude mcp add --transport http com-bitcoincreditstack-mcp 'https://mcp.bitcoincreditstack.com/mcp'
{
"mcpServers": {
"com-bitcoincreditstack-mcp": {
"url": "https://mcp.bitcoincreditstack.com/mcp"
}
}
} {
"servers": {
"com-bitcoincreditstack-mcp": {
"type": "http",
"url": "https://mcp.bitcoincreditstack.com/mcp"
}
}
} [mcp_servers.com-bitcoincreditstack-mcp] url = "https://mcp.bitcoincreditstack.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-bitcoincreditstack-mcp": {
"type": "remote",
"url": "https://mcp.bitcoincreditstack.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-bitcoincreditstack-mcp --url 'https://mcp.bitcoincreditstack.com/mcp' --transport streamable-http
mcp_servers:
com-bitcoincreditstack-mcp:
url: "https://mcp.bitcoincreditstack.com/mcp" {
"McpServers": {
"com-bitcoincreditstack-mcp": {
"Transport": "http",
"Url": "https://mcp.bitcoincreditstack.com/mcp"
}
}
} assistant mcp add com-bitcoincreditstack-mcp -t streamable-http -u 'https://mcp.bitcoincreditstack.com/mcp'
{
"mcpServers": {
"com-bitcoincreditstack-mcp": {
"type": "http",
"url": "https://mcp.bitcoincreditstack.com/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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 0
- “compare_venues” added an optional parameter “class” cosmetic
- “compare_venues” added an optional parameter “side” cosmetic
- “compare_venues” added an optional parameter “venues” cosmetic
- “compare_venues” dropped the optional parameter “collateral” cosmetic
- “compare_venues” dropped the optional parameter “denomination” cosmetic
5 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
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.bitcoincreditstack.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.bitcoincreditstack.com | CN=YE1,O=Let's Encrypt,C=US | 29 Aug 2026 | 27 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5e1e85bf6730c07bfa1a83691c9e24cd5e0 |
| SANs: api.bitcoincreditstack.com, mcp.bitcoincreditstack.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.bitcoincreditstack.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| bitcoincreditstack.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.bitcoincreditstack.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.bitcoincreditstack.com/mcp | HTTPS enforced | 301 | https://mcp.bitcoincreditstack.com/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 →
compare_venues Credit cost across venues ~175
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".
| Name | Type | Req | Description |
|---|---|---|---|
| class | string | – | Restrict to one credit class. The full matrix is ~160 rows; one class is far lighter. |
| ltv | number | – | Loan-to-value as a decimal 0–1, not a percentage. |
| side | string | – | 'borrow' (what a borrower pays, the default) or 'lend' (what a capital provider earns). |
| tenor_days | number | – | Loan term in days to compare at. |
| venues | string | – | Comma-separated registry ids to restrict the rows to, e.g. 'aave_v3_ethereum,cefi_ledn'. |
No output schema declared.
No examples provided.
get_credit_state The Bitcoin credit surface, now ~133
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_credit_state_history The Bitcoin credit surface over time ~141
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | How many days of history. Default 365, capped at 3650. |
No output schema declared.
No examples provided.
get_indicator Get an Indicator ~239
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | History start, ISO 8601 date. Only meaningful with include_history. |
| id | string | yes | Indicator id from list_indicators, e.g. 'tci', 'tsr', 'cdr'. |
| include_history | boolean | – | If true, return the historical series instead of the current value. Not every indicator has one. |
| to | string | – | History end, ISO 8601 date. Only meaningful with include_history. |
No output schema declared.
No examples provided.
get_lens Reading lenses ~243
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.
| Name | Type | Req | Description |
|---|---|---|---|
| lens | string | – | Which lens. Omit to list all of them. 'orientation' — Orientation — what this dataset is, and what it will not tell you; 'holder' — Holder — the cost of credit against bitcoin you already hold; 'trea… |
No output schema declared.
No examples provided.
get_market_composition What this credit market is made of ~149
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_market_flows Credit created and retired ~139
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_mvrv Bitcoin MVRV Ratio ~228
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 }.
| Name | Type | Req | Description |
|---|---|---|---|
| timestamp | string | – | ISO 8601 date. Currently ignored: the upstream serves the latest computed row only. Historical MVRV is available through get_indicator with include_history. |
No output schema declared.
No examples provided.
get_venue One venue against the published criteria ~186
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.
| Name | Type | Req | Description |
|---|---|---|---|
| venue_id | string | yes | Registry id, e.g. 'aave_v3_arbitrum'. Call list_venues to discover valid ids. |
No output schema declared.
No examples provided.
get_verification_bundle Verification bundle ~232
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.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | Network. Default 'arbitrum-one' (mainnet). Use 'arbitrum-sepolia' for the testnet deployment, which carries a far deeper book — but note the two run different contract builds, so a testnet observatio… |
No output schema declared.
No examples provided.
list_indicators Indicator Catalogue ~201
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.
| Name | Type | Req | Description |
|---|---|---|---|
| family | string | – | Restrict to one family. Omit to return the whole catalogue. |
| live_only | boolean | – | If true, omit indicators that are not currently live on this network. |
No output schema declared.
No examples provided.
list_onchain_indicators List On-chain Indicators ~69
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_venues Credit venues covered ~278
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain_id | integer | – | Restrict to venues on one EVM chain id. |
| complete_attributes_only | boolean | – | Only venues whose criteria cells are fully researched (8 of 8). Default false. |
| limit | integer | – | Cap the rows returned. Default 50. The response always states the unfiltered total. |
| status | string | – | Restrict by registry status: 'live', 'ingesting', 'registered', 'unresolved', 'defunct'. |
| venue_type | string | – | Restrict to one class, e.g. 'onchain_pooled', 'cefi_desk', 'corporate_debt', 'auction'. |
No output schema declared.
No examples provided.
What is the com.bitcoincreditstack/mcp server?
com.bitcoincreditstack/mcp is listed in the public MCP registry as com.bitcoincreditstack/mcp. The Bitcoin credit markets, measured. Cross-venue rates, venue criteria, chain indicators. This page covers its hosted endpoint (https://mcp.bitcoincreditstack.com/mcp).
Is the com.bitcoincreditstack/mcp server safe to use?
com.bitcoincreditstack/mcp scores 76 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 com.bitcoincreditstack/mcp server expose?
com.bitcoincreditstack/mcp exposes 13 tools: list_onchain_indicators, get_mvrv, list_indicators, get_indicator, get_verification_bundle, and 8 more. Their descriptions and schemas cost roughly 2,413 tokens of context every time the server is loaded.
Does the com.bitcoincreditstack/mcp server require authentication?
No. We connected to com.bitcoincreditstack/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.bitcoincreditstack/mcp server still maintained?
com.bitcoincreditstack/mcp 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.