Skip to main content
Glama

Blockstream Info

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Blockstream.info Esplora MCP — Bitcoin block/tx/address explorer.

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
30.6% over 40 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-blockstream-info
GitHub Stars
0
Server Listing
mcp-blockstream-info

TDQS

B3.4/5.0

Scored across 39 tools

Disambiguation3/5

Most tools have clearly distinct roles (Bitcoin explorer endpoints, memory, subscriptions, Polymarket analytics), and the verbose descriptions help separate near-neighbors like ask_pipeworx_grounded vs ask_pipeworx vs deep_research. However ask_pipeworx_beta is explicitly documented as identical to ask_pipeworx, and the research/meta cluster (ask_pipeworx, deep_research, discover_tools, suggest_questions, entity_profile, recent_changes, validate_claim) plus the Polymarket cluster (bet_research vs polymarket_edges vs polymarket_arbitrage) have genuinely fuzzy boundaries.

Naming Consistency3/5

All names use snake_case with no camelCase mixing, which is good, but conventions alternate between bare nouns (address, block, mempool, transaction, fee_estimates, tip_height) and verb_noun/action forms (address_txs, tx_status, validate_claim, resolve_entity, compare_entities, scan_dependency, generate_llms_txt). The Bitcoin names also lack any domain prefix while the Pipeworx meta-tools carry one, so the pattern is readable but not predictable.

Tool Count2/5

39 tools is well above the 25-tool ceiling for a well-scoped server, and the set is not even single-purpose: roughly 8 Bitcoin/Esplora tools sit alongside ~30 unrelated Pipeworx gateway, memory, subscription, AI-marketing and Polymarket tools. The Bitcoin surface alone (8 tools) would be appropriately scoped; the combined surface is overloaded.

Completeness3/5

The Esplora-style Bitcoin surface covers address summary, address transactions, block lookup, raw transaction, tx confirmation status, tip height, mempool stats and fee estimates, but omits common operations such as address UTXO/balance lookups, listing a block's transactions, recent-blocks listing, and transaction broadcast — noticeable gaps for a block-explorer domain. The Pipeworx meta layer is broad, but the server as a whole reads as two partially-complete surfaces stitched together.

Tool Schema Changelog

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

  1. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "market": "will-bitcoin-reach-100k-in-july-2026"
-  },
-  {
-    "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
-  }
-]New value: +[
+  {
+    "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  },
+  {
+    "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  }
+]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
    • Changedpolymarket_kalshi_spread2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "topic": "fed"
-  },
-  {
-    "topic": "btc"
-  }
-]New value: +[
+  {
+    "topic": "fed"
+  },
+  {
+    "topic": "btc"
+  },
+  {
+    "topic": "bitcoin"
+  },
+  {
+    "topic": "fed rate decision"
+  }
+]
      • changedInput schema / properties / topic / description
        Previous value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."
  2. 1 tool update
    • Changedentity_profile3 fields changed
      • changedInput schema / properties / type / description
        Previous value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."
      • changedInput schema / properties / type / enum
        Previous value: -[
-  "company"
-]New value: +[
+  "company",
+  "ticker"
+]
      • changedInput schema / properties / value / description
        Previous value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."
  3. 1 tool update
    • Changedresolve_entity1 field changed
      • changedInput schema / properties / value / description
        Previous value: -"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\")."New value: +"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\"). Pass the ENTITY NAME ONLY — for a bond that is the ISSUER exactly as printed (\"NEW YORK ST DORM AUTH\"), never the question's full noun phrase (\"NEW YORK ST DORM AUTH revenue bonds\"): the FIGI lookup matches instrument names, so trailing security-class words match nothing."

Related MCP Connectors

Related MCP Servers

  • mcp-mempool-space

    pipeworx-io
    A
    license
    Not graded
    quality
    B
    maintenance
    MCP server for Bitcoin block explorer and mempool/fee statistics, providing tools to query fees, mempool stats, blocks, transactions, addresses, hashrate, and mining pools.
    4 npm
    MIT

  • mcp-mempool

    Ethosbtc
    F
    license
    A
    quality
    C
    maintenance
    MCP server for querying live Bitcoin data from mempool.space, including recommended fees, mempool stats, blocks, transactions, addresses, and price. No API key required.
    7
    -
Try in Browser
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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources