Blocksize Market Data
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BLOCKSIZE_BASE_URL | No | Optional base URL for the Blocksize MCP server | https://mcp.blocksize.info |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_pairsA | Search supported Blocksize instruments. Free, read-only, and does not fetch live prices. |
| list_instrumentsB | List supported instruments for one Blocksize service. Free and read-only. |
| get_pricing_infoA | Return Blocksize pricing, starter-credit positioning, and settlement guidance without starting payment. |
| get_product_catalogC | Inspect Blocksize raw data and premium workflow products, including the monthly free tier, state-data products, credit costs, endpoint templates, and upgrade path. |
| get_market_data_endpointA | Build a paid x402 HTTP endpoint URL without calling it or starting payment. |
| searchB | Search Blocksize docs/catalog entries. Free and read-only. |
| fetchA | Fetch one docs/catalog entry returned by search. Free and read-only. |
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 7 tools
Most tools have distinct purposes (search vs fetch, list_instruments vs search_pairs), but get_product_catalog and get_pricing_info overlap on pricing/credit information, and search_pairs and list_instruments both operate on the instrument domain, creating some potential for misselection.
The set mixes verb_noun names (get_product_catalog, list_instruments, search_pairs) with bare verbs (fetch, search), which is readable but not a single predictable convention.
Seven tools is well-scoped for a market-data discovery/catalog server, with each tool earning a distinct role in search, fetch, listing, pricing, and endpoint construction.
The discovery surface (search, fetch, catalog, pricing, instruments, endpoint builder) is fairly complete for its purpose, though the lack of any live data retrieval tool means agents must exit the server to actually obtain prices.