Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Blocksize Agentic Market Intelligence

REMOTE · MCP.BLOCKSIZE.INFO

Multi-venue VWAP, bid/ask, crypto FX, metals and equities with provenance receipts for AI agents

+3 this week 83 Trust /100

Last scanned (8 hours ago)

Scores higher than 89% of remote servers

Reachable. Last reached 25 Oct 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability84
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1139 tokens (~113/item across 10 items; 9 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
  • Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 93% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 13. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 25 Oct 2026 · Probed https://mcp.blocksize.info/mcp/server/?utm_source=mcp-registry

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.blocksize.info CN=YE2,O=Let's Encrypt,C=US 21 Oct 2026 19 Jan 2027 ECDSA 256 ECDSA-SHA384 646fb86a71721517b34dd079919c52e477e
SANs: mcp.blocksize.info
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.blocksize.info. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
info. present 9986 8 Verified
blocksize.info. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.blocksize.info/mcp/server/?utm_source=mcp-registry Verified 200
http (plaintext) http://mcp.blocksize.info/mcp/server/?utm_source=mcp-registry HTTPS enforced 301 https://mcp.blocksize.info/mcp/server/?utm_source=mcp-registry
MCP tools · 9 exposed · ~901 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
fetch ~72

Fetch one document or instrument guide returned by search. This is free, read-only content retrieval with no account, credential, payment, or live-price side effects.

NameTypeReqDescription
idstringyesResult id returned by the search tool, for example doc:pricing, doc:quickstart, or instrument:crypto:BTCUSD.
NameTypeReqDescription
resultstringyes–

No examples provided.

get_market_data_endpoint ~190

Build the exact x402-protected HTTP URL for one live market-data request. Returns method, URL, service notes, pricing docs, and next steps; it is read-only and does not fetch prices, charge a wallet, or submit payment.

NameTypeReqDescription
servicestringyesLive HTTP data service to prepare: vwap for crypto VWAP, bidask for crypto pairs or catalog-confirmed equity symbols such as AAPLXUSD, state for AMM state price, vwap30m for latest completed 30-minut…
symbolstringyesExact pair or ticker to use in the paid HTTP URL, such as BTC-USD, AAPL, MSFT, NVDA, EURUSD, or XAUUSD. Use search_pairs first if unsure.
NameTypeReqDescription
resultstringyes–

No examples provided.

get_pricing_info ~51

Inspect current direct x402 per-call prices, authenticated connector starter-credit costs, supported USDC settlement networks, and the account-plan contact path. This is free read-only metadata; it does not initiate payment.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_product_catalog ~55

Inspect Blocksize raw data, supported equity ticker bid/ask, and premium agent-native workflow products, including starter-credit positioning, credit costs, suggested paid prices, endpoint templates, and upgrade path. This is free and read-only.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_workflow_endpoint ~69

Build the exact paid HTTP endpoint, method, starter-credit cost, and example body for a premium Blocksize workflow. This is free and read-only; it does not fetch live data, charge credits, or start x402.

NameTypeReqDescription
productstringyesPremium Blocksize workflow product to prepare.
NameTypeReqDescription
resultstringyes–

No examples provided.

list_instruments ~127

List the supported instruments for one Blocksize service. This is free, read-only catalog metadata; it does not fetch live prices, create accounts, or start x402 payment.

NameTypeReqDescription
limitinteger–Maximum instruments to return. Use offset to traverse the stable catalog without requesting the entire upstream array.
offsetinteger–Zero-based offset into the sorted instrument catalog.
servicestring–Blocksize service namespace to list: vwap for crypto VWAP pairs, bidask for shared bid/ask symbols including supported equities, fx for FX pairs, or metal for metals.
NameTypeReqDescription
resultstringyes–

No examples provided.

recommend_account_plan ~112

Recommend a sales-assisted Blocksize account plan from expected live-call volume, team size, recurring use, and SLA needs. This is free and does not collect contact details, create an entitlement, or start a purchase.

NameTypeReqDescription
expected_monthly_live_callsintegeryesExpected live-data calls per month.
needs_slaboolean––
recurring_days_per_monthinteger–Days per month the workflow is expected to run.
team_seatsinteger–People or service identities sharing access.
NameTypeReqDescription
resultstringyes–

No examples provided.

search ~75

Search Blocksize documentation and catalog metadata by keyword. This free read-only search returns document and instrument ids for fetch; it does not return live prices or start payment.

NameTypeReqDescription
querystringyesDocumentation or catalog search query, such as pricing, quickstart, credits, x402, Solana, Base, BTC, or VWAP.
NameTypeReqDescription
resultstringyes–

No examples provided.

search_pairs ~150

Discover supported crypto, equity, FX, and metal symbols before using the paid HTTP API. Returns up to 50 catalog matches with asset class, available services, and pricing tier; it is free, read-only, and never returns live prices or starts payment.

NameTypeReqDescription
asset_classstring–Optional asset-class filter. Use all for the full catalog, crypto for digital assets, equity/equities for catalog-confirmed stock symbols such as AAPLXUSD, fx for currency pairs, or metal for metals.
querystringyesSymbol, ticker, asset, or pair to search for, such as BTC, BTC-USD, ETH, AAPL, EURUSD, or XAUUSD.
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the Blocksize Agentic Market Intelligence MCP server?

Blocksize Agentic Market Intelligence is a hosted endpoint at https://mcp.blocksize.info/mcp/server/?utm_source=mcp-registry, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.blocksize.info

# add to Claude Code
claude mcp add --transport http info-blocksize-mcp-agentic-payments 'https://mcp.blocksize.info/mcp/server/?utm_source=mcp-registry'
Common questions

What is the Blocksize Agentic Market Intelligence MCP server?

Blocksize Agentic Market Intelligence is an MCP server listed in the public MCP registry as info.blocksize.mcp/agentic-payments. Multi-venue VWAP, bid/ask, crypto FX, metals and equities with provenance receipts for AI agents. This page covers its hosted endpoint (https://mcp.blocksize.info/mcp/server/?utm_source=mcp-registry).

Is the Blocksize Agentic Market Intelligence MCP server safe to use?

Blocksize Agentic Market Intelligence scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Blocksize Agentic Market Intelligence MCP server expose?

Blocksize Agentic Market Intelligence exposes 9 tools: search_pairs, list_instruments, get_pricing_info, get_product_catalog, recommend_account_plan, and 4 more. Their descriptions and schemas cost roughly 901 tokens of context every time the server is loaded.

Does the Blocksize Agentic Market Intelligence MCP server require authentication?

No. We connected to Blocksize Agentic Market Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Blocksize Agentic Market Intelligence MCP server still maintained?

Blocksize Agentic Market Intelligence is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.