ORDnet MCP Server v3.3

Enable AI agents to create Web3 content on Bitcoin SV blockchain

Overview

ORDnet MCP Server enables AI agents (Claude, GPT, etc.) to create permanent, censorship-resistant content on the Bitcoin SV blockchain using the 1SatOrdinals protocol. This is a key component of the freedom of speech infrastructure - allowing AI to autonomously publish Web3 content.

Key Features

• 45 MCP Tools for complete blockchain content creation, payments and transfers

• BRC-100 aligned identity (v3.0): ordnet_identity, ordnet_sign_message, ordnet_verify_message, ordnet_derive_payment_address — agent identity, off-chain signing, and per-invoice payment-address derivation as the foundation for x402

• Agent payments: ordnet_send (P2PKH + optional OP_RETURN reference, miner fee only — x402-ready), ordnet_transfer for ordinals/domains (1SatOrdinals input-0/output-0 semantics, outpoint verified via own node)

• Binary inscriptions via ordnet_inscribe_binary (base64 → bytes untouched); BSVmap tile claims via ordnet_bsvmap_inscribe

• Agent conveniences: ordnet_tx_status (confirmations via own node), ordnet_price (via own CoinGecko proxy)

• 3 MCP Prompts (prompts/list): inscribe-website, register-domain, agent-payment

• 1SatOrdinals inscriptions (HTML, JSON, text, images, etc.)

• SNS/OPNS domain registration (.sats, .btc, .bsv, etc.)

• 3-tier wallet security (env vars → encrypted → plaintext; plaintext-WIF tools are disabled on the HTTP transport)

• Agent safety layer: tx simulation via ORDnet's own node + spend limits with operator-set hard ceilings (fail-closed)

• HTTP transport with mandatory bearer auth (ORDNET_MCP_AUTH_TOKEN, server refuses to start without it)

• Agent-tier service fee: 396 satoshis across 11 outputs to 10 addresses, plus a miner fee of 0.15 sat/byte (min. 200 sats). That is deliberately one tenth of the 3.996-satoshi fee the ORDnet wallets charge — an agent inscribes far more often than a person does, so the per-transaction fee is scaled down to match. The same agent tier applies to ORDmail. See Service fees for the exact split.

Related MCP server: aibtc-mcp-server

Quick Start

Installation

git clone https://github.com/ORDNET/ORDnet-MCP-Server.git && cd ORDnet-MCP-Server
npm install && npm run build

Note: the package is not (yet) published on npm; install from source.

Usage with Claude Desktop

Add to your Claude Desktop config (~/.config/claude/claude_desktop_config.json):

{
  "mcpServers": {
    "ordnet": {
      "command": "node",
      "args": ["/absolute/path/to/ORDnet-MCP-Server/dist/index.js"],
      "env": {
        "ORDNET_WIF": "your-wif-private-key"
      }
    }
  }
}

Usage with OpenClaw

{
  "mcp_servers": [
    {
      "name": "ordnet",
      "command": "node",
      "args": ["/path/to/ordnet-mcp-server/dist/index.js"],
      "env": {
        "ORDNET_WIF": "your-wif-private-key"
      }
    }
  ]
}

Service Fees

Every inscription includes a total service fee of 396 satoshis, split across 11 outputs to 10 addresses (monitor and founder share one), exactly as defined in src/constants.ts (SERVICE_FEE_OUTPUTS). These are the values the code actually writes:

Miner fee is separate: 0.15 sat/byte, minimum 200 sats.

Why 396 and not 3.996

The ORDnet wallets (Chrome extension, iOS, Android) charge 3.996 satoshis over the same 11-output structure — every amount is exactly ten times the one above. That is not a discrepancy between products: agents and mail run on a deliberately reduced agent tier, because an autonomous agent inscribes far more often than a person opening a wallet. The split across recipients is identical; only the scale differs.

Note: ordnet_send (plain payments / x402 micropayments) carries no service fee — only the miner fee — so agent-to-agent payments stay lean. The x402 facilitator has no service-fee outputs at all.

Tools Reference

Wallet Management (6 tools)

Inscriptions (6 tools)

Domains (6 tools)

Search & Lookup (4 tools)

Security (4 tools)

Payments (5 tools)

Identity & signing (3 tools)

Utilities (11 tools)

Total: 45 tools.

† Disabled on the remote HTTP transport: these two tools would move a plaintext private key (WIF) over the network. Locally (stdio) they work; remotely the server refuses them with an explanatory error. Use ordnet_wallet_init_env on servers.

Example: Create an HTML Inscription

User: Create a simple webpage saying "Hello from AI" and inscribe it on Bitcoin

AI: I'll create and inscribe this HTML content on the BSV blockchain.

1. First, let me initialize the wallet...
   [ordnet_wallet_init_env]
   ✓ Wallet initialized at 1ABC...

2. Creating the HTML inscription...
   [ordnet_inscribe_html] content="<html><body><h1>Hello from AI</h1></body></html>"
   
   ✓ Inscription successful!
   - TXID: abc123...
   - Inscription ID: abc123..._0
   - View: https://ordnet.io/view/abc123..._0

Supported Content Types

• text/html;charset=utf8 - HTML web pages

• text/plain;charset=utf8 - Plain text

• application/json - JSON data

• image/svg+xml - SVG graphics

• image/png - PNG images

• image/jpeg - JPEG images

• image/gif - GIF animations

• image/webp - WebP images

• audio/mpeg - MP3 audio

• video/mp4 - MP4 video

• application/pdf - PDF documents

Supported Domain Extensions

Universal

• .sats

Chain-specific

• BTC: .btc .ord .xbt .gm .unisat .x

• BSV: .bsv

• DOGE: .doge .shibe

• LTC: .ltc

• BCH: .bch

• BELLS: .bells

• And more...

Security Tiers

Recommendation: Always use environment variables in production.

Development

# Clone and install
git clone https://github.com/ORDNET/ORDnet-MCP-Server.git
cd mcp-server
npm install

# Build
npm run build

# Run the audit regression tests (SSRF guard + spend policy).
# These run straight from source with Node's type stripping:
node --experimental-strip-types test/audit-2026-08-11.test.mjs

# Start server (stdio)
npm start

# Start server (HTTP)
TRANSPORT=http PORT=3000 npm start

Transaction Structure

The inscription transaction follows the same output layout as the reference inscriber (ordmail-v10-standalone-026.html). The service-fee outputs are the 11 entries of SERVICE_FEE_OUTPUTS in src/constants.ts:

Input:   UTXO(s) (user funds)
Output 0:  1 sat    - Inscription (OP_FALSE OP_IF "ord" ... OP_ENDIF + P2PKH)
Output 1:  0 sat    - OP_RETURN "ORDnet.io"
Output 2..12:        - 11 service-fee outputs (11,11,11,11,22,22,33,44,66,77,88 = 396 sats)
Output 13: Change (if > 546 sats)

The exact per-output amounts and addresses are listed under Service Fees above and are the single source of truth (SERVICE_FEE_OUTPUTS). ordnet_send omits the fee outputs entirely.

API Endpoints Used

• WhatsOnChain: https://api.whatsonchain.com/v1/bsv/main

• ORDnet Registry: https://registry.ordnet.io

• ORDnet Search: https://search.ordnet.io

License

MIT © ORDnet.io / Mister HHC B.V.

Links

• Website: https://ordnet.io

• Documentation: this README is the reference for the MCP server. (https://docs.ordnet.io documents the ORD/apps suite, not this server.)

• GitHub: https://github.com/ordnet

Environment Variables

Known limitations

• Wallet and spend-policy state are per server process, not per client session. Run the HTTP transport for a single trusted agent/team behind the auth token, not as a public multi-tenant service.

• Balance and UTXO lookups use ORDnet's OWN address index (ordnet-utxo, port 7002, every UTXO node-verified) since v2.5; WhatsOnChain is a connectivity fallback only. New tools in v2.5: ordnet_index_health, ordnet_address_watch.

• UTXO selection skips 1-sat UTXOs as ordinal protection and combines multiple inputs when needed.