Mempool Space
Server Details
mempool.space MCP — Bitcoin block explorer + mempool/fee stats
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
- 36.9% over 37 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-mempool-space
- GitHub Stars
- 0
- Server Listing
- mcp-mempool-space
TDQS
Scored across 41 tools
The set is deeply confusing due to massive overlap: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all serve similar meta-purposes. Furthermore, the core purpose appears to be a Bitcoin mempool explorer (block_height, get_address, mempool_stats, etc.), but it is overlaid with a huge general-purpose data routing layer (Pipeworx) whose tools (entity_profile, compare_entities, recent_changes, etc.) are completely unrelated to the server name. An agent cannot reliably select the correct tool for a given intent.
Naming conventions are inconsistent across the two domains. Blockchain tools use snake_case (block_height, get_address) and sometimes omit the get_ prefix inconsistently (block_height vs get_block). Pipeworx meta-tools mix prefixes (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools) and include unusual patterns like pipeworx_feedback, pipeworx_trending. There is no single predictable verb_noun pattern.
41 tools is too many for a server ostensibly focused on the Bitcoin mempool. The large majority of tools belong to a different domain (financial/economic data) and are not cohesive with the blockchain tools, making the set unwieldy and difficult to navigate.
For the Bitcoin mempool domain, the tool set covers core operations (address lookup, transactions, blocks, mempool stats, fees, hashrate, mining pools), but it is missing write/broadcast capabilities (e.g., submit transaction, estimate fee). However, because the server also bundles a vast unrelated data-routing layer, assessing overall completeness against a single domain is impossible; the set is uneven and lacks coherence.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
entity_profile3 fields changed- changed
Input schema / properties / type / descriptionPrevious 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." - changed
Input schema / properties / type / enumPrevious value: -[ - "company" -]New value: +[ + "company", + "ticker" +] - changed
Input schema / properties / value / descriptionPrevious 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."
1 tool update
- Changed
resolve_entity1 field changed- changed
Input schema / properties / value / descriptionPrevious 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
DEX Screener MCP — DEX price/liquidity/volume data
Solscan MCP — Solana block-explorer API (Pro v2)
Crypto market data & research MCP: price, derivatives, on-chain, sentiment, news, catalysts.
Related MCP Servers
- FlicenseAqualityCmaintenanceMCP server for querying live Bitcoin data from mempool.space, including recommended fees, mempool stats, blocks, transactions, addresses, and price. No API key required.7-
- AlicenseBqualityCmaintenanceMCP server offering 26 Lightning-paid tools for Bitcoin mempool intelligence and sovereign on-prem AI inference, with no third-party APIs and pay-per-call in sats.267 npm1MIT
- AlicenseAqualityCmaintenanceThe first MCP Server dedicated to Bitcoin ecosystem236MIT
- AlicenseBqualityBmaintenanceProvides live Bitcoin network data (fees, mempool, hashrate) and AI-powered price/fee forecasts via MCP tools, with free access to basic data and pay-per-call for advanced features.1755 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.