Gavel MCP

What JamieFrame/gavel-mcp MCP server does

JamieFrame/gavel-mcp MCP server gives MCP-compatible agents an interface to Gavel credit data, Bitcoin on-chain indicators, and selected lending-market operations. The service is a TypeScript wrapper around the Gavel API rather than a separate data store or analytics engine. Responses are shaped as JSON text for consumption by language-model clients.

The data surface includes auction discovery, user positions, loan status, yield-curve data, MVRV, protocol references, and catalogues of Gavel and on-chain indicators. The server also exposes wallet readiness information such as balances, allowances, and blockers through its wallet-status tool.

How it works

An MCP client connects to the service over HTTP, and the service forwards data requests to the authoritative Gavel REST API at api.thegavel.io or another configured base URL. It does not query PostgreSQL directly or reproduce the API’s business logic. Chain-dependent reads and transaction encoding use configured Arbitrum RPC endpoints; viem is used for function-data encoding.

The transaction tools return unsigned call blueprints. They cover bidding, auction creation, loan repayment, collateral claims, and refund claims, including approval calls when the relevant allowance is insufficient. The user remains responsible for reviewing and signing those calls. No wallet client, account, private key, or signing surface is present.

Setup and configuration

Local development requires Node 20 or newer. Install dependencies with npm install, copy .env.example to .env, set the applicable values, and run npm run dev. The project also provides npm run typecheck and npm run build commands. A development client can connect to http://localhost:3002/mcp.

The HTTP port defaults to 3002. GAVEL_API_BASE_URL selects the upstream REST service and defaults to http://localhost:3001. Other settings control logging, CORS, health-check protection, anonymous and paid rate limits, and the Arbitrum mainnet and Sepolia RPC URLs. Internal tier resolution uses GAVEL_API_INTERNAL_URL and, when configured, INTERNAL_API_SECRET. Tier enforcement is disabled by default.

Tools and capabilities

The available tools are grouped into three operational areas:

• Read state: check wallet status, find auctions matching supplied criteria, retrieve user positions, and inspect loan status.
• Transaction preparation: encode bid, auction-creation, repayment, collateral-claim, and refund-claim calls without signing them.
• Catalogues and data: list wallet options, recommend a fiat onramp, list or retrieve indicators, get the yield curve and MVRV, and retrieve protocol references.

Filtering can use user-provided criteria, but the server does not rank, score, or select opportunities for the user. Catalogue tools are static catalogues and do not perform ranking.

Limitations and notes

JamieFrame/gavel-mcp MCP server does not sign transactions or hold account credentials. Any agent workflow using the calldata tools needs a separate wallet or signing step controlled by the user. The service is therefore suited to preparation and information retrieval, not autonomous transaction execution.

Rate limits apply independently of tier enforcement. The documented tier ladder is free, pro, and enterprise; enforcement is authored but currently defaults to off. Internal tier lookup fails open to free if it encounters an error. The server does not provide bulk delivery, and it should not be treated as an investment-advice or ranking system.

For deployment, the documented target uses a systemd service and serves the compiled dist/ directory. Changes must be built before restarting the service. A reverse proxy and TLS can expose the MCP endpoint publicly, while the internal tier-resolution URL must remain a loopback address.