Developer · Local MCP server
Nockchain MCP
Moved to io.github.winter0x/nockchain-mcp. This entry is no longer updated.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.mizuki0x/nockchain-mcp- Version
- 0.1.2
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-08-25
- Updated
- 2026-08-25
- Publisher
- mizuki0x (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/mizuki0x) · how
- Listed under
- GitHub MCP servers
- Repository
- github.com/winter0x/nockchain-agent (folder packages/mcp)
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | nockchain-mcp | 0.1.0 | stdio |
How to connect Nockchain MCP
Nockchain MCP runs locally from a Node.js package published to the npm registry: nockchain-mcp version 0.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y nockchain-mcp@0.1.0. It reads these environment variables: NOCKCHAIN_ENDPOINTS, NOCKCHAIN_MAX_STALENESS_SECONDS and NOCKCHAIN_MAX_HEIGHT_LAG; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"nockchain-mcp": {
"command": "npx",
"args": [
"-y",
"nockchain-mcp@0.1.0"
],
"env": {
"NOCKCHAIN_ENDPOINTS": "<value>",
"NOCKCHAIN_MAX_STALENESS_SECONDS": "<value>",
"NOCKCHAIN_MAX_HEIGHT_LAG": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| nlqdb - analytical memory for AI agentsAnalytical memory for AI agents: a real Postgres queried in plain English over MCP. One command. | Remote · HTTPLive check: sign-in required |
| No CrdDynamic pod spawner & proxy for ephemeral AI agent workspaces on Kubernetes without CRDs. | Local · stdio |
| No-Code ExitsNo-code startups for sale, the deal-scoring method behind each pick, and exit stories. | Remote · HTTPLive check: ✓ handshake |
| No-Shell Agent Architect MCPTurns vague automation requests into tool stacks, prompts, QA checks, and human boundaries. | Remote · HTTPLive check: ✓ handshake |
| Node RuntimeThis package is intended for demonstration only. Maintained by JFrog Security. | Local · stdio |
| NodecelVibe deployment for nodecel - deploy, roll back, diagnose, and manage apps and domains from chat. | Remote · HTTPLive check: sign-in required |
| Nodegrove VRAM: can I run it?Can this LLM run on my GPU? VRAM, speed ceiling and what fits instead, for any model and GPU. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| nodriver - undetected browser automationUndetected anti-bot Chrome automation. 70 tools, parallel isolated browsers. | Local · stdio |