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
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
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_catalogB | Inspect Blocksize raw data and premium workflow products, including 50 starter live-data credits, 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
Each tool has a distinct purpose, but 'search' and 'fetch' both deal with catalog entries, and 'list_instruments' and 'search_pairs' both involve instruments, leading to possible confusion.
Most tools follow a verb_noun pattern, but 'fetch' lacks an underscore, and the verbs vary between 'get_', 'list_', 'search_', and 'fetch', introducing minor inconsistency.
Seven tools is an appropriate number for a market data server, covering catalog inspection, search, pricing, and endpoint building without being excessive.
The set covers catalog, search, and pricing, but lacks tools for actual market data retrieval (only endpoint building is provided) and direct instrument data querying, leaving notable gaps.