Hosted MCP server/Other

Ironclaw BTC Node MCP server

Hosted at mcp.btcnode.uk·SSE

Ironclaw BTC Node provides real-time Bitcoin blockchain data and analytical tools for AI agents through 17 MCP tools. Three tools are free and 14 cost $0.001 each, paid in USDC on Base mainnet via x402; no API keys or subscriptions are needed. The provider declares an SSE endpoint at https://mcp.btcnode.uk/sse, so clients must use SSE rather than Streamable HTTP.

mcp.btcnode.uk SSE x402 pay-per-call (no API keys) Server not checked yet Reviewed 2026-11-16
About

Where it fits

Bitcoin analysts and agent developers who need full-node data without an API key.

  • Retrieve real-time Bitcoin blockchain data for analysis.
  • Run analytical tools on Bitcoin data.
  • Pay $0.001 per paid call in USDC on Base via x402.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses SSE.

All client guides
  1. 01

    Run this command in your terminal

    This adds Ironclaw BTC Node as a remote SSE server in Claude Code.

    Claude Code
    claude mcp add --transport sse ironclaw-btc-node https://mcp.btcnode.uk/sse --scope project
  2. 02

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://mcp.btcnode.uk/sse
Host
mcp.btcnode.uk · /sse
Transport
SSE
Authentication
x402 pay-per-call (no API keys)
Server name
ironclaw-btc-node
Listing type
Community or directory listing

The installer uses the server name ironclaw-btc-node. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that ironclaw-btc-node appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Retrieve real-time Bitcoin blockchain data for analysis. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • Your client only supports Streamable HTTP. Use a client that supports SSE or the provider's HTTP endpoint.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider source

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Ironclaw BTC Node repositoryhttps://github.com/cariohca-ux/x402-btc-node