io.github.CloudCorpRecords/poworacle

Official registry Other

Proof-of-work mining oracle: solo-mining odds, cost of production, network state, hardware, news.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @reneturcios/poworacle
Claude Code
claude mcp add poworacle -- npx -y @reneturcios/poworacle@0.1.0 mcp
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "poworacle": {
            "command": "npx",
            "args": [
                "-y",
                "@reneturcios/poworacle@0.1.0",
                "mcp"
            ]
        }
    }
}
OCI package ghcr.io/cloudcorprecords/poworacle:0.1.0
Claude Code
claude mcp add poworacle -- docker run -i --rm ghcr.io/cloudcorprecords/poworacle:0.1.0 mcp
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "poworacle": {
            "command": "docker",
            "args": [
                "run",
                "-i",
                "--rm",
                "ghcr.io/cloudcorprecords/poworacle:0.1.0",
                "mcp"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. poworacle
  2. Tools
  3. CLI
  4. MCP
  5. Docker
  6. Development
  7. License

poworacle

Live proof-of-work mining data as MCP tools: how long a solo miner would wait for a block, what it costs to produce one coin, the current state of a network, which hardware earns what, and recent mining news.

poworacle is a keyless forwarding client. It serves six tools over stdio MCP (and as CLI subcommands) and forwards each call to the public BackPow MCP endpoint at https://mcp.backpow.com/mcp — no API key, no account, nothing to configure. The upstream server is stateless, so each call is a single Streamable HTTP POST carrying a tools/call JSON-RPC request; the upstream result's content is returned verbatim. Upstream JSON-RPC errors come back as backpow error: <message>, an unparseable response as backpow error: malformed response, and a transport failure (including a timeout) as backpow unreachable.

Two environment variables adjust the client (both are this rebuild's own knobs, not upstream requirements):

VariableDefaultPurpose
BACKPOW_MCP_URLhttps://mcp.backpow.com/mcpEndpoint override
BACKPOW_TIMEOUT_MS30000Per-call timeout, AbortController-enforced

Tools

ToolAnswers
calculate_solo_mining_oddsMean time to a block and Poisson odds over 1/7/30/90/365 days for a given coin and hashrate, plus the electricity cost of the attempt
get_cost_of_productionAll-in electricity cost of mining one unit on the most efficient tracked hardware, against spot price and margin
get_coin_oracleLive difficulty, hashrate, block height and reward for one chain, with a measurement-confidence block
list_pow_coinsPaginated catalogue of tracked PoW networks, filterable by algorithm or profitability
get_hardware_benchmarksHardware matched to the coins it can mine, ranked by net USD per day at a given electricity rate
get_pow_newsRecent PoW mining and network news, optionally filtered to one coin

Ambiguity and missing measurements are refused upstream rather than guessed or substituted, and those errors pass through unchanged apart from the backpow error: rendering.

CLI

npx @reneturcios/poworacle get_coin_oracle '{"coin_id":"Kaspa"}'
npx @reneturcios/poworacle calculate_solo_mining_odds '{"coin_id":"Bitcoin","hashrate":100,"hashrate_unit":"TH/s"}'
npx @reneturcios/poworacle list_pow_coins '{"algorithm":"SHA-256"}'
npx @reneturcios/poworacle --version

Each tool subcommand takes one JSON argument string. Exit codes: 0 on success, 1 when the tool result is an error, 2 on a usage error (unknown command, extra arguments, or a non-object JSON argument).

MCP

npx @reneturcios/poworacle mcp

MCP client configuration:

{
  "mcpServers": {
    "poworacle": {
      "command": "npx",
      "args": ["-y", "@reneturcios/poworacle", "mcp"]
    }
  }
}

Docker

docker run -i ghcr.io/cloudcorprecords/poworacle          # stdio MCP server (CMD defaults to "mcp")
docker run --rm ghcr.io/cloudcorprecords/poworacle get_pow_news '{"coin_id":"Bitcoin"}'

Development

npm install
npm run build      # tsc -> dist/ (dist/cli.js is the bin)
npm test           # tsx --test test/*.test.ts (fake fetch only, no network)
npm run dev        # tsx src/cli.ts — run the CLI from source

License

MIT — see LICENSE.

Frequently asked questions

What is io.github.CloudCorpRecords/poworacle?

Proof-of-work mining oracle: solo-mining odds, cost of production, network state, hardware, news.

How do I install io.github.CloudCorpRecords/poworacle?

It runs on your machine. In Claude Code: claude mcp add poworacle -- npx -y @reneturcios/poworacle@0.1.0 mcp. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.CloudCorpRecords/poworacle need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is io.github.CloudCorpRecords/poworacle open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.github.CloudCorpRecords/poworacle?

It is published by CloudCorpRecords. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.