Home / MCP registry index / com.bitcoincreditstack/mcp
com.bitcoincreditstack/mcp
com.bitcoincreditstack/mcp in the official MCP registry.
Endpoint https://mcp.bitcoincreditstack.com/mcp. Source: github.com/JamieFrame/gavel-mcp.
The registry describes it as: The Bitcoin credit markets, measured. Cross-venue rates, venue criteria, chain indicators.
We read its 28 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
list_onchain_indicators get_mvrv list_chain_series get_chain_series get_cost_basis list_series get_series get_chart get_corporate_instruments get_fund_holdings get_balance_sheet get_events get_event_post_kit get_desk_rates get_debt_by_collateral list_indicators get_indicator get_verification_bundle list_venues get_venue compare_venues get_lens get_guide get_credit_state get_credit_state_history get_market_composition get_market_flows get_liquidation_map
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-bitcoincreditstack-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.