# Startmining Bitcoin Mining Data (npm · @startminingmcp/mcp)

Bitcoin mining data from a self-hosted node: hashprice, profitability, weekly/monthly stats, history

- Trust score: 82/100 (high trust)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@startminingmcp/mcp`: 82/100 (this document), [markdown](https://verifymcp.io/servers/tibsp-startmining-mcp/startminingmcp-mcp.md), [page](https://verifymcp.io/servers/tibsp-startmining-mcp/startminingmcp-mcp)

## Channel facts

- Registry: `npm`
- Package: `@startminingmcp/mcp`
- Version: `1.2.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 27 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 708 tokens (~54/item across 13 items; 13 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Startmining Bitcoin Mining Data MCP server?

Startmining Bitcoin Mining Data runs locally as an npm package, launched with npx -y @startminingmcp/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add tibsp-startmining-mcp -- npx -y @startminingmcp/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "tibsp-startmining-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@startminingmcp/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tibsp-startmining-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@startminingmcp/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add tibsp-startmining-mcp -- npx -y @startminingmcp/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tibsp-startmining-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@startminingmcp/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tibsp-startmining-mcp --command npx --arg -y --arg @startminingmcp/mcp
```

### Hermes

```yaml
mcp_servers:
  tibsp-startmining-mcp:
    command: "npx"
    args: ["-y", "@startminingmcp/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "tibsp-startmining-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@startminingmcp/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add tibsp-startmining-mcp -t stdio -c npx -a -y @startminingmcp/mcp
```

### Other

```json
{
  "mcpServers": {
    "tibsp-startmining-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@startminingmcp/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-31 (score 82, +1)

- [security] Stability: 0.97 → pass

### 2026-10-29 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-18 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-16 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (13)

### `get_market_data` (~28 tokens)

Get current Bitcoin market and mining data including price, hashprice, difficulty, and network stats

### `get_hashprice` (~25 tokens)

Get current hashprice (mining revenue per PH/day) with detailed breakdown

### `get_difficulty` (~17 tokens)

Get current difficulty and next adjustment prediction

### `get_halving_info` (~27 tokens)

Get Bitcoin halving information - current era, next halving date, supply stats

### `get_price_history` (~67 tokens)

Get historical Bitcoin prices

Input parameters:

- `from` (string): Start date (YYYY-MM-DD)
- `granularity` (string): Data granularity (default: day). For calendar-month averages use get_monthly_averages
- `to` (string): End date (YYYY-MM-DD)

### `get_difficulty_history` (~45 tokens)

Get historical difficulty and hashrate data

Input parameters:

- `from` (string): Start date (YYYY-MM-DD)
- `to` (string): End date (YYYY-MM-DD)

### `calculate_profitability` (~116 tokens)

Calculate mining profitability for given hashrate and electricity cost

Input parameters:

- `btc_price` (number): BTC price (optional, uses current if not provided)
- `days` (number): Number of days to calculate (default: 30)
- `electricity_cost` (number, required): Electricity cost in $/kWh
- `hashrate_th` (number, required): Hashrate in TH/s
- `pool_fee_pct` (number): Pool fee percentage (default: 2)
- `power_watts` (number, required): Power consumption in watts

### `calculate_breakeven` (~64 tokens)

Calculate breakeven BTC price for mining operation

Input parameters:

- `electricity_cost` (number, required): Electricity cost in $/kWh
- `hashrate_th` (number, required): Hashrate in TH/s
- `power_watts` (number, required): Power consumption in watts

### `get_mempool` (~18 tokens)

Get mempool status and fee estimates

### `get_recent_blocks` (~64 tokens)

Get the most recent Bitcoin blocks (max 50, i.e. a few hours). For weekly block time, fees or hashprice use get_weekly_stats

Input parameters:

- `limit` (number): Number of blocks to return (default: 10, max: 50)

### `get_monthly_averages` (~77 tokens)

Get calendar-month averages (UTC) of BTC price, network hashrate, and hashprice in USD and BTC, for monthly mining reports. The month must be complete.

Input parameters:

- `month` (string, required): Calendar month (YYYY-MM), e.g. 2026-09 for 1-30 September 2026

### `get_weekly_stats` (~141 tokens)

Get closed ISO-week (Monday 00:00 UTC to Monday 00:00 UTC) Bitcoin network stats for weekly mining reports: block count and average block time, real transaction fees, implied hashrate, real hashprice in BTC and USD, difficulty adjustments with timestamps, BTC price, raw daily rows, methodology and coverage. Defaults to the last 2 closed weeks.

Input parameters:

- `week` (string): Any day (YYYY-MM-DD) of the most recent week wanted. Default: last fully closed week
- `weeks` (number): Number of consecutive weeks ending with `week`, oldest first (default: 2, max: 8)

### `get_asic_prices` (~19 tokens)

Get ASIC miner price data and efficiency stats

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/tibsp-startmining-mcp/startminingmcp-mcp#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 82
- 2026-10-30: 81
- 2026-10-29: 81
- 2026-10-28: 80
- 2026-10-27: 80
- 2026-10-26: 79
- 2026-10-25: 79
- 2026-10-24: 79
- 2026-10-23: 78
- 2026-10-22: 78
- 2026-10-21: 77
- 2026-10-20: 77
- 2026-10-19: 76
- 2026-10-18: 76
- 2026-10-17: 75
- 2026-10-16: 75
- 2026-10-15: 74
- 2026-10-14: 74
- 2026-10-13: 38
- 2026-10-12: 38
- 2026-10-09: 23
- 2026-10-05: 67
- 2026-10-04: 67
- 2026-10-03: 67
- 2026-10-02: 67

## Common questions

### What is the Startmining Bitcoin Mining Data MCP server?

Startmining Bitcoin Mining Data is an MCP server listed in the public MCP registry as io.github.TIBSP/startmining-mcp. Bitcoin mining data from a self-hosted node: hashprice, profitability, weekly/monthly stats, history. This page covers its npm package (@startminingmcp/mcp).

### Is the Startmining Bitcoin Mining Data MCP server safe to use?

Startmining Bitcoin Mining Data scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Startmining Bitcoin Mining Data MCP server expose?

Startmining Bitcoin Mining Data exposes 13 tools: get_market_data, get_hashprice, get_difficulty, get_halving_info, get_price_history, and 8 more. Their descriptions and schemas cost roughly 708 tokens of context every time the server is loaded.

### Is the Startmining Bitcoin Mining Data MCP server still maintained?

Startmining Bitcoin Mining Data is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Startmining Bitcoin Mining Data MCP server under?

Startmining Bitcoin Mining Data declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@startminingmcp/mcp
- Socket report: https://socket.dev/npm/package/@startminingmcp/mcp
- Repository: https://github.com/TIBSP/startmining-mcp
- Website: https://pro.startmining.io/
- Changelog RSS feed: https://verifymcp.io/servers/tibsp-startmining-mcp/startminingmcp-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/tibsp-startmining-mcp/startminingmcp-mcp.json
- HTML version of this page: https://verifymcp.io/servers/tibsp-startmining-mcp/startminingmcp-mcp