Skip to main content
ClaudeWave
winter0x avatar
winter0x

nockchain-agent

Ver en GitHub

Typed Nockchain client and MCP server for agents. Built by Prism. Resolves balances the public address selector misses, and refuses to answer from stale nodes.

MCP ServersRegistry oficial0 estrellas0 forksTypeScriptApache-2.0Actualizado today
ClaudeWave Trust Score
87/100
Trusted
Passed
  • Open-source license (Apache-2.0)
  • Actively maintained (<30d)
  • Clear description
  • Documented (README)
Last scanned: 8/26/2026
Install in Claude Code / Claude Desktop
Method: NPX · nockchain-mcp
Claude Code CLI
claude mcp add nockchain-agent -- npx -y nockchain-mcp
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "nockchain-agent": {
      "command": "npx",
      "args": ["-y", "nockchain-mcp"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
Casos de uso

Resumen de MCP Servers

# nockchain-agent

A typed TypeScript client and an MCP server for reading Nockchain from an agent.

Built by Prism. Not affiliated with, endorsed by, or operated by Nockchain, Nock Community Co, Zorp, or National Compute.

## Install

```sh
npm install nockchain-agent-sdk
```

The MCP server runs straight from npm:

```sh
npx nockchain-mcp
```

Node 20 or newer.

## Read a balance

```js
import { NockchainClient } from "nockchain-agent-sdk";

const client = new NockchainClient();
const balance = await client.getBalance("2s3K...");

console.log(`${balance.nock} NOCK (${balance.nicks} nicks) across ${balance.notes.length} notes`);
```

## Verify a payment

Issue one address per invoice, then ask whether it has been paid:

```js
import { NockchainClient } from "nockchain-agent-sdk";

const client = new NockchainClient();
const result = await client.verifyPayment({
  address: invoiceAddress,
  minNock: "1.5",
  sinceHeight: 133400,
  confirmations: 3,
});

if (result.paid) {
  console.log(`${result.confirmedNock} NOCK settled at height ${result.tipHeight}`);
}
```

## Use it from an MCP client

```json
{
  "mcpServers": {
    "nockchain": {
      "command": "npx",
      "args": ["-y", "nockchain-mcp"]
    }
  }
}
```

Seven tools, all read-only:

| tool | what it answers |
| --- | --- |
| `nock_tip` | current height, with a freshness reading per endpoint |
| `nock_balance` | what an address can spend right now |
| `nock_verify_payment` | has this address been paid, with confirmations |
| `nock_block` | block contents by height or block ID |
| `nock_transaction` | transaction contents, or why the node could not decode them |
| `nock_metrics` | cache and refresh state of the selected endpoint, and its peer table |
| `nock_endpoints` | the full endpoint health table |

## Why this exists

Two things about reading Nockchain today cost more time than they should.

**Balances come back as zero.** The public `WalletGetBalance` call accepts an address selector, and for notes in the current v1 format that selector returns nothing at all. The balance lives under the note first-name, which you reach by hashing the pay-to-pubkey-hash behind the address. Two derivations matter, because coinbase notes lock differently from ordinary ones, and the real balance is the union of both. `getBalance` does that work and returns the figure the address can actually spend.

**Public nodes go stale quietly.** Three endpoints, measured within the same minute on 2026-08-25:

| endpoint | height | age of its chain state |
| --- | --- | --- |
| `api.nockscan.net:443` | 133598 | 157 s |
| `23.252.122.18:5556` | 133598 | 214 s |
| `rpc.nockbox.org:443` | 133226 | 50625 s, close to 14 hours |

A response carries no sign of which of these answered it. The client probes every endpoint in its pool and declines to read from one that fails the freshness threshold, raising a typed error that names the ages it measured. `client.health()` returns the whole table.

## Limitations

**Read-only.** No signing library for Nockchain exists, so sending NOCK needs the official `nockchain-wallet` CLI. The SDK will submit a transaction the CLI has already produced. It will not build or sign one.

**A balance is the live unspent-note set.** It answers what an address can spend at the current tip. A spent note leaves the set, so the total is no record of what an address has received over its lifetime. Nothing the wallet sends carries a memo or a tag on the wire either, which is why payment correlation works by issuing one address per invoice.

**Upstream `GetTransactionDetails` fails on transactions produced after the Logos upgrade.** The node answers with a decoder error instead of the transaction. `getTransactionDetails` catches that case and returns `{ ok: false, reason: "upstream_decoder_bug", txId, fallback }`, where `fallback` carries the inclusion facts that `GetTransactionBlock` and `GetBlockDetails` could still establish, such as the block height and its timestamp.

**The public API is alpha and unauthenticated.** There is no key to obtain and no rate limit to plan against. Endpoints move and lag without notice.

## Packages

| package | contents |
| --- | --- |
| [`nockchain-agent-sdk`](packages/sdk) | the client and the note first-name derivation it depends on |
| [`nockchain-mcp`](packages/mcp) | the stdio MCP server built on it |

## Examples

The examples import the workspace build, so build it once first.

```sh
npm install
npm run build
node examples/balance.mjs 2s3K...
node examples/verify-payment.mjs 2s3K... 1.5
```

Both read the public network.

## Development

```sh
npm install
npm run build
npm test
```

Tests run offline against fixtures, including the golden vectors generated from the upstream Rust crates. Nothing in the test suite opens a socket.

## License

Apache-2.0. See [LICENSE](LICENSE) and [NOTICE](NOTICE).

Lo que la gente pregunta sobre nockchain-agent

¿Qué es winter0x/nockchain-agent?

+

winter0x/nockchain-agent es mcp servers para el ecosistema de Claude AI. Typed Nockchain client and MCP server for agents. Built by Prism. Resolves balances the public address selector misses, and refuses to answer from stale nodes. Tiene 0 estrellas en GitHub y su última actualización registrada es del 2026-08-25.

¿Cómo se instala nockchain-agent?

+

Puedes instalar nockchain-agent clonando el repositorio (https://github.com/winter0x/nockchain-agent) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.

¿Es seguro usar winter0x/nockchain-agent?

+

Nuestro agente de seguridad ha analizado winter0x/nockchain-agent y le ha asignado un Trust Score de 87/100 (tier: Trusted). Revisa el desglose completo de comprobaciones superadas y flags en esta página.

¿Quién mantiene winter0x/nockchain-agent?

+

winter0x/nockchain-agent es mantenido por winter0x. La última actividad registrada en GitHub es del 2026-08-25, con 0 issues abiertos.

¿Hay alternativas a nockchain-agent?

+

Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.

Despliega nockchain-agent en tu cloud

Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.

¿Mantienes este repo? Añade un badge a tu README

Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.

Featured on ClaudeWave: winter0x/nockchain-agent
[![Featured on ClaudeWave](https://claudewave.com/api/badge/winter0x-nockchain-agent)](https://claudewave.com/repo/winter0x-nockchain-agent)
<a href="https://claudewave.com/repo/winter0x-nockchain-agent"><img src="https://claudewave.com/api/badge/winter0x-nockchain-agent" alt="Featured on ClaudeWave: winter0x/nockchain-agent" width="320" height="64" /></a>

Más MCP Servers

Alternativas a nockchain-agent