Summary

Hosted endpoints first; self-hosting is the fallback, not the default.

The two published URLs mean the fastest path is an API key and a config entry — no Bun, no build. Self-hosting exists and is a three-command setup, but it mostly matters if you want the traffic inside your own network. Testnet4 is a separate URL rather than a flag, which makes it hard to point a test run at mainnet by accident.

What it is

A Streamable HTTP MCP server generated from Maestro's Bitcoin API. It exposes blocks, transactions and addresses to an assistant, and Maestro runs hosted endpoints for both mainnet and testnet4 so you do not have to deploy anything.

What you get

Blockchain Indexer access for exploring blocks, transactions and addresses
Mempool Monitoring for what has not been confirmed yet
Market Price data alongside the chain data
Wallet and Node RPC surfaces from the same server
Two networks, selected by endpoint: mainnet at https://xbt-mainnet.gomaestro-api.org/v0/mcp and testnet4 at https://xbt-testnet.gomaestro-api.org/v0/mcp
Streamable HTTP transport, so clients connect by URL

Requirements

A Maestro API key from docs.gomaestro.org, used to authenticate against the hosted endpoint. To run your own instance you need Bun 1.0 or higher: `bun install`, `bun run build`, then `bun run start:http`, with the key and API_BASE_URL set in .env. A self-hosted server listens on the port in .env, defaulting to 3000, and serves MCP at /mcp.