Home / MCP registry index / io.thegavel/gavel
io.thegavel/gavel
io.thegavel/gavel in the official MCP registry.
Endpoint https://mcp.thegavel.io/mcp. Source: github.com/JamieFrame/gavel-mcp.
The registry describes it as: Oracle-free fixed-rate, fixed-term BTC credit on Arbitrum One. Data and unsigned blueprints.
We read its 21 tools on 2026-10-21. 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
get_yield_curve get_protocol_reference check_wallet_status find_auctions_matching_criteria list_fiat_onramps list_wallet_options get_user_positions get_loan_status list_gavel_indicators get_gavel_indicator prepare_bid_calldata prepare_create_auction_calldata prepare_repay_loan_calldata prepare_claim_collateral_calldata prepare_claim_refund_calldata list_comparables get_address_history get_book get_verification_bundle list_onchain_indicators get_mvrv
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-thegavel-gavel)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.