LabscoMCP early access ↗
b-open-ioMCP SERVER

Bitcoin SV MCP Server

A Bitcoin SV wallet, blockchain explorer, ordinals marketplace and on-chain social feed, all behind one server.

by b-open-io ↗Wallets, Signing & Transaction ExecutionCommunity

LABSCO SUMMARY

An agent can hold a BSV wallet, read the chain, and trade ordinals.

The spread is what makes it usable in one conversation: look up a price, decode a transaction, check a token's market, and then actually send, buy or inscribe — with the key handling kept behind a passphrase rather than pasted into a config.

What it is

A toolkit for Bitcoin SV work from an AI client, grouped by what you are doing: wallet operations, chain lookups, ordinals and token markets, on-chain social posts, BAP identities and MNEE tokens. It also carries educational prompts about the BSV SDK, so the model can look up how the protocol works before it acts.

What you get

  • Wallet — wallet_getAddress, wallet_getPublicKey, wallet_createSignature, wallet_verifySignature, wallet_encryption for encrypt and decrypt, wallet_sendToAddress in BSV or USD amounts, wallet_purchaseListing, wallet_createOrdinals
  • Chain — bsv_getPrice, bsv_decodeTransaction for a full input and output breakdown, bsv_explore across the WhatsOnChain endpoints
  • Ordinals — ordinals_getInscription, ordinals_searchInscriptions, ordinals_marketListings, ordinals_marketSales, ordinals_getTokenByIdOrTicker
  • Social — bsocial_createPost writes a post using the B:// and MAP protocols, bsocial_readPosts reads them back with filters
  • Identity — bap_getId, bap_getCurrentAddress, bap_generate
  • MNEE tokens — mnee_getBalance, mnee_sendMnee, mnee_parseTx
  • Utilities — utils_convertData between utf8, hex, base64 and binary
  • Prompts the model can pull in: bitcoin_sv_ordinals, bitcoin_sv_sdk_overview, bitcoin_sv_sdk_wallet, bitcoin_sv_sdk_transaction, bitcoin_sv_sdk_auth, bitcoin_sv_sdk_cryptography

Requirements

PRIVATE_KEY_WIF is optional — without it the server runs in a limited mode with the educational resources and the non-wallet tools, and wallet plus MNEE operations need a key. IDENTITY_KEY_WIF turns on sigma-protocol signing of ordinals inscriptions; BSV_MCP_PASSPHRASE enables encrypted key storage, which the README recommends over passing a raw key. Run it with bunx bsv-mcp@latest (Bun is the project's runtime, npx works too), or install the Claude Code plugin with claude plugin install bsv-mcp@b-open-io. There is also a hosted endpoint at https://bsv-mcp.rohenaz.workers.dev/mcp with OAuth sign-in through auth.sigmaidentity.com, where you hold no coins of your own. The project describes itself as early and experimental, with an unstable API.

Setup effort

One command — claude plugin install bsv-mcp@b-open-io

See installation options