
Nockchain Mcp
io.github.winter0xPublished by GitHub account winter0xv0.1.1Updated Oct 25, 2026
Community-built read-only Nockchain access: balances, payment verification, blocks, node health.
Overview
Read-only Nockchain access for an assistant: check balances, verify payments, inspect blocks and node health.
- What you can do
- Query Nockchain data in read-only mode: look up balances and verify payments against the chain. Inspect blocks and chain state. Check node health and endpoint status. Endpoint selection can be tuned through environment variables that set the endpoint pool, maximum height lag and maximum staleness.
- When to use it
- Useful when you want an assistant to answer questions about Nockchain balances, payment confirmations, blocks or node health without giving it write access. Suited to monitoring and verification tasks rather than transactions.
- Requirements
- Runs locally over stdio via npx from the npm package nockchain-mcp, so Node.js is needed. No authentication is declared. Optional environment variables NOCKCHAIN_ENDPOINTS, NOCKCHAIN_MAX_HEIGHT_LAG and NOCKCHAIN_MAX_STALENESS_SECONDS tune the endpoint pool and freshness checks; network access to Nockchain endpoints is required.
Installation
In SourceWeft
- Open Nockchain Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.