bitmap-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_bitmapA | Resolve a Bitmap district number (a Bitcoin block height) to its claiming inscription id, owner address, and sat. A district N is owned by the first valid '.bitmap' inscription. |
| get_inscriptionA | Look up an Ordinals inscription by id and return its content type, owner address, sat, genesis height, current location, and content URL. |
| get_runeA | Look up a Rune by name (with or without bullet separators) and return supply, divisibility, holder count, mint status, and market data. |
| get_feesA | Return current recommended Bitcoin transaction fee estimates in sat/vB (fastest, half hour, hour, economy, minimum). |
| get_blockA | Return a summary of a Bitcoin block (hash, timestamp, transaction count, size, weight, difficulty). Omit height for the current chain tip. |
| resolve_satA | Given a sat ordinal number, return its Rodarmor rarity (common, uncommon, rare, epic, legendary, mythic), the block it was minted in, and its current inscription/owner if inscribed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct entity or concept: sat ordinals, Bitmap districts, inscriptions, runes, fees, and blocks. There is no overlap or ambiguity between tool purposes.
All tool names follow a uniform verb_noun snake_case pattern (resolve_sat, get_bitmap, get_inscription, get_rune, get_fees, get_block). The naming is fully consistent.
Six tools is well within the ideal range and appropriate for a Bitcoin/Ordinals data server. Each tool covers a meaningful aspect without redundancy.
The tool set covers the core entities of the domain (sats, inscriptions, bitmaps, runes, blocks, fees), but lacks address-level or transaction-level lookups, which are common extensions for such a service. These gaps are minor and not severe.