io.github.winter0x/nockchain-mcp
NPM · NOCKCHAIN-MCP · SCANNED SEP 20
Community-built read-only Nockchain access: balances, payment verification, blocks, node health.
Available components
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
- 42 of 130 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 17 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 729 tokens (~104/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
How do I install the io.github.winter0x/nockchain-mcp server?
io.github.winter0x/nockchain-mcp runs locally as an npm package, launched with npx -y nockchain-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 · nockchain-mcp
claude mcp add winter0x-nockchain-mcp -- npx -y nockchain-mcp
{
"mcpServers": {
"winter0x-nockchain-mcp": {
"command": "npx",
"args": [
"-y",
"nockchain-mcp"
]
}
}
} {
"servers": {
"winter0x-nockchain-mcp": {
"command": "npx",
"args": [
"-y",
"nockchain-mcp"
]
}
}
} codex mcp add winter0x-nockchain-mcp -- npx -y nockchain-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"winter0x-nockchain-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"nockchain-mcp"
],
"enabled": true
}
}
} openclaw mcp add winter0x-nockchain-mcp --command npx --arg -y --arg nockchain-mcp
mcp_servers:
winter0x-nockchain-mcp:
command: "npx"
args: ["-y", "nockchain-mcp"] {
"McpServers": {
"winter0x-nockchain-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"nockchain-mcp"
]
}
}
} assistant mcp add winter0x-nockchain-mcp -t stdio -c npx -a -y nockchain-mcp
{
"mcpServers": {
"winter0x-nockchain-mcp": {
"command": "npx",
"args": [
"-y",
"nockchain-mcp"
]
}
}
} 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.
- 20 Sept 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.
- 17 Sept 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.
- 15 Sept 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.
- 13 Sept 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.
- 11 Sept 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.
- 9 Sept 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.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 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 20 Sept 2026 · Analysed npm/nockchain-mcp@0.1.1
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 130 packages
| Packages resolved | 130 |
|---|---|
| Stale | 42 |
| 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 →
nock_balance Address balance ~118
Spendable balance for a Nockchain address, in nicks and in NOCK, where 1 NOCK is 65536 nicks. The balance is derived from the note first-names behind the address, which is the path that returns a correct figure for v1 notes. The result is the unspent-note set at the current tip, so a note that has already been spent no longer appears and the total is not a record of payments received. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Base58 Nockchain address. |
No output schema declared.
No examples provided.
nock_block Block details ~46
Block contents by height or by block ID, including the transactions the block carries. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| block | string | yes | Block height as a decimal number, or a block ID. |
No output schema declared.
No examples provided.
nock_endpoints Endpoint health ~68
Health table for every endpoint in the pool: reported height, seconds since that endpoint last refreshed its chain state, round-trip latency, and whether it was rejected for being stale or behind. Public nodes do go stale, so check here before trusting a reading. Takes no arguments. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
nock_metrics Chain metrics ~43
State of the endpoint currently selected by the pool: cache coverage and refresh ages under explorer, and one row per connected peer under peers. Takes no arguments. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
nock_tip Chain tip ~35
Current Nockchain tip height, together with a freshness reading for every endpoint in the pool. Takes no arguments. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
nock_transaction Transaction details ~73
Transaction contents by transaction ID. The upstream node fails to decode transactions produced after the Logos upgrade. When that happens this tool returns reason "upstream_decoder_bug" along with the inclusion facts that could still be established, such as the block height and timestamp. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| txId | string | yes | Transaction ID. |
No output schema declared.
No examples provided.
nock_verify_payment Verify payment ~257
Check whether an address has received at least a given amount, counting only notes that are buried under enough confirmations. Payments carry no memo or tag on the wire, so correlate them by issuing one address per invoice. The check reads the unspent-note set, so a payment that arrived and has since been spent will not be counted. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Base58 Nockchain address that should have received the payment. |
| confirmations | integer | – | How many blocks a note must be buried under before it counts. Defaults to 3. |
| minNicks | string | – | Minimum amount in nicks as a whole-number string above zero. Supply this or minNock. |
| minNock | string | – | Minimum amount in NOCK as a decimal string above zero, for example "0.25". An amount finer than one nick is rejected. Supply this or minNicks. |
| sinceHeight | integer | – | Only count notes created above this block height. |
| sinceTime | string | – | ISO 8601 timestamp. Only count notes created at or after this moment. A note is dated by the block that carries it, so the cutoff lands on the first block at or after the timestamp. |
No output schema declared.
No examples provided.
What is the io.github.winter0x/nockchain-mcp server?
io.github.winter0x/nockchain-mcp is listed in the public MCP registry as io.github.winter0x/nockchain-mcp. Community-built read-only Nockchain access: balances, payment verification, blocks, node health. This page covers its npm package (nockchain-mcp).
Is the io.github.winter0x/nockchain-mcp server safe to use?
io.github.winter0x/nockchain-mcp scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 io.github.winter0x/nockchain-mcp server expose?
io.github.winter0x/nockchain-mcp exposes 7 tools: nock_tip, nock_balance, nock_verify_payment, nock_block, nock_transaction, and 2 more. Their descriptions and schemas cost roughly 640 tokens of context every time the server is loaded.
Is the io.github.winter0x/nockchain-mcp server still maintained?
io.github.winter0x/nockchain-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.winter0x/nockchain-mcp server under?
io.github.winter0x/nockchain-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.