io.github.PulseBet/pulse-verity
NPM · PULSE-VERITY · SCANNED SEP 20
Read crypto reference prices and verify signed receipts. Includes limited keyless samples.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 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 5 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 44% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
npm · pulse-verity
claude mcp add pulsebet-pulse-verity -- npx -y pulse-verity
{
"mcpServers": {
"pulsebet-pulse-verity": {
"command": "npx",
"args": [
"-y",
"pulse-verity"
]
}
}
} {
"servers": {
"pulsebet-pulse-verity": {
"command": "npx",
"args": [
"-y",
"pulse-verity"
]
}
}
} codex mcp add pulsebet-pulse-verity -- npx -y pulse-verity
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pulsebet-pulse-verity": {
"type": "local",
"command": [
"npx",
"-y",
"pulse-verity"
],
"enabled": true
}
}
} openclaw mcp add pulsebet-pulse-verity --command npx --arg -y --arg pulse-verity
mcp_servers:
pulsebet-pulse-verity:
command: "npx"
args: ["-y", "pulse-verity"] {
"McpServers": {
"pulsebet-pulse-verity": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"pulse-verity"
]
}
}
} assistant mcp add pulsebet-pulse-verity -t stdio -c npx -a -y pulse-verity
{
"mcpServers": {
"pulsebet-pulse-verity": {
"command": "npx",
"args": [
"-y",
"pulse-verity"
]
}
}
} 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.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +1
- Stability: 0.13 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- 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 functional
- 13 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 12 Sept 26 +11
- Stability: 0.03 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Known CVEs: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 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 functional
- 11 Sept 26 0
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- 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. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- 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 functional
- 10 Sept 26 +4
- Known CVEs: pass → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- 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). security
- Dependency health: 0.84 → unverified ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- 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 functional
- 6 Sept 26 0
- 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. security
- 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. 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 20 Sept 2026 · Analysed npm/pulse-verity@1.2.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 | 2836243642 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:fa29741e7a1c74d372d527a432100d36f973af2c9ce396ba186947b1ea2db9069cef6857e2ef12e59bcab72580807650b182619475dbfe97b60c5823c |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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_index_batch Get Pulse Verity Index Batch ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| symbols | array | yes | – |
No output schema declared.
No examples provided.
get_index_price Get Pulse Verity Index Price ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Crypto ticker symbol, e.g. BTC, ETH, SOL |
No output schema declared.
No examples provided.
get_settlement_print Get Settlement Print ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| at | string | yes | – |
| symbol | string | yes | Crypto ticker symbol, e.g. BTC, ETH, SOL |
No output schema declared.
No examples provided.
list_index_assets List Pulse Verity Index Assets ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| band | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
verify_print Verify a Signed Print ~273
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.
| Name | Type | Req | Description |
|---|---|---|---|
| at | string | yes | Timestamp from the print, unchanged |
| grade | string | yes | – |
| kid | string | – | Signing key identifier, when provided by the API |
| 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 |
| symbol | string | yes | Crypto ticker symbol, e.g. BTC, ETH, SOL |
No output schema declared.
No examples provided.
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.