btcmatic-mcp-server
OfficialClick on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@btcmatic-mcp-servercheck the self-custody radar for any open incidents"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
btcmatic-mcp-server
MCP server for the BTCMatic agent API: pay-per-call
Bitcoin context for autonomous agents — the self-custody security radar, fee percentile,
price change windows and condition frequency — paid in sats over Lightning. No account, no
API key, no credit card: the API answers 402 with an invoice, the agent's wallet pays, the tool
call completes with the preimage.
BTCMatic is the Bitcoin event engine; this package is the agent's way in. Everything here is read-only context — it cannot create rules, place orders, notify anyone or touch funds.
Tools
Tool | Paid | What it does |
| no | Prices, prepaid bounds and the payment flow — call first |
| yes | Open/corroborated self-custody incidents, per-product chatter counts with distinct-source counts, per-source precision ledger |
| yes | Latest price with 1h/24h/7d change, next-block fee + its 90-day percentile, mempool size; stale values withheld, gaps reported |
| yes | How often |
| no | Mint a prepaid top-up invoice |
| no | Prove the top-up with its preimage → bearer token (shown once) |
| no | Prepaid balance and calls remaining |
One paid call costs about 21 sats (the live price is in btcmatic_discover).
Related MCP server: x402-api
How payment works
Call a paid tool with no proof. The result is the 402 offer as data, not an error:
{ kind: "offer", price_sats, bolt11, payment_hash, next_step }.Your wallet pays the
bolt11and shows the preimage.Call the same tool again with
{ payment_hash, preimage }. The proof is single use.
Prepaid: btcmatic_topup → pay → btcmatic_topup_claim → token. Start the server with
BTCMATIC_AGENT_TOKEN=agt_… and every paid tool debits the balance; at zero the tools answer
{ kind: "topup_needed" }.
This server never holds keys and never pays. It moves proofs; paying is always the decision of a
wallet you control. The proof format is Authorization: L402 <payment_hash>:<preimage> — the
payment hash names an invoice BTCMatic minted and sha256(preimage) = payment_hash is the proof, so
no macaroon is needed.
Install
{
"mcpServers": {
"btcmatic": {
"command": "npx",
"args": ["-y", "btcmatic-mcp-server"],
"env": { "BTCMATIC_AGENT_TOKEN": "agt_…" }
}
}
}BTCMATIC_AGENT_TOKEN is optional (per-call 402 flow without it). BTCMATIC_API_URL overrides the
API base (default https://api.btcmatic.com).
What the numbers are — and are not
Per-source precision comes from labels BTCMatic sets by hand and publishes on btcmatic.com/radar; an unlabeled source shows no precision at all.
Fee percentile, change windows and frequency are descriptive statistics over public series. They describe the past; they do not predict anything and nothing here is a recommendation to buy or sell.
Every paid response carries a
metablock with the price paid, the remaining balance, a disclaimer and a signup link — the same data is free with a BTCMatic account; this API exists for clients that cannot have one.
Development
pnpm install
pnpm build && pnpm test && pnpm lint
BTCMATIC_API_URL=http://localhost:3000 node dist/cli.js # stdio transportResources
Agent API docs: https://btcmatic.com/integrations/agents
OpenAPI (tag
agent): https://api.btcmatic.com/docsBTCMatic for automations (API keys, n8n): https://btcmatic.com/integrations/n8n
License
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityBmaintenanceMCP server that enables AI agents to make autonomous Bitcoin Lightning Network payments using the L402 protocol. Agents can pay for API access, purchase resources, and complete transactions without human intervention — invoice comes in, sats go out, done.179MIT
- AlicenseAqualityDmaintenanceMCP server for pay-per-call DeFi and crypto data via x402 micropayments on Base. 8 endpoints: token prices, TVL, funding rates, token security, gas tracker, whale monitoring, wallet profiling, and yield scanning.846MIT
- AlicenseNot gradedqualityDmaintenanceMinimal MCP server demonstrating L402 pay-per-call with Depth-of-Identity reputation gating, providing a bitcoin data tool that fetches BTC price and mempool fees.MIT
- AlicenseBqualityCmaintenanceMCP server offering 26 Lightning-paid tools for Bitcoin mempool intelligence and sovereign on-prem AI inference, with no third-party APIs and pay-per-call in sats.26181MIT
Related MCP Connectors
Monetize any MCP server: x402 paywall, pay-per-call billing in USDC on Base, agent marketplace.
MCP marketplace: agents pay per call in USDC via x402. Plus Base chain data and a USDC<->bank ramp.
MCP server connecting AI agents to non-custodial staking data across 130+ networks.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/btcmatic-com/btcmatic-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server