# Pulse Verity (remote · mcp.thepulse.markets)

Signed Bitcoin and crypto prices for AI agents: multi-exchange prices anyone can verify offline.

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

## Components

- remote · `mcp.thepulse.markets`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pulsebet-pulse-verity/api-index-mcp.md), [page](https://verifymcp.io/servers/pulsebet-pulse-verity/api-index-mcp)
- npm · `pulse-verity`: 85/100, [markdown](https://verifymcp.io/servers/pulsebet-pulse-verity/pulse-verity.md), [page](https://verifymcp.io/servers/pulsebet-pulse-verity/pulse-verity)

## Channel facts

- Endpoint: `https://mcp.thepulse.markets/api/index/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.6`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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.

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

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

Pulse Verity is a hosted endpoint at https://mcp.thepulse.markets/api/index/mcp, so there is nothing to install locally. 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 --transport http pulsebet-pulse-verity 'https://mcp.thepulse.markets/api/index/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "pulsebet-pulse-verity": {
      "url": "https://mcp.thepulse.markets/api/index/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pulsebet-pulse-verity": {
      "type": "http",
      "url": "https://mcp.thepulse.markets/api/index/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.pulsebet-pulse-verity]
url = "https://mcp.thepulse.markets/api/index/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pulsebet-pulse-verity": {
      "type": "remote",
      "url": "https://mcp.thepulse.markets/api/index/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pulsebet-pulse-verity --url 'https://mcp.thepulse.markets/api/index/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  pulsebet-pulse-verity:
    url: "https://mcp.thepulse.markets/api/index/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "pulsebet-pulse-verity": {
      "Transport": "http",
      "Url": "https://mcp.thepulse.markets/api/index/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add pulsebet-pulse-verity -t streamable-http -u 'https://mcp.thepulse.markets/api/index/mcp'
```

### Other

```json
{
  "mcpServers": {
    "pulsebet-pulse-verity": {
      "type": "http",
      "url": "https://mcp.thepulse.markets/api/index/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-05 (score 83, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: pass → unverified
- [security regression] Stability: 0.53 → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.

### 2026-11-03 (score 83, +1)

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

### 2026-11-01 (score 82, +1)

- [security] Tool “submit_verity_feedback” rewrote its description, which is the text the model reads
- [cosmetic] “submit_verity_feedback” added an optional parameter “quote”

### 2026-10-30 (score 81, +1)

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

### 2026-10-28 (score 80, +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-10-26 (score 79, +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-10-24 (score 78, +1)

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

### 2026-10-21 (score 77, +1)

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

## MCP tools (9)

### `get_index_price` (~149 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; they are not covered by the v1 signature, and the v2 block signs them with the price. Pass the whole print, v2 included, to verify_print. 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

Output parameters:

- `at` (string)
- `cadence`
- `confidence`
- `dispersionBps`
- `engine`
- `error` (object)
- `getKey` (string)
- `grade` (string)
- `interval`
- `kid` (string)
- `note` (string)
- `price` (number)
- `priceText` (string)
- `requestId` (string): Identifier for this MCP call; not a signed price field.
- `sample` (boolean)
- `sig` (string)
- `signature` (string)
- `sources`
- `success` (boolean)
- `symbol` (string)
- `tier`
- `v2` (object)

### `get_index_batch` (~121 tokens)

Get Pulse Verity Index Batch

Read signed prices for up to 100 symbols per request; this account's plan may allow fewer (get_account_status reports batchMaxSymbols). One /api/index/v1/batch request returns observations with individually signed successful rows and per-symbol errors for unavailable rows. A request over the plan's limit is refused with code TOO_MANY_SYMBOLS: split it. Verify each successful row with verify_print; the v2 block on each row signs its quality fields, while the surrounding batch metadata is not signed. No automatic retries.

Input parameters:

- `symbols` (array, required)

Output parameters:

- `error` (object)
- `observations` (array)
- `requestId` (string): Identifier for this MCP call; not a signed price field.
- `requested` (integer)
- `returned` (integer)
- `success` (boolean)

### `list_index_assets` (~129 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): Rows per page, 1 to 100; 50 when omitted. A plan may return fewer: use count and offset.
- `offset` (integer)
- `status` (string)

Output parameters:

- `bands` (array)
- `count` (integer)
- `engine` (string)
- `error` (object)
- `note` (string)
- `requestId` (string): Identifier for this MCP call; not a signed price field.
- `rows` (array)
- `total` (integer)

### `get_recorded_print` (~159 tokens)

Get Recorded 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. qualityRecorded says whether its quality fields were stored when it was recorded (prints from 1 Oct 2026). Preserve priceText, kid and the v2 block when present for verify_print. deltaMs is not signed. Formerly named get_settlement_print; calls under that name still work.

Input parameters:

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

Output parameters:

- `assetId`
- `at` (string)
- `cadence`
- `closeDay`
- `confidence`
- `deltaMs` (number)
- `dispersionBps`
- `engine`
- `error` (object)
- `getKey` (string)
- `grade` (string)
- `interval`
- `kid` (string)
- `kind` (string)
- `note` (string)
- `price` (number)
- `priceText` (string)
- `qualityRecorded` (boolean)
- `requestId` (string): Identifier for this MCP call; not a signed price field.
- `sample` (boolean)
- `sig` (string)
- `signature` (string)
- `sources`
- `success` (boolean)
- `symbol` (string)
- `tier`
- `v2` (object)

### `verify_print` (~494 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 read 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. valid=true authenticates only the canonical price fields, not kid, sig, quality, cadence, timestamps outside at, or other metadata. When the print carries a v2 block (pulse-index-v2), it is verified too: v2.valid=true means the signature over v2.canonical is valid AND every signed line (sources, tier, confidence, dispersionBps, interval, cadence, engine, price and the rest) matches the supplied fields; v2.signedFields are the signed values and v2.mismatches names any field that differs. recordValid=true and verificationScope=full-record require BOTH price and complete v2 record verification. metadataSigned equals recordValid. Require recordValid before trusting quality fields. A v1-only print has scope price-only, never verified metadata. Neither signature proves freshness or settlement suitability; indicative data must not be used for settlement. An invalid signature can mean an altered print or a key no longer published; it does not by itself prove tampering.

Input parameters:

- `assetId`
- `at` (string, required): Timestamp from the print, unchanged
- `cadence`
- `closeDay`
- `confidence`
- `dispersionBps`
- `engine`
- `grade` (string, required)
- `interval`
- `kid` (string): Signing key identifier, when provided by the API
- `kind` (string)
- `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
- `sources`
- `symbol` (string, required): Crypto ticker symbol, e.g. BTC, ETH, SOL
- `tier`
- `v2` (object): The v2 block from the print, unchanged: it signs the whole record, quality fields included

Output parameters:

- `checked` (string)
- `error` (object)
- `keySource` (string)
- `metadataSigned` (boolean)
- `recordValid` (boolean): Both signatures and every required v2 field verified. Does not prove freshness or settlement suitability.
- `requestId` (string): Identifier for this MCP call; not a signed price field.
- `v2`
- `valid` (boolean): Legacy price-only signature check. Use recordValid for quality metadata.
- `verificationScope` (string)
- `verifiedWithKid`

### `get_account_status` (~95 tokens)

Get Pulse Verity Account Status

Read this connection's Pulse Verity plan and usage from /api/index/v1/account: plan, used (calls counted this UTC month), limit, remaining, resetAt, perMinute, batchMaxSymbols, capacityAction and upgradeUrl (the plans page). The monthly allowance is account-wide: every key and connected app on the account shares it. perMinute applies to each key. This call does not count toward the allowance.

Output parameters:

- `batchMaxSymbols`
- `capacityAction` (string)
- `error` (object)
- `limit` (integer): The monthly allowance
- `perMinute`
- `plan` (string): The plan name customers see, e.g. Developer
- `remaining` (integer)
- `requestId` (string): Identifier for this MCP call; not a signed price field.
- `resetAt` (string)
- `success` (boolean)
- `upgradeUrl` (string)
- `used` (integer): Calls counted this UTC month, account-wide

### `get_index_history` (~425 tokens)

Get Pulse Verity Index History

Read price history for one crypto symbol from /api/index/v1/history: candles (open, high, low, close) at 1m, 5m, 1h or 1d, with period metrics and pagination. dataset=verified (default) is built from prints Pulse signed live; reconstructed is rebuilt history at 1h or 1d and was not signed at the historical time. The account's plan sets whether history is included and how far back a request reaches: rangeClamped says the window was shortened, and historyLimit names the plan when the plan did it. Each call counts as one API call. For the next page pass pagination.nextCursor as cursor with the same symbol, dataset and interval. Signed rows (verifiedObservations) are returned only with includeSignedRows=true; each verifies with verify_print. Candles and metrics are not signed. An empty page means no recorded history in that window, never a zero price.

Input parameters:

- `assetId` (string): Canonical asset id, when a ticker names more than one asset.
- `cursor` (string): pagination.nextCursor from the previous page, unchanged.
- `dataset` (string): verified (default): built from prints Pulse signed live. reconstructed: rebuilt hourly and daily history, not signed at the historical time; interval 1h or 1d only.
- `from` (string): Start, ISO-8601 or epoch milliseconds (13 digits); 30 days before `to` when omitted. The plan may shorten it.
- `includeSignedRows` (boolean): Include verifiedObservations, each a signed row verify_print checks (verified dataset only). Off by default to keep pages small.
- `interval` (string): Candle width; 1h when omitted.
- `limit` (integer): Underlying points per page, 1 to 1000; 500 when omitted.
- `symbol` (string, required): Crypto ticker symbol, e.g. BTC
- `to`: End, ISO-8601 or epoch milliseconds (13 digits); now when omitted.

Output parameters:

- `candles` (array)
- `dataset` (string)
- `error` (object)
- `from` (string)
- `interval` (string)
- `pagination` (object)
- `rangeClamped` (boolean)
- `requestId` (string): Identifier for this MCP call; not a signed price field.
- `signedRowsOmitted` (integer)
- `success` (boolean)
- `symbol` (string)
- `to` (string)

### `get_upgrade_options` (~240 tokens)

Get Pulse Verity Upgrade Options

List the Pulse Verity plans with their limits and prices, and the prepaid call packs and extra stream connections while each is on sale, each with a portal link. Read-only; does not count toward the allowance. The current plan is marked when the account is on that plan's terms (currentPlan shows the account's own limits either way), and when a recent plan refusal is known (or reason is given) the smallest plan, add-on or pack that fixes it is recommended. A link opens the portal, which shows the item, price and terms; the account holder completes payment on Stripe. Nothing is bought by this tool or by opening a link.

Input parameters:

- `dataset` (string): For HISTORY_WINDOW: the history dataset that was shortened; verified (the get_index_history default) when omitted.
- `feature` (string): For RESEARCH_NOT_INCLUDED: history when get_index_history was refused, research-tools for compare or metadata; when omitted, the plan that includes both.
- `reason` (string): A refusal code this connection received, e.g. TOO_MANY_SYMBOLS or MONTHLY_LIMIT, when it is not the most recent one.

Output parameters:

- `checkout` (object)
- `currency` (string)
- `currentPlan`
- `error` (object)
- `plans` (array)
- `pricingVersion` (string)
- `recommendation`
- `requestId` (string): Identifier for this MCP call; not a signed price field.
- `success` (boolean)

### `submit_verity_feedback` (~220 tokens)

Submit Verity Feedback

Write one structured bug, missing capability, or data quality report for private human triage. Only submit when the user requests reporting; do not include keys, passwords, transcripts or attachments. For a price problem, add quote: the price, at and source exactly as you received them, and grade, signature and kid from the print when you have it; with a signature the server checks the quote against Verity's published keys, so triage can tell a real Verity print from an altered or foreign one. Returns a durable receipt and duplicate flag, not a promise of a fix. No code or production behavior changes automatically. Status is available with the same account at GET /api/index/v1/feedback/<id>.

Input parameters:

- `actual` (string, required)
- `category` (string, required)
- `expected` (string, required)
- `observedAt` (string)
- `quote` (object)
- `reproduction` (array, required)
- `requestId` (string)
- `surface` (string, required)
- `symbol` (string)

Output parameters:

- `duplicate` (boolean)
- `error` (object)
- `feedback` (object)
- `requestId` (string): Identifier for this MCP call; not a signed price field.
- `success` (boolean)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/pulsebet-pulse-verity/api-index-mcp#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 83
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 80
- 2026-10-28: 80
- 2026-10-27: 79
- 2026-10-26: 79
- 2026-10-25: 78
- 2026-10-24: 78
- 2026-10-23: 77
- 2026-10-22: 77
- 2026-10-21: 77
- 2026-10-20: 76
- 2026-10-19: 76
- 2026-10-18: 39

## Common questions

### What is the Pulse Verity MCP server?

Pulse Verity is an MCP server listed in the public MCP registry as io.github.PulseBet/pulse-verity. Signed Bitcoin and crypto prices for AI agents: multi-exchange prices anyone can verify offline. This page covers its hosted endpoint (https://mcp.thepulse.markets/api/index/mcp).

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

Pulse Verity scores 83 out of 100 on VerifyMCP. 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 9 tools: get_index_price, get_index_batch, list_index_assets, get_recorded_print, verify_print, and 4 more. Their descriptions and schemas cost roughly 2,032 tokens of context every time the server is loaded.

### Does the Pulse Verity MCP server require authentication?

Its publisher declares no required credentials for Pulse Verity. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

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

Pulse Verity is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Pulse Verity MCP server?

VerifyMCP ran 3 checks on Pulse Verity, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about Pulse Verity: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.thepulse.markets/api/index/mcp
- Repository: https://github.com/PulseBet/pulse-verity
- Changelog RSS feed: https://verifymcp.io/servers/pulsebet-pulse-verity/api-index-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/pulsebet-pulse-verity/api-index-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pulsebet-pulse-verity/api-index-mcp.json
- HTML version of this page: https://verifymcp.io/servers/pulsebet-pulse-verity/api-index-mcp