# Nist Beacon [Health: Active]

**Category:** 🔑 Cryptography  
**Repository:** https://github.com/pipeworx-io/mcp-nist-beacon  
**GitHub Stars:** 0  
**npm Downloads (last month):** 446  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/nist-beacon

## Description
NIST Randomness Beacon v2 — signed public random pulses every 60s.

## Tools
Capabilities this server exposes over MCP:

- **last_pulse** — Fetch the most recent NIST Randomness Beacon pulse: a publicly verifiable, timestamped 512-bit random value signed by NIST, updated every 60 seconds.
- **pulse_at** — Fetch the NIST Randomness Beacon pulse closest to a given Unix timestamp in milliseconds (time_ms); returns the 512-bit output value and chain/signature metadata.
- **pulse_by_chain_pulse** — Pulse by chain + pulse index.
- **latest_in_chain** — Latest pulse in chain.
- **chain_info** — Chain metadata.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "nist-beacon": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-nist-beacon"]
  }
}
```

## Documentation

## What Nist Beacon does

Nist Beacon provides MCP access to the NIST Randomness Beacon v2. The service publishes signed, timestamped 512-bit random values at 60-second intervals. Agents can retrieve the newest value, locate a pulse near a UTC Unix timestamp in milliseconds, or address a pulse by its chain and pulse identifiers.

The integration is intended for workflows where randomness should be independently verifiable rather than generated privately by an application. Example uses include lottery draws, audit procedures, election seed generation, and fair sampling. Nist Beacon is an independent, unofficial integration and is not affiliated with or endorsed by NIST.

## How it works

The hosted MCP endpoint is served through Pipeworx at `https://gateway.pipeworx.io/nist-beacon/mcp`. Requests are forwarded to the NIST Beacon v2 data source at `https://beacon.nist.gov/beacon/2.0`. A client can connect directly to the hosted endpoint, or run the npm package as a local stdio bridge that forwards requests to the same gateway.

The pack endpoint exposes the Nist Beacon tools and also includes shared Pipeworx meta-tools. The local bridge lists only the pack tools by default; setting `PIPEWORX_META_TOOLS=1` enables the gateway-wide tools as well. The gateway can also route natural-language questions through `ask_pipeworx`.

## Setup and configuration

For an MCP client supporting a hosted endpoint, add the following server URL:

```json
{
  "mcpServers": {
    "nist-beacon": {
      "url": "https://gateway.pipeworx.io/nist-beacon/mcp"
    }
  }
}
```

The npm option starts the local bridge with `npx`:

```json
{
  "mcpServers": {
    "nist-beacon": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-nist-beacon"]
    }
  }
}
```

The bridge needs network access and has no offline mode. Anonymous use is capped at 50 calls per day. A Pipeworx account and `PIPEWORX_API_KEY` raise the allowance to 200 calls per day; the key is sent as a Bearer token. Set `NODE_USE_ENV_PROXY=1` when using an HTTPS proxy with Node versions that support the related environment-proxy behavior.

## Tools and capabilities

- `last_pulse` retrieves the most recent NIST pulse.
- `pulse_at` finds the pulse closest to a supplied Unix timestamp in milliseconds and returns its output plus chain and signature metadata.
- `pulse_by_chain_pulse` retrieves a pulse using a chain ID and pulse ID.
- `latest_in_chain` returns the newest pulse in a selected chain. Chain 1 is the primary chain.
- `chain_info` returns metadata for a chain.

The same operations can be called over HTTP through the gateway's tools API, including `POST /v1/tools/last_pulse`.

## Limitations and notes

Results depend on network access to the Pipeworx gateway and NIST Beacon source. Hosted pack connections include shared gateway meta-tools, so the tool list is larger than the five Nist Beacon-specific tools. The integration is keyless for anonymous calls, but unauthenticated usage has a daily limit. Pipeworx access and usage limits apply to the gateway connection.

_Full upstream README: https://allmcps.com/mcp/nist-beacon/readme_