Mainnet · Arbitrum One

Connect an assistant

Everything on this site is reachable by an assistant or a script, with the same provenance fields the pages render. There is no chat here — you bring your own agent.

MCP server

https://mcp.thegavel.io/mcp

Transport: streamable-http
Protocol version: 2025-06-18
Server: aletheia-mcp 0.3.0
Authentication: none — anonymous tier, no key
Tools: 21

Verified 2026-08-27 — JSON-RPC initialize + tools/list against the endpoint; an unauthenticated tools/call was served.

One server, two networks — but not for every tool

11 of the 21 tools accept a `network` parameter (`arbitrum-one` / `arbitrum-sepolia`, default `arbitrum-one`). The other 10 — including `get_yield_curve` and the whole indicator family — do not, and return mainnet. For testnet figures, read the testnet REST endpoint directly.

Mainnet REST — https://api.thegavel.io/v1

Testnet REST — https://api-testnet.thegavel.io/v1

Client configuration

Any client that speaks the Model Context Protocol over streamable HTTP can use the endpoint above; that is a property of the protocol, and of our server, both of which are verified.

Per-client instructions are not published here yet. Remote-MCP onboarding has changed repeatedly in every major client, and a settings snippet is the kind of thing that rots silently — nobody files a bug against an out-of-date configuration block. Rather than reproduce steps we have not checked against each vendor’s current documentation, this page states the endpoint and lets your client’s own instructions do the rest.

Clients known to support remote MCP servers: Claude, ChatGPT, Cursor. Consult each one’s current documentation for where to add the URL.

Agent templates and skills

The agent templates and the skills repository are specified in the TA runbook set and are not yet built. When they exist, each template renders here as a card with its "does not do" section visible — the part that says what the template will not attempt is the part worth reading first.

Planned index: gavel://templates/index.json

What this server does, and does not, do

Every tool returns observed data or an unsigned transaction blueprint.
Nothing on the server signs, submits or broadcasts a transaction. No tool takes custody of funds or receives a mandate.
A blueprint is calldata your own wallet may choose to sign. Reading it is not agreeing to it.
Tools that return catalogues do not rank their entries. Tools that return distributions report what was observed with the sample size, and do not forecast a fill, a rate, a time-to-fill or a return.
Read the provenance block before treating any rate as a market reference. On Mainnet today it states plainly that this is not yet an independent market assessment.
Nothing here is advice.