₿itcoin & Lightning Network MCP Server

Created By
AbdelStarka year ago
Bitcoin & Lightning Network MCP Server.
Overview

What is ₿itcoin MCP Server?

₿itcoin MCP Server is a Model Context Protocol (MCP) server that allows AI models to interact with the Bitcoin blockchain, enabling functionalities such as key generation, address validation, transaction decoding, and blockchain queries.

How to use ₿itcoin MCP Server?

To use the ₿itcoin MCP Server, integrate it with AI applications like Claude Desktop or Goose by configuring the respective settings to connect to the server. Follow the provided documentation for detailed integration steps.

Key features of ₿itcoin MCP Server?

  • Key Generation: Create Bitcoin key pairs including addresses and private keys.
  • Address Validation: Check the validity of Bitcoin addresses.
  • Transaction Decoding: Decode raw Bitcoin transactions into readable formats.
  • Blockchain Queries: Retrieve information about the latest blocks and transaction details.

Use cases of ₿itcoin MCP Server?

  1. Enabling AI agents to fetch real-time Bitcoin data.
  2. Assisting developers in building applications that require Bitcoin blockchain interactions.
  3. Providing educational tools for understanding Bitcoin transactions and blockchain technology.

FAQ from ₿itcoin MCP Server?

  • Can the server handle all Bitcoin operations?

Yes, it supports various operations including key generation, address validation, and transaction decoding.

  • Is there a demo available?

Yes, demo videos for both Claude and Goose integrations are provided in the documentation.

  • How can I contribute to the project?

Contributions are welcome! You can submit pull requests or open issues on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
AbdelStark
Star
45
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago