Skip to main content
Glama
blocklens

blocklens-mcp-server

Official
by blocklens

Related Servers

Alternatives to blocklens-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that tracks Bitcoin's Unspent Transaction Outputs (UTXO) and block statistics, giving AI agents direct access to essential on-chain data.
      2
      2
      MIT
    • 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
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables AI agents to query real-time Bitcoin network intelligence and corporate treasury data, including company holdings and SEC filings. It combines 49 core Bitcoin tools with specialized functions for tracking publicly traded companies and their Bitcoin assets.
      53
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Bitcoin market intelligence MCP server. Exposes Signal Lord's composite gauge scoring, on-chain and macro regime signals, and market data to AI agents.
      26
      14 npm
      1
      MIT

    TDQS

    A3.9/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool has a distinct purpose: discovery (list_metrics, search_metrics, get_metric), specific data categories (prices, supply, valuation, profit, cohort, UTXO, coindays, blockchain, cycle), and visualization (render_chart). Even similar tools like get_cohort_metrics and get_utxo_history are clearly delineated by their descriptions.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern: list_*, get_*, search_*, render_*. No mixed casing or inconsistent verb styles are present.

    Tool Count4/5

    With 15 tools, the server sits at the upper boundary of the typical well-scoped range. Each tool covers a distinct aspect of on-chain data, but the count is slightly high, making it feel a bit heavier than the 3-15 ideal.

    Completeness4/5

    The tool surface comprehensively covers discovery, data retrieval for major on-chain metric families, and charting. A minor gap is the lack of a generic get_metric_data tool to fetch arbitrary historical time series, as specific getters only cover predetermined categories.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues