Skip to content
BTC Power Law logo

BTC Power Law MCP server

Which MCP servers are BTC Power Law's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-28

← Back to BTC Power Law

Whose server it is
  • Registry nameio.btclaw/power-lawverified in the MCP registry

The registry name sits under btclaw.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-28
  • Stateanswerschecked 2026-10-28
  • Tools4
  • Server calls itselfbtclaw
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 467 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: check whether bitcoin trades above or below its power law fair value; estimate when bitcoin might reach a target price.
  • Checked on 5 of the 7 days it takes to judge reliability.

Once connected

  • For "check whether bitcoin trades above or below its power law fair value", the likely first call is get_power_law_status.
  • For "estimate when bitcoin might reach a target price", the likely first call is when_will_bitcoin_reach.
  • Parameters are untyped or undescribed in 2 of 4 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 5, the first on 2026-10-28
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
  • What an agent can do with it2 of 2 use cases
  • Answeredmeasuring5 of the 7 daily checks it takes to print a share
  • Median first answer487 ms
  • Space in an agent's context≈ 337 tokensthe definitions of all its tools (4), which an agent carries on every turn
  • Tool definitionsA · 92 of 100
  • Typed results0 of 4 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 2 of 4

What an agent can do with it

  • can do · check whether bitcoin trades above or below its power law fair value
  • not sure · project a monthly bitcoin savings plan against the trend model
  • can do · estimate when bitcoin might reach a target price

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers4 tools · read 2026-10-28
  • get_power_law_status

    Where Bitcoin is against its power-law trend right now: live price, trend (fair) value, % deviation, zone, lower and upper band, the fit used and the next halving.

  • get_trend_on_date

    Power-law trend (fair) value and the lower/upper band on a date, past or future. `date` is YYYY-MM-DD (UTC), between 2010-07-18 and 2100-12-31.

  • when_will_bitcoin_reach

    When the power-law trend reaches a Bitcoin price, plus the earliest date (upper band, 3x trend: a historical ceiling that recent peaks stayed well below) and the date after which even the lower band (0.4x) stays above it.

  • explain_power_law_model

    Background on the Bitcoin power-law model: the formula, how it is fitted, the bands, its limits, and the paper.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "power-law": {
      "type": "http",
      "url": "https://btclaw.io/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http btclaw https://btclaw.io/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://btclaw.io/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.