Skip to main content
Glama
ORDnet MCP Server

ORDnet MCP Server

Official
by ORDNET

ORDnet MCP Server v3.3

Enable AI agents to create Web3 content on Bitcoin SV blockchain

Version tests test count tools License

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:

Label

Amount

Address

ordiBuilder

11 sats

1HdbyucjYU2yfDFXzAQt3kCdP3VvM4tjzr

onnoBuilder

11 sats

1JKcD1kx8XeJFfd32sug1MaXfruurHTCjv

algoBuilder

11 sats

1AHEUcWuCfdRnfwNsvwZhZSetXjEuAvBot

colleagueI

11 sats

1ENW3XBoAv4KQ4FuQ4MtzNkLq82eJd12PV

protocol

22 sats

15q8YQSqUa9uTh6gh4AVixxq29xkpBBP9z

colleagueD

22 sats

1GeifRjPLWTDqL1DZ2vaqorX6pqCi9PyJB

monitor

33 sats

1EXupec98g8TDTG5cwJwH3U8V3PezvvLv8

indexer

44 sats

18RHRqQhsKKZwMnGevvnRQ8KrryAXvQUWQ

partner

66 sats

19o4rByWRvdq6zziJEfhpe4xdq5z43jYrr

founder

77 sats

1EXupec98g8TDTG5cwJwH3U8V3PezvvLv8

foundation

88 sats

1ATEXPH6FSctbZdAz8MnXCfDpCvDnFrWma

Total

396 sats

11 outputs

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.

Tier

Products

Total per inscription

Wallet

Chrome extension, iOS, Android

3.996 sats

Agent

this MCP server, ORDmail

396 sats

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)

Tool

Description

ordnet_wallet_init

Initialize wallet from WIF private key †

ordnet_wallet_init_env

Initialize from environment variable (recommended)

ordnet_wallet_status

Check wallet status and balance

ordnet_wallet_balance

Get balance for any BSV address

ordnet_wallet_utxos

Get unspent transaction outputs

ordnet_wallet_clear

Clear wallet from memory

Inscriptions (6 tools)

Tool

Description

ordnet_fee_estimate

Calculate fee for an inscription

ordnet_inscribe_prepare

Prepare inscription (no broadcast)

ordnet_inscribe_broadcast

Broadcast prepared transaction

ordnet_inscribe_html

Quick HTML inscription

ordnet_inscribe_json

Quick JSON inscription

ordnet_inscribe_text

Quick plain text inscription

Domains (6 tools)

Tool

Description

ordnet_domain_check

Check domain availability

ordnet_domain_info

Get domain information

ordnet_domain_search

Search registered domains

ordnet_domain_register

Register SNS/OPNS domain

ordnet_domain_register_sns

Quick SNS registration

ordnet_domain_register_opns

Quick OPNS registration

Search & Lookup (4 tools)

Tool

Description

ordnet_search_inscriptions

Search inscriptions

ordnet_get_inscription

Get inscription details

ordnet_get_content_url

Get content URLs

ordnet_validate_address

Validate BSV address

Security (4 tools)

Tool

Description

ordnet_security_encrypt_wallet

Encrypt WIF with AES-256-GCM

ordnet_security_tier

Check security tier

ordnet_security_validate_password

Validate password strength

ordnet_generate_wallet

Generate new random wallet †

Payments (5 tools)

Tool

Description

ordnet_send

Plain BSV payment (miner fee only, no service fee)

ordnet_transfer

Transfer an ordinal/domain to another address

ordnet_x402_quote

Probe an x402-paywalled URL and parse the quote (SSRF-guarded)

ordnet_x402_fetch

Pay an x402 resource in native sats and retrieve it

ordnet_derive_payment_address

Derive a BRC-42 payment address (watch-only)

Identity & signing (3 tools)

Tool

Description

ordnet_identity

Get the wallet's identity public key

ordnet_sign_message

Sign a message with the wallet key

ordnet_verify_message

Verify a signed message

Utilities (11 tools)

Tool

Description

ordnet_info

Server information

ordnet_content_types

List supported content types

ordnet_tx_simulate

Decode/simulate a raw tx via ORDnet's own node

ordnet_policy_set

Set spend-policy limits (within operator ceilings)

ordnet_policy_status

Show the active spend policy and session total

ordnet_index_health

UTXO index health

ordnet_address_watch

Add an address to the watch index

ordnet_bsvmap_inscribe

Inscribe a BSVmap tile

ordnet_inscribe_binary

Inscribe binary content (e.g. an image)

ordnet_tx_status

Look up a transaction's status

ordnet_price

BSV price in fiat

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

Tier

Method

Security Level

Environment

ORDNET_WIF env var

⭐⭐⭐ Highest

Encrypted

AES-256-GCM encrypted store

⭐⭐ Medium

Plaintext

Direct WIF input

⭐ Lowest

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.

Environment Variables

Variable

Required

Purpose

ORDNET_WIF

for wallet ops

Wallet private key (WIF). On HTTP transport this is the ONLY way to load a wallet.

TRANSPORT

no

stdio (default) or http.

PORT

no

HTTP port (default 3000).

ORDNET_MCP_AUTH_TOKEN

yes, when TRANSPORT=http

Bearer token (min. 32 chars). Server refuses to start without it. Generate: openssl rand -hex 32.

ORDNET_POLICY_MAX_SATS_PER_TX

recommended on http

Operator hard ceiling per transaction. ordnet_policy_set can tighten below it, never loosen above it.

ORDNET_POLICY_MAX_SATS_PER_SESSION

recommended on http

Operator hard ceiling per server session.

ORDNET_UTXO_URL

no

Base URL of the ordnet-utxo index (default http://127.0.0.1:7002).

ORDNET_API

no

Base URL of the ORDnet API used for price and proxy calls (default https://api.ordnet.io).

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.

Available Tools

45 tools
ordnet_address_watchWatch Address in ORDnet IndexA
Idempotent

Register a BSV address in ORDnet's own UTXO index watchlist.

The index seeds the address immediately (WhatsOnChain as outpoint hint, every UTXO verified by ORDnet's own node) and then tracks it in real time via the tip-follower. Unknown addresses are also auto-registered on their first balance/UTXO query; this tool lets an agent pre-register addresses so that first query is instant.

Args:

  • address (string): BSV address to watch

  • label (string, optional): label for the watchlist entry (default: "mcp")

Returns: Watchlist registration result from the index.

Inputs: address (required), label.

ordnet_bsvmap_inscribeClaim BSVmap TileA

Claim a BSVmap tile by inscribing ".bsvmap" (text/plain), following the bitmap convention on BSV. Tiles 0-999999 map to the 1M-tile BSVmap grid.

Note: first-is-first — if the tile was already claimed on-chain, your inscription will not make you the owner. Check bsvmap.io first.

Args:

  • tile (number): tile number 0-999999

  • feePerByte (number, optional): default 0.15

Returns prepared inscription; broadcast with ordnet_inscribe_broadcast.

Inputs: tile (required), feePerByte.

ordnet_content_typesList Supported Content TypesA
Read-onlyIdempotent

Get list of all supported content types for inscriptions.

Returns: { contentTypes: [...] }

Inputs: no named parameters.

ordnet_derive_payment_addressDerive Payment Address (BRC-42/29)A
Read-onlyIdempotent

Derive a unique, deterministic payment address for a given invoice or reference string (BRC-42/29-style key derivation).

Each invoice number yields a different address controlled by the same wallet, so incoming payments for different invoices are unlinkable on-chain — the foundation for clean x402 payment flows. The same invoice always derives the same address, so a payer and payee can compute it independently. Requires an initialized wallet.

Args:

  • invoiceNumber (string): invoice/reference string

Returns: { address, publicKey, invoiceNumber }

Inputs: invoiceNumber (required).

ordnet_domain_checkCheck Domain AvailabilityA
Read-onlyIdempotent

Check if a domain name is available for registration.

Args:

  • name (string): Domain name without extension (e.g., "myname")

  • extension (string): Domain extension (default: .sats)

Returns: { available: boolean, owner?: string, inscriptionId?: string }

Inputs: name (required), extension.

ordnet_domain_infoGet Domain InformationA
Read-onlyIdempotent

Get detailed information about a domain.

Args:

  • fullName (string): Full domain name (e.g., "myname.sats")

Returns: { name, extension, owner, inscriptionId, genesisHeight, protocol }

Inputs: fullName (required).

ordnet_domain_registerRegister DomainA
Destructive

Register a new SNS/OPNS domain on the blockchain.

Creates and broadcasts a domain registration inscription.

Args:

  • name (string): Domain name without extension

  • extension (string): Domain extension (default: .sats)

  • protocol (string): Registration protocol: sns or opns (default: sns)

  • feePerByte (number): Fee per byte (default: 0.2)

Returns: { txid, inscriptionId, domain }

Requires: Wallet must be initialized.

Inputs: name (required), protocol, extension, feePerByte.

ordnet_domain_register_opnsRegister OPNS DomainA
Destructive

Quick registration of an OPNS domain.

Args:

  • name (string): Domain name without extension

  • extension (string): Extension (default: .sats)

  • feePerByte (number): Fee per byte (default: 0.2)

Returns: { txid, inscriptionId, domain }

Inputs: name (required), extension, feePerByte.

ordnet_domain_register_snsRegister SNS DomainB
Destructive

Quick registration of an SNS domain (.sats, .btc, etc).

Args:

  • name (string): Domain name without extension

  • extension (string): Extension (default: .sats)

  • feePerByte (number): Fee per byte (default: 0.2)

Returns: { txid, inscriptionId, domain }

Inputs: name (required), extension, feePerByte.

ordnet_fee_estimateEstimate Inscription FeeA
Read-onlyIdempotent

Calculate fee estimate for an inscription.

Service fees breakdown (per ordmail-v10-standalone-026.html):

  • ordiBuilder / onnoBuilder / algoBuilder / colleagueI: 11 sats each

  • protocol / colleagueD: 22 sats each

  • monitor: 33 sats, indexer: 44 sats, partner: 66 sats

  • founder: 77 sats, foundation: 88 sats

  • Total: 396 sats across 10 distinct addresses

Args:

  • contentSize (number): Size of content in bytes

  • feePerByte (number): Fee per byte (default: 0.15 = 150 sats/KB, miner fee floor 200 sats)

Returns: { estimatedTxSize, minerFee, serviceFee, totalCost, breakdown }

Inputs: contentSize (required), feePerByte.

ordnet_generate_walletGenerate New WalletA
Read-only

Generate a new random BSV wallet.

WARNING: Store the WIF securely! It cannot be recovered if lost.

Returns: { wif, address }

Inputs: no named parameters.

ordnet_get_content_urlGet Content URLA
Read-onlyIdempotent

Get the URL to view inscription content.

Args:

  • inscriptionId (string): Inscription ID

Returns: { inscriptionId, contentUrl, viewUrl, transactionUrl }

Inputs: inscriptionId (required).

ordnet_get_inscriptionGet Inscription DetailsA
Read-onlyIdempotent

Get detailed information about a specific inscription.

Args:

  • inscriptionId (string): Inscription ID (format: txid_outputIndex)

Returns: { inscriptionId, contentType, contentSize, owner, ... }

Inputs: inscriptionId (required).

ordnet_identityGet BRC-100 Identity KeyA
Read-onlyIdempotent

Return the wallet's BRC-100 identity: its public key and address.

This is the agent's on-chain identity — counterparties can use the public key to verify signatures (ordnet_verify_message) and to confirm the agent controls the address. Requires an initialized wallet.

Returns: { publicKey, address }

Inputs: no named parameters.

ordnet_index_healthORDnet UTXO Index HealthA
Read-onlyIdempotent

Check the health and sync status of ORDnet's own address/UTXO index (ordnet-utxo).

This index is the PRIMARY source for balance and UTXO lookups since v2.5 — every UTXO in it has been individually verified by ORDnet's own BSV node. WhatsOnChain is only used as a connectivity fallback.

Returns: { status, index_height, node_height, in_sync }

Inputs: no named parameters.

ordnet_infoORDnet Server InfoA
Read-onlyIdempotent

Get information about the ORDnet MCP server.

Returns server version, capabilities, and service fee information.

Inputs: no named parameters.

ordnet_inscribe_binaryInscribe Binary ContentA

Prepare an inscription for BINARY content (images, audio, video, PDF) from base64.

Bytes are inscribed untouched — use this instead of ordnet_inscribe_prepare for anything that is not text. Supported: image/png, image/jpeg, image/gif, image/webp, image/svg+xml, audio/mpeg, video/mp4, application/pdf.

Args:

  • contentBase64 (string): base64-encoded content

  • contentType (string): MIME type, e.g. image/png

  • feePerByte (number, optional): default 0.15

Returns prepared inscription; broadcast with ordnet_inscribe_broadcast.

Inputs: contentType (required), contentBase64 (required), feePerByte.

ordnet_inscribe_broadcastBroadcast InscriptionA
Destructive

Broadcast a prepared inscription transaction to the BSV network.

WARNING: This action is IRREVERSIBLE. The transaction will be permanently recorded on the blockchain.

Args:

  • rawHex (string): Raw transaction hex from ordnet_inscribe_prepare

Returns: { txid, inscriptionId, viewUrl, transactionUrl }

Inputs: rawHex (required).

ordnet_inscribe_htmlInscribe HTML ContentA
Destructive

Create and broadcast an HTML inscription in one step.

Convenience tool that prepares and broadcasts an HTML inscription.

Args:

  • content (string): HTML content to inscribe

  • feePerByte (number): Fee per byte (default: 0.2)

Returns: { txid, inscriptionId, viewUrl }

Requires: Wallet must be initialized.

Inputs: content (required), feePerByte.

ordnet_inscribe_jsonInscribe JSON ContentA
Destructive

Create and broadcast a JSON inscription in one step.

Args:

  • content (string): JSON content to inscribe

  • feePerByte (number): Fee per byte (default: 0.2)

Returns: { txid, inscriptionId, viewUrl }

Inputs: content (required), feePerByte.

ordnet_inscribe_preparePrepare InscriptionA

Prepare an inscription transaction without broadcasting.

Creates a signed transaction ready for broadcast. Returns the raw hex and fee breakdown for review before broadcasting.

Args:

  • content (string): Content to inscribe (HTML, text, JSON, etc.)

  • contentType (string): MIME type (default: text/html;charset=utf8)

  • feePerByte (number): Fee per byte (default: 0.2)

Returns: { rawHex, txid, feeEstimate, inscriptionId }

Requires: Wallet must be initialized first.

Inputs: content (required), feePerByte, contentType.

ordnet_inscribe_textInscribe Plain TextA
Destructive

Create and broadcast a plain text inscription in one step.

Args:

  • content (string): Text content to inscribe

  • feePerByte (number): Fee per byte (default: 0.2)

Returns: { txid, inscriptionId, viewUrl }

Inputs: content (required), feePerByte.

ordnet_policy_setSet Spend PolicyA

Configure spend limits for this server session (agent safety layer).

When any limit is set, every broadcast is first simulated via ORDnet's own node and BLOCKED if it would exceed a limit (fail-closed). When no limits are set, broadcasts behave exactly as before.

Limits apply to the TOTAL output value of a transaction, including change back to the agent's own wallet (a conservative upper bound).

Args:

  • maxSatsPerTx (number|null, optional): Max output sats per transaction; null removes the limit

  • maxSatsPerSession (number|null, optional): Max cumulative output sats this session; null removes the limit

  • resetSession (boolean, optional): Reset the session spend counter

Returns: The active policy after applying changes.

Inputs: maxSatsPerTx, resetSession, maxSatsPerSession.

ordnet_policy_statusGet Spend Policy StatusA
Read-onlyIdempotent

Show the active spend policy and session totals.

Returns: { maxSatsPerTx, maxSatsPerSession, spentThisSession, broadcastCount }

Inputs: no named parameters.

ordnet_priceBSV PriceA
Read-onlyIdempotent

Get the current BSV price in fiat, via ORDnet's own CoinGecko proxy.

Lets an agent convert satoshis to USD/EUR before spending.

Args:

  • currencies (string, optional): comma-separated, default "usd,eur"

Returns: { bsv: { usd, eur, ... }, satsPerUsd }

Inputs: currencies.

ordnet_search_inscriptionsSearch InscriptionsB
Read-onlyIdempotent

Search for inscriptions on the BSV blockchain.

Args:

  • query (string): Search query

  • contentType (string, optional): Filter by content type

  • limit (number): Maximum results (default: 20)

Returns: { inscriptions: [...], count }

Inputs: query (required), limit, contentType.

ordnet_security_encrypt_walletEncrypt WalletA
Read-onlyIdempotent

Encrypt a WIF private key with AES-256-GCM.

Use this to create an encrypted wallet that can be stored safely. The encrypted data can later be decrypted with ordnet_wallet_init with the password.

Args:

  • wif (string): WIF private key to encrypt

  • password (string): Strong password (min 12 chars)

Returns: { encrypted: { iv, data, tag, salt } }

Inputs: wif (required), password (required).

ordnet_security_tierGet Security TierA
Read-onlyIdempotent

Check the current wallet security tier.

Tiers (highest to lowest):

  1. environment - WIF from environment variable

  2. encrypted - WIF from encrypted store

  3. plaintext - WIF provided directly (not recommended)

Returns: { tier, envVarSet, recommendation }

Inputs: no named parameters.

ordnet_security_validate_passwordValidate Password StrengthA
Read-onlyIdempotent

Check if a password meets security requirements.

Requirements:

  • Minimum 12 characters

  • At least one uppercase letter

  • At least one lowercase letter

  • At least one number

  • At least one special character

Args:

  • password (string): Password to validate

Returns: { valid: boolean, errors: string[] }

Inputs: password (required).

ordnet_sendSend BSV PaymentA
Destructive

Send a plain BSV payment (P2PKH) from the initialized wallet.

THE core tool for agent payments: miner fee only (0.15 sat/byte, min 200 sats), NO service fees — micropayments stay lean. Optional OP_RETURN data lets you attach a payment reference (e.g. an x402 invoice ID).

Safety: spend policy (ordnet_policy_status) is enforced; 1-sat ordinal UTXOs are never used as funding.

Args:

  • to (string): recipient BSV address

  • satoshis (number): amount in satoshis

  • opReturn (string, optional): OP_RETURN payload / payment reference

Returns: { txid, satoshis, minerFee, change, transactionUrl }

Inputs: to (required), satoshis (required), opReturn.

ordnet_sign_messageSign Message (BRC-100)A
Read-onlyIdempotent

Sign an arbitrary message with the wallet's private key (BRC-100 createSignature).

Use this to prove control of the identity key, authenticate to a service, or sign an x402 payment authorization off-chain. The private key never leaves the server. Requires an initialized wallet.

Args:

  • message (string): the message to sign

Returns: { publicKey, signature, messageHash }

Inputs: message (required).

ordnet_transferTransfer Ordinal or DomainA
Destructive

Transfer an inscription (ordinal, .web3/SNS/OPNS domain, BSVmap tile) to another address.

1SatOrdinals semantics: the inscription outpoint becomes input 0 and the 1-sat output to the recipient becomes output 0 — the sat carries the inscription. The outpoint is verified as unspent via ORDnet's own node before building. Miner fee only.

Args:

  • inscriptionTxid (string): txid of the inscription outpoint

  • inscriptionVout (number): output index (usually 0)

  • to (string): recipient BSV address

Returns: { txid, transferred, to, minerFee, transactionUrl }

Inputs: to (required), inscriptionTxid (required), inscriptionVout (required).

ordnet_tx_simulateSimulate Transaction (Dry Run)A
Read-onlyIdempotent

Decode and inspect a raw transaction via ORDnet's OWN node WITHOUT broadcasting it.

Use this BEFORE ordnet_inscribe_broadcast to verify exactly what a transaction will do: destinations, amounts, and safety warnings (e.g. 1-satoshi outputs that are likely ordinals/inscriptions).

Args:

  • rawHex (string): Raw transaction hex to simulate

Returns: { txid, sizeBytes, outputCount, totalOutputSats, outputs[], warnings[] }

Inputs: rawHex (required).

ordnet_tx_statusTransaction StatusA
Read-onlyIdempotent

Check the status and confirmations of a transaction via ORDnet's own node.

Essential after ordnet_send / ordnet_inscribe_broadcast / ordnet_transfer: poll this to see your transaction confirm.

Args:

  • txid (string): transaction ID

Returns: { txid, found, confirmations, blockhash, blocktime }

Inputs: txid (required).

ordnet_validate_addressValidate BSV AddressA
Read-onlyIdempotent

Validate a BSV address format.

Args:

  • address (string): BSV address to validate

Returns: { valid: boolean, address }

Inputs: address (required).

ordnet_verify_messageVerify Message Signature (BRC-100)A
Read-onlyIdempotent

Verify a signature against a message and public key (BRC-100 verifySignature).

Does NOT require a wallet — anyone can verify. Use this to check that a counterparty's message (e.g. a payment authorization or a signed quote) really came from the holder of a given public key.

Args:

  • message (string): the original message

  • signature (string): signature hex from ordnet_sign_message

  • publicKey (string): compressed public key hex of the claimed signer

Returns: { valid: boolean }

Inputs: message (required), publicKey (required), signature (required).

ordnet_wallet_balanceGet BSV BalanceA
Read-onlyIdempotent

Get balance for any BSV address.

Args:

  • address (string, optional): BSV address. Uses wallet address if not provided.

Returns: { address: string, confirmed: number, unconfirmed: number, total: number }

Inputs: address.

ordnet_wallet_clearClear WalletA
DestructiveIdempotent

Clear wallet from memory. Use when done with operations.

Returns: { cleared: true }

Inputs: no named parameters.

ordnet_wallet_initInitialize ORDnet WalletA
Idempotent

Initialize wallet from WIF private key for blockchain operations.

This is the first step before creating inscriptions. The wallet will be used for:

  • Creating and signing inscription transactions

  • Paying service fees (396 sats across 11 outputs / 10 addresses)

  • Receiving change from transactions

Security: WIF is held in memory only, not persisted. Use ordnet_wallet_init_env for production.

Args:

  • wif (string): WIF private key (starts with 5, K, or L, 51-52 chars)

Returns: { address: string, publicKey: string, balanceSatoshis: number }

Example: ordnet_wallet_init({ wif: "L1a2b3c4d5..." }) → Wallet initialized at 1ABC...

Inputs: wif (required).

ordnet_wallet_init_envInitialize Wallet from EnvironmentA
Idempotent

Initialize wallet from environment variable (highest security tier).

Reads WIF from environment variable instead of passing it directly. Recommended for production use.

Args:

  • envVarName (string): Environment variable name (default: ORDNET_WIF)

Returns: { address: string, balanceSatoshis: number }

Example: export ORDNET_WIF="L1a2b3c4..." ordnet_wallet_init_env({}) → Wallet initialized

Inputs: envVarName.

ordnet_wallet_statusGet Wallet StatusA
Read-onlyIdempotent

Check current wallet initialization status and balance.

Returns wallet address and balance if initialized.

Returns: { initialized: boolean, address?: string, balanceSatoshis?: number }

Inputs: no named parameters.

ordnet_wallet_utxosGet Wallet UTXOsA
Read-onlyIdempotent

Get unspent transaction outputs (UTXOs) for an address.

Args:

  • address (string, optional): BSV address. Uses wallet address if not provided.

  • limit (number): Maximum UTXOs to return (default: 5)

Returns: { utxos: [{ txid, vout, satoshis }], count: number }

Inputs: limit, address.

ordnet_x402_fetchFetch x402 Resource (auto-pay)A
Destructive

Consume an x402-paywalled resource in one call: detect the 402, pay the quoted amount in native BSV sats from the loaded wallet, retry with proof, and return the resource plus the settlement receipt.

Safety:

  • maxSats is REQUIRED: the tool refuses quotes above it (agent-set budget)

  • the spend policy (ordnet_policy_status) is enforced on the payment

  • only the 'exact' scheme on network 'bsv' is supported; other networks (e.g. USDC on Base) are reported honestly as unsupported

  • non-paywalled URLs are fetched and returned without any payment

Args:

  • url (string): resource URL

  • method (string, optional): GET or POST (default GET)

  • maxSats (number): spending guard in satoshis

Returns: { status, body, paid?: { txid, satoshis, payTo }, receipt? }

Inputs: url (required), maxSats (required), method.

ordnet_x402_quotex402 Price Quote (no payment)A
Read-onlyIdempotent

Inspect an x402-paywalled URL WITHOUT paying: returns the price, payTo address, and payment requirements from the HTTP 402 response.

Use this to check costs before committing. Free and read-only.

Args:

  • url (string): resource URL

  • method (string, optional): GET or POST (default GET)

Returns: { isPaywalled, priceSats?, network?, payTo?, description?, accepts }

Inputs: url (required), method.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 45 tools

    Disambiguation2/5

    Several tools are near-duplicates: ordnet_inscribe_html/json/text are all one-step broadcast tools differing only by content type, and ordnet_domain_register_sns/opns duplicate ordnet_domain_register with a protocol parameter. While descriptions are clear, the redundant convenience wrappers create ambiguity about which tool to select.

    Naming Consistency3/5

    All tools share the ordnet_ prefix and snake_case, but the pattern is inconsistent: some follow topic_verb (wallet_init, domain_check), others verb_topic (search_inscriptions, generate_wallet). Suffixes like _env, _sns, _html add further irregularity.

    Tool Count2/5

    45 tools is well above the 25-tool threshold, and several are redundant convenience wrappers (inscribe_html/json/text, domain_register_sns/opns) that could be consolidated. The breadth of domains partially justifies the count, but it still feels heavy.

    Completeness3/5

    The server covers wallet, inscriptions, domains, payments, identity, x402, and indexing thoroughly. Minor gaps include no way to list inscriptions owned by an address or retrieve address transaction history, but most core workflows (create, broadcast, transfer, read, search) are covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers