Agents

Bitcoin Layers exposes a hosted MCP server for LLM agents that need current and historical BTC supply, token, network, price, and top-gainer datasets.

MCP Server

Use this Streamable HTTP MCP endpoint:

https://mcp.bitcoinlayers.org/

Every tool call must include a Bitcoin Layers API key:

Authorization: Bearer YOUR_API_KEY

For clients that support custom headers but not bearer auth, x-api-key: YOUR_API_KEY is also accepted.

Agent Instructions

Connect to https://mcp.bitcoinlayers.org/ as a remote MCP server. Send the user's Bitcoin Layers API key as Authorization: Bearer <API_KEY>. Use the MCP tools for read-only Bitcoin Layers data. API keys are limited to 60 requests per rolling 60-second window; if a tool call is rate limited, wait at least 60 seconds before retrying and avoid parallel polling.

Connection Config

Exact setup varies by MCP client. Use this configuration shape when a client asks for a remote MCP server URL and headers:

{
  "url": "https://mcp.bitcoinlayers.org/",
  "headers": {
    "Authorization": "Bearer YOUR_API_KEY"
  }
}

If the client separates bearer tokens from headers, enter only the API key in that credential field and keep the server URL as https://mcp.bitcoinlayers.org/.

Request Examples

View available tools

curl https://mcp.bitcoinlayers.org/ \
  -H "content-type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Run a data query

curl https://mcp.bitcoinlayers.org/ \
  -H "content-type: application/json" \
  -H "authorization: Bearer YOUR_API_KEY" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"list_current_supplies_by_network","arguments":{"limit":5,"order":"rank.asc"}}}'

Available Tools

The MCP server mirrors the curated public API surface documented in the API reference, plus cached Bitcoin Network data endpoints. It does not expose internal helper endpoints or raw PostgREST CRUD.

list_current_prices list_historical_prices list_current_supplies_by_network list_current_supplies_by_token_implementation list_current_supplies_by_token_project list_historical_supplies_by_network list_historical_supplies_by_token_implementation list_historical_supplies_by_token_project list_historical_supplies_by_staking list_historical_supplies_by_liquid_staking list_top_gainers_by_percentage list_top_gainers_by_absolute_growth get_bitcoin_network_hashrate get_bitcoin_difficulty_adjustments get_bitcoin_prices get_bitcoin_dominance

Querying

Tool arguments use PostgREST filter syntax for field filters. Common examples:

network_slug: "eq.Ethereum"
token_slug: "eq.BitGo-wBTC"
date: "gte.2026-04-01"
period: "eq.daily"
order: "rank.asc" or order: "date.desc"
limit: 25

Rate Limits

API keys are currently limited to 60 requests per rolling 60-second window. Rate-limited upstream calls return a JSON-RPC tool error. The underlying API uses 429, retry-after, x-ratelimit-limit, and x-ratelimit-remaining.

Bitcoin Network tools follow the same Bitcoin Layers API-key rate limit. Responses are cached for up to 10 minutes, so freshness may vary by upstream provider.