# com.bitcoincreditstack/mcp (remote · mcp.bitcoincreditstack.com)

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

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.bitcoincreditstack.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-bitcoincreditstack-mcp/mcp.md), [page](https://verifymcp.io/servers/com-bitcoincreditstack-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.bitcoincreditstack.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-bitcoincreditstack-mcp 'https://mcp.bitcoincreditstack.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-bitcoincreditstack-mcp": {
      "url": "https://mcp.bitcoincreditstack.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-bitcoincreditstack-mcp": {
      "type": "http",
      "url": "https://mcp.bitcoincreditstack.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-bitcoincreditstack-mcp]
url = "https://mcp.bitcoincreditstack.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-bitcoincreditstack-mcp": {
      "type": "remote",
      "url": "https://mcp.bitcoincreditstack.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-bitcoincreditstack-mcp --url 'https://mcp.bitcoincreditstack.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-bitcoincreditstack-mcp:
    url: "https://mcp.bitcoincreditstack.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-bitcoincreditstack-mcp": {
      "Transport": "http",
      "Url": "https://mcp.bitcoincreditstack.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-bitcoincreditstack-mcp -t streamable-http -u 'https://mcp.bitcoincreditstack.com/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 76, +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.

### 2026-09-18 (score 75, +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.

### 2026-09-16 (score 74, 0)

- [cosmetic] “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”

### 2026-09-15 (score 74, +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.

### 2026-09-13 (score 73, +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.

### 2026-09-11 (score 72, +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.

### 2026-09-09 (score 71, +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.

### 2026-09-07 (score 70, +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.

## MCP tools (13)

### `list_onchain_indicators` (~69 tokens)

List On-chain 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.

### `get_mvrv` (~228 tokens)

Bitcoin MVRV Ratio

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 }.

Input parameters:

- `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.

### `list_indicators` (~201 tokens)

Indicator Catalogue

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.

Input parameters:

- `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.

### `get_indicator` (~239 tokens)

Get an 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.

Input parameters:

- `from` (string): History start, ISO 8601 date. Only meaningful with include_history.
- `id` (string, required): 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.

### `get_verification_bundle` (~232 tokens)

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.

Input parameters:

- `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…

### `list_venues` (~278 tokens)

Credit venues covered

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.

Input parameters:

- `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'.

### `get_venue` (~186 tokens)

One venue against the published criteria

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.

Input parameters:

- `venue_id` (string, required): Registry id, e.g. 'aave_v3_arbitrum'. Call list_venues to discover valid ids.

### `compare_venues` (~175 tokens)

Credit cost across 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".

Input parameters:

- `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'.

### `get_lens` (~243 tokens)

Reading lenses

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.

Input parameters:

- `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…

### `get_credit_state` (~133 tokens)

The Bitcoin credit surface, now

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` (~141 tokens)

The Bitcoin credit surface over time

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.

Input parameters:

- `days` (integer): How many days of history. Default 365, capped at 3650.

### `get_market_composition` (~149 tokens)

What this credit market is made of

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` (~139 tokens)

Credit created and retired

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-bitcoincreditstack-mcp/mcp#diagnostics

## Score history

- 2026-09-20: 76
- 2026-09-19: 75
- 2026-09-18: 75
- 2026-09-17: 74
- 2026-09-16: 74
- 2026-09-15: 74
- 2026-09-14: 73
- 2026-09-13: 73
- 2026-09-12: 72
- 2026-09-11: 72
- 2026-09-10: 71
- 2026-09-09: 71
- 2026-09-08: 70
- 2026-09-07: 70
- 2026-09-06: 69
- 2026-09-05: 69
- 2026-09-04: 68
- 2026-09-03: 68
- 2026-09-02: 67
- 2026-09-01: 67
- 2026-08-31: 67
- 2026-08-30: 63
- 2026-08-29: 63

## Common questions

### 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.

## Links

- Remote endpoint: https://mcp.bitcoincreditstack.com/mcp
- Repository: https://github.com/JamieFrame/gavel-mcp
- Website: https://bitcoincreditstack.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-bitcoincreditstack-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-bitcoincreditstack-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-bitcoincreditstack-mcp/mcp