Skip to main content
Glama
Ethosbtc

mcp-mempool

by Ethosbtc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to mcp-mempool

No user-submitted related servers found.

    Related Servers

    • mcp-mempool-space

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      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.
      1 npm
      MIT

    • MCP Mempool

      jaducku
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides AI agents with real-time and historical Bitcoin network data by wrapping the mempool.space WebSocket and REST APIs. It enables tracking addresses, monitoring blocks, and retrieving transaction details or fee estimates through natural language.
      MIT

    • @bitcoinbenji/mcp

      ocbenji
      A
      license
      B
      quality
      C
      maintenance
      MCP 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.
      26
      7 npm
      1
      MIT

    • Bitcoin Node MCP Server

      andy-builds-ai
      A
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server that monitors a Bitcoin Core full node via JSON-RPC, providing tools to check node status, network info, mempool, and peer information.
      MIT

    • mcp-l402-gate-example

      zekebuilds-lab
      A
      license
      Not graded
      quality
      D
      maintenance
      Minimal MCP server demonstrating L402 pay-per-call with Depth-of-Identity reputation gating, providing a bitcoin data tool that fetches BTC price and mempool fees.
      MIT
    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

    A4.4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct data resource: fees, mempool stats, chain tip, recent blocks, a specific transaction, an address, and price. No two tools overlap in purpose, making selection unambiguous.

    Naming Consistency5/5

    All tools follow a consistent 'get_' verb + noun pattern (get_recommended_fees, get_mempool_stats, get_tip, get_recent_blocks, get_transaction, get_address, get_price). The naming scheme is uniform and predictable.

    Tool Count5/5

    Seven tools is well-scoped for a mempool/blockchain information server. Each tool addresses a common need without redundancy, and the count is within the ideal 3-15 range.

    Completeness4/5

    The server covers fees, mempool state, chain tip, recent blocks, transactions, addresses, and price—covering the primary read-only use cases. A notable minor gap is the lack of a way to fetch a specific block by height or hash, but this is not critical for typical mempool queries.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources