Startmining Bitcoin Mining Data
NPM · @STARTMININGMCP/MCP
Bitcoin mining data from a self-hosted node: hashprice, profitability, weekly/monthly stats, history
Available components
Last scanned (4 hours ago)
Scores higher than 72% of npm servers
Category Crypto and Web3
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 27 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 708 tokens (~54/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 31 Oct 26 +1
- Stability: 0.97 → pass security
- 29 Oct 26 +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.
- 27 Oct 26 +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.
- 24 Oct 26 +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.
- 22 Oct 26 +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.
- 20 Oct 26 +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.
- 18 Oct 26 +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.
- 16 Oct 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@startminingmcp/mcp@1.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
calculate_breakeven ~64
Calculate breakeven BTC price for mining operation
| Name | Type | Req | Description |
|---|---|---|---|
| electricity_cost | number | yes | Electricity cost in $/kWh |
| hashrate_th | number | yes | Hashrate in TH/s |
| power_watts | number | yes | Power consumption in watts |
No output schema declared.
No examples provided.
calculate_profitability ~116
Calculate mining profitability for given hashrate and electricity cost
| Name | Type | Req | Description |
|---|---|---|---|
| btc_price | number | – | BTC price (optional, uses current if not provided) |
| days | number | – | Number of days to calculate (default: 30) |
| electricity_cost | number | yes | Electricity cost in $/kWh |
| hashrate_th | number | yes | Hashrate in TH/s |
| pool_fee_pct | number | – | Pool fee percentage (default: 2) |
| power_watts | number | yes | Power consumption in watts |
No output schema declared.
No examples provided.
get_asic_prices ~19
Get ASIC miner price data and efficiency stats
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_difficulty ~17
Get current difficulty and next adjustment prediction
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_difficulty_history ~45
Get historical difficulty and hashrate data
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Start date (YYYY-MM-DD) |
| to | string | – | End date (YYYY-MM-DD) |
No output schema declared.
No examples provided.
get_halving_info ~27
Get Bitcoin halving information - current era, next halving date, supply stats
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_hashprice ~25
Get current hashprice (mining revenue per PH/day) with detailed breakdown
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_market_data ~28
Get current Bitcoin market and mining data including price, hashprice, difficulty, and network stats
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_mempool ~18
Get mempool status and fee estimates
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_monthly_averages ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| month | string | yes | Calendar month (YYYY-MM), e.g. 2026-09 for 1-30 September 2026 |
No output schema declared.
No examples provided.
get_price_history ~67
Get historical Bitcoin prices
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
get_recent_blocks ~64
Get the most recent Bitcoin blocks (max 50, i.e. a few hours). For weekly block time, fees or hashprice use get_weekly_stats
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Number of blocks to return (default: 10, max: 50) |
No output schema declared.
No examples provided.
get_weekly_stats ~141
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
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.
npm · @startminingmcp/mcp
claude mcp add tibsp-startmining-mcp -- npx -y @startminingmcp/mcp
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.