# Pulse Verity (npm · @pipeworx/mcp-pulse-verity)

Pulse Verity — crypto index prices that come with a PROOF.

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-pulse-verity/pulse-verity-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-pulse-verity/pulse-verity-mcp)
- npm · `@pipeworx/mcp-pulse-verity`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-pulse-verity/pipeworx-mcp-pulse-verity.md), [page](https://verifymcp.io/servers/pipeworx-io-pulse-verity/pipeworx-mcp-pulse-verity)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-pulse-verity`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-pulse-verity).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1540 tokens (~256/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Pulse Verity MCP server?

Pulse Verity runs locally as an npm package, launched with npx -y @pipeworx/mcp-pulse-verity. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-pulse-verity -- npx -y @pipeworx/mcp-pulse-verity
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-pulse-verity": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-pulse-verity"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-pulse-verity": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-pulse-verity"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-pulse-verity -- npx -y @pipeworx/mcp-pulse-verity
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-pulse-verity": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-pulse-verity"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-pulse-verity --command npx --arg -y --arg @pipeworx/mcp-pulse-verity
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-pulse-verity:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-pulse-verity"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-pulse-verity": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-pulse-verity"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-pulse-verity -t stdio -c npx -a -y @pipeworx/mcp-pulse-verity
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-pulse-verity": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-pulse-verity"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 82, +3)

- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional improvement] Stability: unverified → 0.20
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-03 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-02 (score 79, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (6)

### `pulse_signed_price` (~242 tokens)

The current CRYPTOGRAPHICALLY SIGNED index price for one crypto asset, from the Pulse Verity Index across thousands of assets and dozens of venues — this result carries a signature you can verify: pass it unchanged to pulse_verify_print to check it OFFLINE, with no network call, against Pulse's public key. Each print carries signature, kid, grade, the number of independent venues (sources), dispersion in basis points and a confidence interval. Grades: consensus (3+ venues) and blended (2) are settleable; indicative (1 venue) is NOT. Use it when a price has to be defensible — settlement, an audit trail, a dispute — not merely current. Requires a Pulse API key via _apiKey. Example: pulse_signed_price({ symbol: "BTC" }).

Input parameters:

- `_apiKey` (string): Pulse Verity API key. Free and self-serve at https://thepulse.markets/developers (60 req/min, 25,000/month, no card).
- `symbol` (string, required): Asset ticker as Pulse spells it, e.g. BTC, ETH, SOL. pulse_asset_catalog lists coverage.

### `pulse_signed_batch` (~196 tokens)

Signed index prices for up to 100 crypto assets in ONE call — each row carries its own signature you can verify individually with pulse_verify_print, offline, with no network call, not just the batch as a whole. Use this instead of looping pulse_signed_price: it is one request against the rate limit and every observation still carries its own signature, grade, venue count and interval. Symbols Pulse does not serve come back named in not_served rather than silently missing. Requires a Pulse API key via _apiKey. Example: pulse_signed_batch({ symbols: ["BTC", "ETH", "SOL"] }).

Input parameters:

- `_apiKey` (string): Pulse Verity API key. Free and self-serve at https://thepulse.markets/developers (60 req/min, 25,000/month, no card).
- `symbols` (array, required): Up to 100 tickers. A comma-separated string is also accepted.

### `pulse_settlement_print` (~252 tokens)

The signed index print Pulse RECORDED nearest a past moment — the tool for settling a contract, pricing an option at expiry, or reconstructing what an asset was worth at a specific timestamp. Returns the observation with its original signature intact — verify it offline with pulse_verify_print, no network call — plus delta_ms, the distance between the time you asked for and the print actually returned; it is the nearest recorded print, never a price synthesised at your exact instant. Accepts ISO-8601 or epoch milliseconds. Requires a Pulse API key via _apiKey. Example: pulse_settlement_print({ symbol: "BTC", at: "2026-09-16T21:41:46.000Z" }).

Input parameters:

- `_apiKey` (string): Pulse Verity API key. Free and self-serve at https://thepulse.markets/developers (60 req/min, 25,000/month, no card).
- `at` (string, required): The moment to price, as ISO-8601 (2026-09-16T21:41:46.000Z) or epoch milliseconds.
- `symbol` (string, required): Asset ticker, e.g. BTC.

### `pulse_verify_print` (~444 tokens)

Check whether a Pulse signed price print is authentic and unaltered — pass a print back exactly as a Pulse tool returned it and this recomputes the ECDSA P-256 / SHA-256 signature over the canonical string, entirely OFFLINE with no network call to Pulse. WHAT A valid:true RESULT PROVES: that Pulse asserted this exact price, for this symbol, at this timestamp, at this grade, and that nobody altered any of those fields in transit — it detects a single changed digit of price or a one-millisecond shift in the timestamp. WHAT IT DOES NOT PROVE: that the price is CORRECT or reflects the true market — this checks Pulse's signature, not the world, so a print can verify perfectly and still be a price Pulse itself got wrong. The verification is computed here, not asked of Pulse, so Pulse cannot vouch for a print it never signed and an offline or compromised source cannot turn an invalid print into a valid one. Needs NO API key. Example: pulse_verify_print({ symbol: "BTC", priceText: "76051.0676303142", price: 76051.0676303142, at: "2026-09-16T23:39:30.524Z", grade: "consensus", signature: "wiD005d9...", kid: "pvi-Sl40p5Gj2t_-JyKUhxyg" }).

Input parameters:

- `at` (string, required): From the print, unchanged. A 1ms difference invalidates the signature.
- `grade` (string, required): From the print: consensus, blended or indicative.
- `kid` (string): Key id from the print; selects which public key to check against.
- `price` (number): From the print. Used only if priceText is absent.
- `priceText` (string): The price EXACTLY as Pulse served it. This is what was signed — prefer it always.
- `sig` (string): Scheme tag from the print (pulse-index-v1).
- `signature` (string, required): Base64 signature from the print.
- `symbol` (string, required): From the print, unchanged.

### `pulse_asset_catalog` (~255 tokens)

Which crypto assets the Pulse Verity Index covers, at what grade, across how many venues, and how fast each one actually updates — cadence measured per asset from its own update intervals rather than from a poll schedule. Filter by coverage band (real-time, five-second, ten-second, slow, unavailable) or status (consensus, blended, indicative). Call this to find out whether a symbol is covered, and how thin it is, before quoting it. NOTE: these rows are UNSIGNED, including their prices — read a verifiable number through pulse_signed_price. Requires a Pulse API key via _apiKey. Example: pulse_asset_catalog({ limit: 5 }).

Input parameters:

- `_apiKey` (string): Pulse Verity API key. Free and self-serve at https://thepulse.markets/developers (60 req/min, 25,000/month, no card).
- `band` (string): Cadence band: real-time, five-second, ten-second, slow, unavailable.
- `limit` (number): Rows to return, max 500 (default 50).
- `offset` (number): Row offset for paging.
- `status` (string): Coverage grade: consensus, blended, indicative.

### `pulse_key_ring` (~96 tokens)

The public keys Pulse signs its price prints with, as PEM and JWK, plus the signing algorithm and the exact canonical string format — everything needed to verify a signed print yourself, OFFLINE, with no network call to Pulse. Use it to write your own verifier, or to audit what pulse_verify_print (this pack's ready-made offline checker) is checking against. Needs NO API key. Example: pulse_key_ring({}).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-pulse-verity/pipeworx-mcp-pulse-verity#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Pulse Verity MCP server?

Pulse Verity is an MCP server listed in the public MCP registry as io.github.pipeworx-io/pulse-verity. Pulse Verity, crypto index prices that come with a PROOF. This page covers its npm package (@pipeworx/mcp-pulse-verity).

### Is the Pulse Verity MCP server safe to use?

Pulse Verity scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Pulse Verity MCP server expose?

Pulse Verity exposes 6 tools: pulse_signed_price, pulse_signed_batch, pulse_settlement_print, pulse_verify_print, pulse_asset_catalog, pulse_key_ring. Their descriptions and schemas cost roughly 1,485 tokens of context every time the server is loaded.

### Is the Pulse Verity MCP server still maintained?

Pulse Verity is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Pulse Verity MCP server under?

Pulse Verity declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-pulse-verity
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-pulse-verity
- Repository: https://github.com/pipeworx-io/mcp-pulse-verity
- Website: https://pipeworx.io/packs/pulse-verity
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-pulse-verity/pipeworx-mcp-pulse-verity.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-pulse-verity/pipeworx-mcp-pulse-verity.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-pulse-verity/pipeworx-mcp-pulse-verity