What can you do with this server?

Read-only Blocksize market-data discovery server for searching instruments, pricing, and building paid x402 URLs without fetching live data. * Search supported instruments/pairs (symbol, ticker, asset, pair) with optional asset-class filter. * List instruments for vwap, bidask, fx, or metal services. * Inspect pricing, starter-credit positioning, and supported settlement rails. * View product catalog: raw data, premium workflows, state-data products, credit costs, endpoint templates, upgrade path. * Build paid x402 HTTP endpoint URLs (including /v1/state/{pair} for state data) without calling them. * Search and fetch Blocksize docs/catalog entries. * Free, read-only discovery; live data requires credits/subscription; no payment proofs, fund movement, credential storage, or trade execution.

Blocksize Market Data

by jf-cmyk

Overview Schema Source Related Servers Discussions Admin

Python

Blocksize Market Data MCP

Smithery

Read-only Model Context Protocol (MCP) package for Blocksize real-time market-data discovery.

This package gives MCP clients a GitHub-hosted, installable wrapper around the public Blocksize discovery surface. It helps agents search supported instruments, inspect pricing, review the product catalog, find docs, and build exact paid HTTP URLs for live data. It does not fetch live prices, submit x402 payment proofs, move funds, store credentials, or execute trades.

Free Tier and Subscriptions

Eligible authenticated connector users (Claude, Cursor, OpenAI) receive 15,000 free live-data credits every calendar month under an evaluation licence with "Data by Blocksize" attribution. Production use continues with a subscription from EUR 49/month (free trial at https://mcp.blocksize.info/go/free-trial, plans at https://mcp.blocksize.info/go/pricing) or direct x402 payment. Discovery tools in this package are free and read-only; live market data and premium workflow endpoints return an HTTP 402 Payment Required challenge for x402 settlement when called without connector credits. Terms: https://blocksize.info/terms-conditions-data/.

Related MCP server: market-data-mcp

State Data

The hosted Blocksize API includes state-data and oracle-aware coverage for supported assets. State price requests use /v1/state/{pair} and resolve supported protocol/pool symbols through Blocksize state_instruments plus state_pool data when coverage exists. Examples include protocol symbols such as MSOLUSD, JUPSOLUSD, and WSTETHUSD.

Tools

search_pairs - search supported symbols and metadata.
list_instruments - list instruments for vwap, bidask, fx, or metal.
get_pricing_info - inspect current pricing, starter-credit positioning, and supported settlement rails.
get_product_catalog - inspect raw data and premium workflow products, including starter-credit costs, state-data products, endpoint templates, and upgrade path.
get_market_data_endpoint - build a paid x402 HTTP endpoint URL without calling it, including /v1/state/{pair} for state data.
search - search Blocksize docs/catalog entries.
fetch - fetch one docs/catalog entry returned by search.

Install From GitHub

{
  "mcpServers": {
    "blocksize-market-data": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/jf-cmyk/blocksize-agentic-payments-mcp",
        "blocksize-agentic-payments-mcp"
      ]
    }
  }
}

Run Locally

git clone https://github.com/jf-cmyk/blocksize-agentic-payments-mcp
cd blocksize-agentic-payments-mcp
uv run blocksize-agentic-payments-mcp

Optional environment variable:

BLOCKSIZE_BASE_URL=https://mcp.blocksize.info

Public Hosted Remote MCP

Agents that support hosted Streamable HTTP MCP can also connect directly to:

https://mcp.blocksize.info/mcp/server/

Live Data Boundary

Live production market data is available through Blocksize's paid x402 HTTP API, not through this package's discovery tools. The endpoint-builder tools only return URLs and guidance; a direct HTTP call without connector credits or payment returns a 402 Payment Required challenge.

Useful links:

Homepage: https://mcp.blocksize.info/
Product catalog: https://mcp.blocksize.info/data-packages.json
OpenAPI: https://mcp.blocksize.info/openapi.json
Quickstart: https://mcp.blocksize.info/quickstart/remote-mcp
Support: https://mcp.blocksize.info/support
Glama connector: https://glama.ai/mcp/connectors/info.blocksize.mcp/agentic-payments
Smithery: https://smithery.ai/servers/blocksize/agentic-payments?capability=tools#performance

Available Tools

7 tools

fetchCatalog FetchA

Fetch one docs/catalog entry returned by search. Free and read-only.

ParametersJSON Schema

Name	Required	Description	Default
`id`	Yes	Result id returned by search.

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It discloses that the tool is free and read-only, which are important behavioral traits. It does not cover error handling or rate limits, but for a simple fetch, this may suffice.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no fluff. Every word serves a purpose. Front-loaded with the main action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one parameter, output schema present), the description covers purpose, usage context, and safety. No missing information required for a fetch tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the schema already describes the 'id' parameter as 'Result id returned by search.' The description repeats this exactly, adding no new meaning. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it fetches one docs/catalog entry returned by search. It distinguishes from sibling tools like 'search' (which returns many) and 'get_product_catalog' (which might return all). Verb 'Fetch' with resource 'docs/catalog entry' is specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage after search, as it says 'returned by search'. It also notes 'Free and read-only,' indicating safe usage. However, it does not explicitly state when not to use it or mention alternatives beyond the sibling list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_market_data_endpointLive Data Endpoint BuilderA

Build a paid x402 HTTP endpoint URL without calling it or starting payment.

ParametersJSON Schema

Name	Required	Description	Default
`symbol`	Yes	Exact paid HTTP symbol, such as BTC-USD, EURUSD, XAUUSD, or MSOLUSD.
`service`	Yes	Live HTTP data service to prepare. Use state for /v1/state/{pair}.

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A4.1/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, description carries full burden. It clearly states no side effects: does not call endpoint or initiate payment. This is sufficient for a non-destructive URL builder tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence of 11 words, front-loaded with action verb. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists to document return structure. Description sufficiently defines purpose and non-side-effect behavior for a low-complexity tool with 2 parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with clear descriptions for both parameters. Description adds no extra parameter information, so baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description uses specific verb 'Build' and resource 'paid x402 HTTP endpoint URL', clearly distinguishing from sibling tools like 'fetch' which would call the endpoint. Scope is explicit: builds URL without executing or starting payment.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies use case: preparing a URL before fetching. But lacks explicit guidance on when to use this vs siblings (e.g., fetch, get_pricing_info). No exclusions or alternatives mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_pricing_infoPricing InformationA

Return Blocksize pricing, starter-credit positioning, and settlement guidance without starting payment.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description bears full burden. It discloses a key behavior: the tool does not start a payment. However, it omits other important traits such as authentication requirements, rate limits, or whether it caches data. Adds some value but could be more comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no unnecessary words. It is front-loaded and efficient, earning its place without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists (not shown but noted), so the description does not need to detail return structure. It covers the high-level content—pricing, starter-credit positioning, settlement guidance. Could benefit from briefly explaining what 'settlement guidance' entails, but overall it is sufficient for a parameterless info tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, and schema description coverage is 100% (vacuously). The description does not need to add parameter meaning. With no parameters, a baseline score of 4 is appropriate; the description provides adequate context for what the tool returns.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'Return' and clearly identifies the resources: Blocksize pricing, starter-credit positioning, and settlement guidance. It distinguishes itself from sibling tools like get_product_catalog or get_market_data_endpoint by noting 'without starting payment,' implying this is an information-only endpoint.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'without starting payment' suggests this tool is for previewing pricing and guidance before initiating a payment, but there is no explicit comparison to sibling tools or mention of when not to use this tool. Adequate but lacks clear exclusion criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_product_catalogProduct CatalogC

Inspect Blocksize raw data and premium workflow products, including the monthly free tier, state-data products, credit costs, endpoint templates, and upgrade path.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must carry the full behavioral burden. It doesn't state whether this is a read-only operation, how large the response may be, whether results are paginated, or what 'inspect' entails beyond the list of content areas.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It's a single, dense sentence that front-loads the main purpose. It is somewhat list-heavy but efficient for a catalog tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has an output schema, so the description needn't explain return values. However, for a discovery/catalog tool with no annotations and several similar siblings, the description should at least clarify its scope relative to get_pricing_info and list_instruments.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero parameters, the baseline is 4. The description appropriately does not mention input parameters, which is correct for a parameterless catalog tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states what the tool inspects (Blocksize raw data and premium workflow products) but is a broad catalog of many things. It doesn't clearly differentiate from siblings like get_pricing_info or list_instruments, which also seem to expose product-related data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given on when to use this catalog versus get_pricing_info, list_instruments, or fetch. The agent is left to infer usage from the sibling names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_instrumentsInstrument ListB

List supported instruments for one Blocksize service. Free and read-only.

ParametersJSON Schema

Name	Required	Description	Default
`service`	No	Blocksize service namespace to list.	vwap

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

B3.4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It states 'read-only' which implies no destructive effects, and 'free' suggests no cost. However, it does not disclose behaviors like rate limits, error handling, or pagination, though for a simple list tool this is acceptable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise, consisting of two short sentences with no superfluous information. Every word is purposeful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with one optional parameter and an output schema exists, so return values need not be explained. The description covers the primary function, but could mention the default value of 'service' and behavior for invalid inputs for complete clarity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% for the single parameter 'service', which has a clear description in the schema. The tool description adds no additional meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'list' and the resource 'supported instruments' with scope 'for one Blocksize service.' It adds 'Free and read-only' for extra clarity. However, it does not explicitly differentiate from sibling tools like 'search_pairs' which might also list instruments.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The description omits any context about selection criteria or exclusions, leaving the agent without decision support.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

searchCatalog SearchB

Search Blocksize docs/catalog entries. Free and read-only.

ParametersJSON Schema

Name	Required	Description	Default
`query`	Yes	Documentation or catalog search query.

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

B3.1/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden. It adds 'Free and read-only,' which is helpful but lacks details on rate limits, pagination, or response characteristics. The output schema exists but doesn't compensate for the lack of behavioral context in the description itself.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise—one sentence with no wasted words. For a simple tool with one parameter, this is appropriately sized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one param, output schema exists), the description covers the basics but remains vague about query syntax and result handling. It is minimally viable but not fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% for the single parameter 'query,' so the schema already provides meaning. The description does not add any additional semantics beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The tool's purpose is clearly stated: 'Search Blocksize docs/catalog entries.' The verb 'search' and the resource 'Blocksize docs/catalog entries' are specific, though 'catalog entries' is slightly vague. It distinguishes from the sibling 'search_pairs' by context, but not explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides only 'Free and read-only,' which implies safe usage but offers no guidance on when to use this tool versus siblings like 'fetch' or 'search_pairs.' No alternatives or exclusions are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_pairsInstrument SearchA

Search supported Blocksize instruments. Free, read-only, and does not fetch live prices.

ParametersJSON Schema

Name	Required	Description	Default
`query`	Yes	Symbol, ticker, asset, or pair to search for, such as BTC, MSOLUSD, or EURUSD.
`asset_class`	No	Optional asset-class filter for client-side narrowing.	all

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A3.8/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description discloses that the tool is free and read-only, and does not fetch live prices. These are important behavioral traits, especially since no annotations are provided. However, it could mention that results are based on a search query, but overall it is sufficiently transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise at 12 words, front-loading the action. It could be slightly more structured, but it contains no filler and every phrase adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the 100% schema coverage and existence of an output schema, the description adequately covers basic behavior. However, it lacks guidance on how to differentiate among sibling tools (e.g., search vs. list_instruments) and does not mention search behavior like fuzzy matching.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%: both parameters (query and asset_class) have clear descriptions. The tool description adds no further meaning beyond what the schema already provides, so baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Search supported Blocksize instruments,' specifying the verb and resource. It adds 'Free, read-only, and does not fetch live prices,' which distinguishes it from sibling data-fetching tools like get_pricing_info or get_market_data_endpoint.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implicitly indicates read-only use for discovery, but it does not explicitly state when to use this tool over siblings like 'search' or 'list_instruments.' No specific when-not-to-use or alternative guidance is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

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

7 tool updatesv1.0.0Jun 18, 2026
- First observedfetch
- First observedget_market_data_endpoint
- First observedget_pricing_info
- First observedget_product_catalog
- First observedlist_instruments
- First observedsearch
- First observedsearch_pairs

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.5/5.0

Scored 2026-09-28 23:16 across 7 tools

Disambiguation3/5

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.

Naming Consistency3/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

The Quiet Protocol Growth Offense MCP A
com.thequietprotocol.www
Read-only MCP server for The Quiet Protocol's engines, benchmarks, proof, and business data.
Databases Research & Data Finance
292
CryptoDecentral Sovereign MCP A
za.co.cryptodecentral
Read-only educational MCP for CryptoDecentral Sovereign. No auth, trading, custody, or advice.
Education & Learning Tools Cryptocurrency
131
FarmNeural Public API A
com.farmneural
Public, read-only MCP server for FarmNeural company facts, packages, and capabilities.
Documentation Access Developer Tools
1
HODLXXI Read-Only A
io.github.hodlxxi
Public read-only MCP server for HODLXXI agent identity, trust, receipts, and verification.
Blockchain Cryptocurrency
262

Related MCP Servers

CoinGecko MCP - Cryptocurrencyofficial
Blockchain Cryptocurrency Web3 & Decentralized Tech
coingecko
A
license
Not graded
quality
A
maintenance
Official CoinGecko API MCP Server for Crypto Price & Market Data. More details: https://docs.coingecko.com/reference/mcp-server
Updated 3 days ago (2026-10-02 06:43 UTC)
878 npm
58
TypeScript
Apache 2.0
market-data-mcp
SmashToes
-
license
Not graded
quality
Not graded
maintenance
Real-time financial market data MCP server. Stocks, crypto, technicals, sentiment, FDA calendar. No API keys required.
Updated 8 months ago (2026-02-15 04:09 UTC)
-
Dataline MCP Serverofficial
Cryptocurrency Finance
dataline-xyz
A
license
A
quality
D
maintenance
MCP server exposing read-only market data tools for crypto prices, funding rates, and prediction markets via Dataline API.
Updated 4 months ago (2026-06-10 08:36 UTC)
8
14 npm
MIT
x402-mcpofficial
Blockchain Cryptocurrency Payments & Billing
x402node
A
license
C
quality
F
maintenance
MCP server bringing 100+ x402-paid APIs to AI agents (Claude, Cursor, MCP-aware clients). Auto-discovers tools from CDP Bazaar; handles USDC micropayments on Base.
Updated 3 months ago (2026-07-18 20:36 UTC)
100
39 npm
1
MIT

Blocksize Market Data MCP

Free Tier and Subscriptions

State Data

Tools

Install From GitHub

Run Locally

Public Hosted Remote MCP

Live Data Boundary

Available Tools

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

CoinGecko MCP - Cryptocurrencyofficial

Dataline MCP Serverofficial

x402-mcpofficial