Name: OrdiscanMCP v1
Author: Calel33

LABSCO SUMMARY

Coverage of an ecosystem that is awkward to query by hand.

Ordinals data is scattered across inscriptions, runes, BRC-20 and sat ranges, each with its own shape, and answering something like what is in this wallet means hitting several of them. Having all of it behind one authenticated server with Zod-validated inputs turns that into one conversation. It reads only — nothing here signs or broadcasts a transaction — and the key you hand it is Ordiscan's, not a wallet's.

What it is

A read client for the Bitcoin ordinals ecosystem, connecting directly to api.ordiscan.com with no proxy in between. It covers what an address holds, what moved through a transaction, and the reference data behind inscriptions, collections, runes, BRC-20 tokens and rare sats. It runs as an HTTP stream server on port 1337.

What you get

Address tools cover UTXOs, inscriptions, rune balances, BRC-20 balances and rare sats held by a Bitcoin address
Activity tools track inscription, rune and BRC-20 transfers for an address
Transaction tools return transaction info plus the inscriptions and runes that moved in it
ordiscan_inscription_info returns detail on a single inscription; traits, list and transfer tools sit alongside it
ordiscan_rune_market returns market information for a rune, next to a runes list and a name-availability check
ordiscan_brc20_info returns token detail, with a BRC-20 list beside it
ordiscan_main is the general-purpose entry point for rune information and status

Requirements

An Ordiscan API key. Pass it as the apiKey parameter on a call, or set ORDISCAN_API_KEY; every tool sends it as Authorization: Bearer <your-api-key>. Build with npm install and npm run build, then npm start — the server listens on port 1337 and clients reach it at /mcp, locally or through a deployed URL. Rate limiting is handled by Ordiscan at their end, so your key's plan is what governs throughput.

Setup effort

Build from source — git clone https://github.com/Calel33/ordiscan-mcp-v1

See installation options

USE CASES

01

Seeing everything a Bitcoin address holds

Read UTXOs, inscriptions, rune and BRC-20 balances and rare sats for one address.

ordiscan_address_utxosordiscan_address_inscriptionsordiscan_address_runesordiscan_address_brc20ordiscan_address_rare_sats

02

Working out what moved in a transaction

Pull the transaction info and the inscription and rune transfers inside it.

ordiscan_tx_infoordiscan_tx_inscription_transfersordiscan_tx_runes

03

Researching a rune before you buy

Read its market information and check whether the name you want is still unlocked.

ordiscan_rune_market

04

Looking up an inscription or a BRC-20 token

Fetch the detailed record and its traits or token info.

ordiscan_inscription_infoordiscan_brc20_info

29 tools

Listed in project docs. Your client may show a different list.

ordiscan_address_brc20

ordiscan_address_brc20_activity

ordiscan_address_inscriptions

ordiscan_address_rare_sats

ordiscan_address_runes

ordiscan_address_utxos

ordiscan_brc20_info

ordiscan_brc20_list

ordiscan_collection_info

ordiscan_collection_inscriptions

ordiscan_collections_list

ordiscan_inscription_info

ordiscan_inscription_traits

ordiscan_inscription_transfers

ordiscan_inscriptions_activity

BEFORE YOU INSTALL

What to know first

Tools you get

29 tools named in the project's documentation.

Requires

Node.js and npm to build
npx on PATH
An Ordiscan API key (ORDISCAN_API_KEY, or the apiKey parameter)

Where it runs

The documented client runs the server on your machine.

INSTALLATION

Connect your client

This one is built from source rather than installed with a single command.

Server setup

TERMINAL

git clone https://github.com/Calel33/ordiscan-mcp-v1
cd ordiscan-mcp-v1
npm install
npm run build

Start the server with your Ordiscan API key in ORDISCAN_API_KEY (or pass it as the apiKey parameter on a tool call): npm start — it listens at http://localhost:1337/mcp

MCP Clients

Any MCP client — mcp-remote

ANY MCP CLIENT — MCP-REMOTE · JSON

{
  "mcpServers": {
    "ordiscanmcpv1": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "http://localhost:1337/mcp"
      ]
    }
  }
}

OrdiscanMCP v1