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.
Skills that pair with Ironclaw BTC Node
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Hand the current conversation to a new background agent that picks up the work right away.
Turns a decision the user cannot fully answer into a questionnaire for someone else to fill in.
Covers writing documents for agents. Use it when creating or editing skills, or when modifying AGENTS.md or CLAUDE.md.
No skills found
Try a different search term or clear the filters.
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.
- 01
Run this command in your terminal
This adds Ironclaw BTC Node as a remote SSE server in Claude Code.
Claude Codeclaude mcp add --transport sse ironclaw-btc-node https://mcp.btcnode.uk/sse --scope project - 02
Verify the connection
Run claude mcp list, or open /mcp in a Claude Code session.
Learn more about MCP in Claude Code
- 01
Install with one click
This opens Cursor with the server pre-filled. Review the connection before accepting it.
Install in Cursor - 02
Verify the connection
Open Cursor's MCP settings and enable the server if it is not active.
Learn more about MCP in Cursor
- 01
Install with one click
This opens VS Code with the server pre-filled. Review the connection before accepting it.
Install in VS Code - 02
Verify the connection
Run MCP: List Servers from the Command Palette and start the server.
Learn more about MCP in VS Code
- 01
Open Claude settings
Open Settings, choose Connectors, add a custom connector, and paste the hosted endpoint. Complete the provider sign-in when prompted.
Open Claude settings - 02
Verify the connection
Return to a chat, open the connector menu, and confirm the server tools appear.
Learn more about MCP in Claude
More clients, including project and global config files, are in the sidebar.
Endpoint and configuration
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.
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.
- 1Open the tool list.
Restart the client or start a new session. Confirm that
ironclaw-btc-nodeappears and that the tools match the provider documentation. - 2Run one small request.
Start with: Retrieve real-time Bitcoin blockchain data for analysis. Check the result before you give the server more access.
- 3Check permissions.
Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.
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.
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.
Before you connect
- 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.
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.
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