MCP server · Bitcoin × AI agents · x402 · Nov 2025
Engrave Protocol — MCP server giving AI agents access to Bitcoin via x402.
Dev on Engrave — the first MCP server that exposes Bitcoin as callable tools for AI agents, with x402 payment endpoints on top. Bridge infrastructure for the agent economy: Bitcoin-native utility an agent can actually use, with $Engrave launched on Solana via pump.fun (Nov 2025 — broke $1M+ at launch, peaked at $1.4M).
The building blocks
MCP Server
First Bitcoin × AI-agent bridge
x402
HTTP 402 payment rail
$1.4M
Peak market cap · $ENGRAVE on Solana
Nov 2025
Shipped
The problem
The agent economy is real but the rails aren't. MCP gave AI agents a protocol for calling tools; x402 — the HTTP 402 "Payment Required" status that sat dormant for twenty-five years — is the protocol being reinvented as the payments layer for that economy. Bitcoin is the asset an autonomous agent actually wants to settle in.
None of it connected. MCP servers exposing trivial tools, x402 drafts in isolation, Bitcoin operations locked behind wallet-specific flows that assume a human in the loop. The bridge didn't exist: an MCP server where an AI agent can read Bitcoin, construct a PSBT, pay through an x402 endpoint, and have it settle on mainnet — without a wallet pop-up or a custodial shortcut.
Engrave built that bridge. The dev brief: ship the first MCP server that treats Bitcoin as a first-class surface for autonomous agents, with x402 as the payment primitive, and a token economy on Solana (fastest liquidity venue) while utility settles on Bitcoin (hardest money).
What I did
Four layers of an agent × Bitcoin bridge.
MCP server — Bitcoin as callable tools
Built an MCP server that exposes Bitcoin operations as tools any Anthropic-compatible agent can discover and call — balance reads, UTXO selection, PSBT construction, broadcast, confirmation tracking. Tool surfaces are designed for autonomous use: deterministic, idempotent where possible, with clear error semantics agents can reason over.
x402 payment endpoint — monetise tool access agent-safely
Wrapped the MCP tools behind HTTP 402 payment requirements. An agent hits an endpoint, receives the payment demand, settles on Bitcoin (or a bridged equivalent), and retries with proof of payment. Machine-to-machine payments without accounts, keys passed around, or trust-me APIs in the middle.
PSBT-first signing inside the tool surface
Every Bitcoin operation an agent triggers is a PSBT by default — server constructs, agent (or its delegated signer) signs, server broadcasts. No custody, no seed exposure, no wallet pop-up trap that doesn't work headlessly. The same Bitcoin pattern the ecosystem has earned over years, adapted to an agent caller.
Cross-chain token economy — $ENGRAVE on Solana, utility on Bitcoin
The token launched on Solana via pump.fun — fastest path to liquidity and a healthy holder base. The utility the token governs — MCP access tiers, x402 payment flows, agent-facing tool economics — settles on Bitcoin. Solana for distribution, Bitcoin for the asset at the end of the rail.
What transferred
Patterns that carry through every drop since.
- MCP is the right API surface for agent × infrastructure. Any chain you want agents to touch needs an MCP server with tool semantics that agents can actually reason over — not a REST wrapper wearing a new hat.
- x402 + Bitcoin is the correct pairing. HTTP 402 was built for payments that sit between machines; Bitcoin is the asset you want at the end of that handshake.
- Cross-chain is a product decision, not a tech one. Solana for liquidity + Bitcoin for utility is legitimate, not a compromise — each chain earning its seat.
- The agent economy is infra-first. The teams that matter will be the ones shipping rails, not the ones shipping "autonomous influencers."
Stack
- MCP (Model Context Protocol) server
- x402 HTTP 402 payment endpoint
- Bitcoin: PSBT construction + node infrastructure
- Solana: $ENGRAVE token via pump.fun
- TypeScript · Node · RPC plumbing
Free download · 6 pages · PDF
What I learned shipping 1,500 Ordinals on Bitcoin.
Pre-launch, launch-day, and the 90 days after — with the mistakes that cost real BTC. Ordinals, Runes, and beyond.
No spam. You also get the Sunday note — unsubscribe in one click.
Keep reading