Pulse Verity
NPM · PULSE-VERITY · 2 COMPONENTS
Signed Bitcoin and crypto prices for AI agents: multi-exchange prices anyone can verify offline.
Available components
Last scanned (4 hours ago)
Scores higher than 87% of npm servers
Category Crypto and Web3
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. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to PulseBet/pulse-verity). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 17 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability54
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2179 tokens (~242/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 36% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 20 Oct 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
- 19 Oct 26 0
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Known CVEs: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → 0.85 ▲ 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.3.4 → 1.3.6 functional
- Package version: 1.3.4 → 1.3.5 functional
- 18 Oct 26 −12
- Known CVEs: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Schema quality: 174 → 242 ▼ functional
- Schema quality: 174 → 213 ▼ functional
- Dependency health: 0.85 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Tool coverage: 26% → 36% ▲ 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.3.1 → 1.3.4 functional
- Package version: 1.3.1 → 1.3.3 functional
- Package version: 1.1.0 → 1.3.3 functional
- 17 Oct 26 +3
- Stability: 0.83 → pass security
- 16 Oct 26 −3
- Stability: pass → 0.83 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/pulse-verity@1.3.6
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | PulseBet/pulse-verity |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/PulseBet/pulse-verity/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3319117358 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:c64f02fa577fac8ee78c1865a9b2cda5b18b4079dc620c953df66e2499d66aa9bda2a446dc1ef29d92c2bcf91844f8e788efcd9ed598a7708a69921de |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_account_status Get Pulse Verity Account Status ~118
Read this developer key'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. The key itself is never returned. Needs a developer key (PULSE_API_KEY) or the hosted server.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 |
No examples provided.
get_index_batch Get Pulse Verity Index Batch ~133
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 plan may allow fewer symbols per request: get_account_status shows batchMaxSymbols, and a larger request is refused with code TOO_MANY_SYMBOLS, batchLimit and requested, so split it. Verify each successful row with verify_print and require recordValid=true before trusting its quality fields. Surrounding batch metadata is unsigned. No automatic retries. Needs a developer key (PULSE_API_KEY) or the hosted server.
| Name | Type | Req | Description |
|---|---|---|---|
| symbols | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | – |
| observations | array | – | – |
| requestId | string | yes | Identifier for this MCP call; not a signed price field. |
| requested | integer | – | – |
| returned | integer | – | – |
| success | boolean | – | – |
No examples provided.
get_index_history Get Pulse Verity Index History ~549
Read one page of index history for a crypto symbol from /api/index/v1/history: candles (open, high, low, close per interval), summary metrics, pagination and, for dataset=verified, verifiedObservations. dataset=verified (default) is built from prints Pulse calculated and signed live; dataset=reconstructed is rebuilt history, not signed at the historical time, served at interval 1h or 1d. Candles, metrics and surrounding metadata are unsigned. Each verifiedObservations row carries symbol, price (the exact signed text), at, grade, signature and kid; pass those fields to verify_print to check a row, which authenticates its price fields only (history rows carry no v2 block). A null kid can be passed as it is or left out; a row whose signature or grade is null cannot be verified. The account's plan sets how far back history reaches: when the request started earlier, rangeClamped is true and from is where the page begins. limit (1 to 1000, default 200) bounds the rows on one page. For dataset=verified at interval 1h or 1d it is at most 250: a page there can count hours, and each hour can carry up to four signed prints (open, high, low and close), so verifiedObservations can hold up to four rows per hour. For the next page pass pagination.nextCursor as cursor with the same symbol, dataset and interval. from and to are ISO-8601 times; the default window is the 30 days before to. Pass assetId, written as the server issues it (native:<namespace>:<id>, or contract:<network>:<address> such as contract:eip155:1:0x...), when a symbol identifies more than one asset. Needs a developer key (PULSE_API_KEY) or the hosted server.
| Name | Type | Req | Description |
|---|---|---|---|
| assetId | string | – | Canonical asset identity as the server issues it, e.g. native:pulse-verity:btc or contract:eip155:1:0x...; only when a symbol identifies more than one asset |
| cursor | string | – | pagination.nextCursor from the previous page |
| dataset | string | – | – |
| from | string | – | Start of the window, ISO-8601 |
| interval | string | – | – |
| limit | integer | – | Rows on one page; at most 250 for dataset=verified at interval 1h or 1d |
| symbol | string | yes | Crypto ticker symbol, e.g. BTC, ETH, SOL |
| to | – | – | End of the window, ISO-8601; defaults to now |
| Name | Type | Req | Description |
|---|---|---|---|
| asset | – | – | – |
| candles | array | – | – |
| contemporaneouslySigned | boolean | – | – |
| dataset | string | – | – |
| error | object | – | – |
| from | string | – | – |
| identityBinding | string | – | – |
| interval | string | – | – |
| metrics | object | – | – |
| note | string | – | – |
| pagination | object | – | – |
| provenance | object | – | – |
| rangeClamped | boolean | – | – |
| requestId | string | yes | Identifier for this MCP call; not a signed price field. |
| success | boolean | – | – |
| symbol | string | – | – |
| to | – | – | – |
| verifiedArchiveSince | – | – | – |
| verifiedObservations | array | – | – |
No examples provided.
get_index_price Get Pulse Verity Index Price ~152
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. Pass the whole print including v2 to verify_print; require recordValid=true before trusting quality fields. Coverage changes: use list_index_assets to discover assets. A stale or unavailable response means no current price, never zero. Without a developer key, only limited daily BTC, ETH and SOL samples are served.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Crypto ticker symbol, e.g. BTC, ETH, SOL |
| Name | Type | Req | Description |
|---|---|---|---|
| at | string | – | – |
| cadence | – | – | – |
| confidence | – | – | – |
| dispersionBps | – | – | – |
| engine | – | – | – |
| error | object | – | – |
| getKey | string | – | – |
| grade | string | – | – |
| interval | – | – | – |
| kid | string | – | – |
| note | string | – | – |
| price | number | – | – |
| priceText | string | – | – |
| requestId | string | yes | Identifier for this MCP call; not a signed price field. |
| sample | boolean | – | – |
| sig | string | – | – |
| signature | string | – | – |
| sources | – | – | – |
| success | boolean | – | – |
| symbol | string | – | – |
| tier | – | – | – |
| v2 | object | – | – |
No examples provided.
get_recorded_print Get Recorded Print ~151
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 the whole print, including priceText, kid and v2, for verify_print. Require recordValid=true before trusting quality fields. Request-envelope fields such as deltaMs are unsigned. Needs a developer key (PULSE_API_KEY) or the hosted server.
| Name | Type | Req | Description |
|---|---|---|---|
| at | string | yes | – |
| symbol | string | yes | Crypto ticker symbol, e.g. BTC, ETH, SOL |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Identifier for this MCP call; not a signed price field. |
| sample | boolean | – | – |
| sig | string | – | – |
| signature | string | – | – |
| sources | – | – | – |
| success | boolean | – | – |
| symbol | string | – | – |
| tier | – | – | – |
| v2 | object | – | – |
No examples provided.
get_settlement_print Get Recorded Print (earlier name) ~180
The earlier name of get_recorded_print, kept so existing integrations keep working; prefer get_recorded_print. Same input, output and behaviour. 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 the whole print, including priceText, kid and v2, for verify_print. Require recordValid=true before trusting quality fields. Request-envelope fields such as deltaMs are unsigned. Needs a developer key (PULSE_API_KEY) or the hosted server.
| Name | Type | Req | Description |
|---|---|---|---|
| at | string | yes | – |
| symbol | string | yes | Crypto ticker symbol, e.g. BTC, ETH, SOL |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Identifier for this MCP call; not a signed price field. |
| sample | boolean | – | – |
| sig | string | – | – |
| signature | string | – | – |
| sources | – | – | – |
| success | boolean | – | – |
| symbol | string | – | – |
| tier | – | – | – |
| v2 | object | – | – |
No examples provided.
list_index_assets List Pulse Verity Index Assets ~119
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. Needs a developer key (PULSE_API_KEY) or the hosted server.
| Name | Type | Req | Description |
|---|---|---|---|
| band | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| status | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| bands | array | – | – |
| count | integer | – | – |
| engine | string | – | – |
| error | object | – | – |
| note | string | – | – |
| requestId | string | yes | Identifier for this MCP call; not a signed price field. |
| rows | array | – | – |
| total | integer | – | – |
No examples provided.
submit_verity_feedback Submit Verity Feedback ~159
Submit a reproducible Verity API or MCP bug, missing capability or data-quality report for human review. Requires a developer key (PULSE_API_KEY) or the hosted server, and an enabled feedback service. Include the failed call's requestId when available. Do not send secrets, personal information or conversation transcripts. Saves a private report; does not change prices, start trades or open or merge a PR. Returns a tracking receipt only after storage succeeds.
| Name | Type | Req | Description |
|---|---|---|---|
| actual | string | yes | – |
| category | string | yes | – |
| expected | string | yes | – |
| observedAt | string | – | – |
| reproduction | array | yes | – |
| requestId | string | – | – |
| surface | string | yes | – |
| symbol | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| duplicate | boolean | – | – |
| error | object | – | – |
| feedback | object | – | – |
| requestId | string | yes | Identifier for this MCP call; not a signed price field. |
| success | boolean | – | – |
No examples provided.
verify_print Verify a Signed Print ~455
Verify a signed print locally with ECDSA P-256/SHA-256. Legacy valid authenticates only the v1 canonical price fields. Pass the whole print including v2 to authenticate its complete live, archive or daily-close index record; agents using sources, confidence, interval or cadence must require recordValid=true. Live records sign 18 fields; archive records sign 13 without freshness ages, and daily-close records add signed assetId and closeDay. v2.signedFields lists exactly what is authenticated. kind selects the format and is not signed. Added non-null freshness ages invalidate archived verification. verificationScope is full-record only when both signatures and all required fields match, price-only for a valid v1 print without v2, or invalid otherwise. metadataSigned equals recordValid. deltaMs and surrounding metadata remain unsigned. Public keys come from /api/index/v1/pubkey, cached five minutes with refresh at most every 30 seconds. Each supplied kid selects only its exact published key; v1 prints without kid (or with kid null, as some history rows carry) use the bounded ring. No API key is sent to the key endpoint. Invalid verification can mean alteration or a key no longer published. Works without a developer key.
| Name | Type | Req | Description |
|---|---|---|---|
| assetId | – | – | – |
| at | string | yes | Timestamp from the print, unchanged |
| cadence | – | – | – |
| closeDay | – | – | – |
| confidence | – | – | – |
| dispersionBps | – | – | – |
| engine | – | – | – |
| grade | string | yes | – |
| interval | – | – | – |
| kid | – | – | Signing key identifier, when provided by the API; null counts as absent |
| kind | string | – | Selects the daily-close record format; this selector is not itself signed |
| price | – | yes | – |
| priceText | – | – | Exact signed price text, when provided by the API; preserve unchanged |
| sig | string | – | – |
| signature | string | yes | ECDSA P-256 signature in base64 |
| sources | – | – | – |
| symbol | string | yes | Crypto ticker symbol, e.g. BTC, ETH, SOL |
| tier | – | – | – |
| v2 | object | – | The unchanged v2 block, which signs price and quality fields together |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | – | – | – |
No examples provided.
How do I install the Pulse Verity MCP server?
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.
npm · pulse-verity
claude mcp add pulsebet-pulse-verity -- npx -y pulse-verity
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 npm package (pulse-verity).
Is the Pulse Verity MCP server safe to use?
Pulse Verity scores 85 out of 100 on VerifyMCP. We recorded 1 known advisory against 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 9 tools: get_index_price, get_index_batch, list_index_assets, get_recorded_print, get_settlement_print, and 4 more. Their descriptions and schemas cost roughly 2,016 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.