pulse-verity
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PULSE_API_KEY | Yes | API key for Pulse Verity Index API. Obtain from https://thepulse.markets/developers |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_index_priceA | 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. |
| get_index_batchA | 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. |
| list_index_assetsA | 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. |
| get_settlement_printA | 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. |
| verify_printA | Verify a signed print locally with ECDSA P-256/SHA-256. Canonical bytes are pulse-index-v1\n\n<priceText or String(price)>\n\n. 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: live single price, live batch prices, asset discovery, historical print lookup, and local signature verification. There is no meaningful overlap among the tool boundaries.
All tool names follow a predictable snake_case action_noun pattern: get_*, list_*, and verify_*. The verbs align with the operation type, and there is no mixing of naming conventions.
Five tools is well-scoped for a focused signed index price service. Each tool serves a necessary function and there is no redundancy or bloat.
The core workflow of discovering assets, fetching current single/batch prices, retrieving historical prints, and verifying signatures is well covered. Minor gaps remain around catalog pagination and direct visibility into key-ring or retention bounds, but these are workable limitations.