# io.github.PulseBet/pulse-verity (npm · pulse-verity)

Read crypto reference prices and verify signed receipts. Includes limited keyless samples.

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

## Components

- npm · `pulse-verity`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pulsebet-pulse-verity/pulse-verity.md), [page](https://verifymcp.io/servers/pulsebet-pulse-verity/pulse-verity)

## Channel facts

- Registry: `npm`
- Package: `pulse-verity`
- Version: `1.2.6`
- 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-09-20.

- **Supply Chain Security**: 98/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.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to PulseBet/pulse-verity).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 698 tokens (~139/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 81/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 44% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 io.github.PulseBet/pulse-verity MCP server?

io.github.PulseBet/pulse-verity runs locally as an npm package, launched with npx -y 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 pulsebet-pulse-verity -- npx -y pulse-verity
```

### Cursor

```json
{
  "mcpServers": {
    "pulsebet-pulse-verity": {
      "command": "npx",
      "args": [
        "-y",
        "pulse-verity"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pulsebet-pulse-verity": {
      "command": "npx",
      "args": [
        "-y",
        "pulse-verity"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pulsebet-pulse-verity -- npx -y pulse-verity
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pulsebet-pulse-verity --command npx --arg -y --arg pulse-verity
```

### Hermes

```yaml
mcp_servers:
  pulsebet-pulse-verity:
    command: "npx"
    args: ["-y", "pulse-verity"]
```

### Netclaw

```json
{
  "McpServers": {
    "pulsebet-pulse-verity": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "pulse-verity"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pulsebet-pulse-verity -t stdio -c npx -a -y pulse-verity
```

### Other

```json
{
  "mcpServers": {
    "pulsebet-pulse-verity": {
      "command": "npx",
      "args": [
        "-y",
        "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-09-19 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 81, +1)

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

### 2026-09-13 (score 80, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-12 (score 64, +11)

- [security regression] Stability: 0.03 → unverified
- [security regression] Tool safety: pass → unverified
- [security improvement] Known CVEs: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Dependency health: unverified → 0.84
- [functional] Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Package version: 1.2.3 → 1.2.5
- [functional] Package version: 1.2.3 → 1.2.4

### 2026-09-11 (score 53, 0)

- [security regression] Tool safety: pass → unverified
- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [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] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.03
- [functional improvement] Dependency health: unverified → 0.84
- [functional] Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Package version: 1.2.1 → 1.2.3
- [functional] Package version: 1.2.1 → 1.2.2

### 2026-09-10 (score 53, +4)

- [security regression] Known CVEs: pass → unverified
- [security regression] Malware scan: pass → unverified
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional regression] Dependency health: 0.84 → unverified
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 44
- [functional] Package version: 1.1.0 → 1.2.1
- [functional] Package version: 1.1.0 → 1.2.0

### 2026-09-06 (score 49, 0)

- [security] Stability: Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare.
- [security] Tool safety: Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan.
- [functional] Schema quality: Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess.
- [functional] Capabilities: Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake.
- [functional] Tool coverage: Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess.

## MCP tools (5)

### `get_index_price` (~124 tokens)

Get Pulse Verity Index Price

Get a current signed crypto index price from /api/index/v1/price. Returns symbol, price, optional priceText, at, grade, signature, kid and sig. Preserve priceText exactly for verify_print. Optional tier, confidence, dispersionBps, interval, sources, engine and cadence describe the observation but are not covered by the v1 signature. Coverage changes: use list_index_assets to discover assets. A stale or unavailable response means no current price, never zero.

Input parameters:

- `symbol` (string, required): Crypto ticker symbol, e.g. BTC, ETH, SOL

### `get_index_batch` (~78 tokens)

Get Pulse Verity Index Batch

Read up to 100 crypto symbols in one /api/index/v1/batch request. Returns observations with individually signed successful rows and per-symbol errors for unavailable rows. Your API tier may allow fewer symbols. Verify each successful row with verify_print; surrounding batch and quality metadata are not signed. No automatic retries.

Input parameters:

- `symbols` (array, required)

### `list_index_assets` (~104 tokens)

List Pulse Verity Index Assets

Read one bounded page from /api/index/v1/verity/catalog. Discover crypto symbols and their current coverage status and measured cadence. Catalog rows, prices and metadata are unsigned: use get_index_price or get_index_batch for signed receipts. Availability changes; total is a catalog count, not a count of fresh prices. No automatic pagination.

Input parameters:

- `band` (string)
- `limit` (integer)
- `offset` (integer)
- `status` (string)

### `get_settlement_print` (~119 tokens)

Get Settlement Print

Get the recorded signed index print nearest a requested time from /api/index/v1/print. Accepts ISO-8601 or epoch milliseconds. Check deltaMs: it is the distance between your requested time and the sampled print. Sampling and retention are bounded; a recorded print need not equal a separate live read. Preserve priceText and kid when present for verify_print. deltaMs and other metadata are not signed.

Input parameters:

- `at` (string, required)
- `symbol` (string, required): Crypto ticker symbol, e.g. BTC, ETH, SOL

### `verify_print` (~273 tokens)

Verify a Signed Print

Verify a signed print locally with ECDSA P-256/SHA-256. Canonical bytes are pulse-index-v1\n<symbol>\n<priceText or String(price)>\n<at>\n<grade>. The public key ring is fetched from /api/index/v1/pubkey, cached for five minutes and refreshed at most once per 30 seconds on a failed check. A supplied kid selects only that exact key; old prints without kid are tried against the bounded published ring. No API key is sent to the public-key endpoint. valid=true authenticates only the canonical price fields, not kid, sig, quality, cadence, timestamps outside at, or other metadata. An invalid signature can mean an altered print or a key no longer published; it does not by itself prove tampering.

Input parameters:

- `at` (string, required): Timestamp from the print, unchanged
- `grade` (string, required)
- `kid` (string): Signing key identifier, when provided by the API
- `price` (required)
- `priceText`: Exact signed price text, when provided by the API; preserve unchanged
- `sig` (string)
- `signature` (string, required): ECDSA P-256 signature in base64
- `symbol` (string, required): Crypto ticker symbol, e.g. BTC, ETH, SOL

## Diagnostics

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

## Score history

- 2026-09-20: 83
- 2026-09-19: 83
- 2026-09-18: 82
- 2026-09-17: 82
- 2026-09-16: 81
- 2026-09-15: 81
- 2026-09-14: 80
- 2026-09-13: 80
- 2026-09-12: 64
- 2026-09-11: 53
- 2026-09-10: 53
- 2026-09-09: 49
- 2026-09-08: 49
- 2026-09-07: 49
- 2026-09-06: 49
- 2026-09-05: 49
- 2026-09-04: 49
- 2026-09-03: 49
- 2026-09-02: 49
- 2026-09-01: 49
- 2026-08-31: 49
- 2026-08-30: 49
- 2026-08-29: 49
- 2026-08-28: 49

## Common questions

### What is the io.github.PulseBet/pulse-verity MCP server?

io.github.PulseBet/pulse-verity is an MCP server listed in the public MCP registry as io.github.PulseBet/pulse-verity. Read crypto reference prices and verify signed receipts. Includes limited keyless samples. This page covers its npm package (pulse-verity).

### Is the io.github.PulseBet/pulse-verity MCP server safe to use?

io.github.PulseBet/pulse-verity scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 io.github.PulseBet/pulse-verity MCP server expose?

io.github.PulseBet/pulse-verity exposes 5 tools: get_index_price, get_index_batch, list_index_assets, get_settlement_print, verify_print. Their descriptions and schemas cost roughly 698 tokens of context every time the server is loaded.

### Is the io.github.PulseBet/pulse-verity MCP server still maintained?

io.github.PulseBet/pulse-verity is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.PulseBet/pulse-verity MCP server under?

io.github.PulseBet/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/pulse-verity
- Socket report: https://socket.dev/npm/package/pulse-verity
- Repository: https://github.com/PulseBet/pulse-verity
- Changelog RSS feed: https://verifymcp.io/servers/pulsebet-pulse-verity/pulse-verity.xml
- Changelog JSON feed: https://verifymcp.io/servers/pulsebet-pulse-verity/pulse-verity.json
- HTML version of this page: https://verifymcp.io/servers/pulsebet-pulse-verity/pulse-verity