mcpbeat Sign in

Pulse Verity MCP Server

answering

Pulse Verity is answering right now. Last checked 12 min ago. 613 installs a week from npm. It exposes 9 tools. Last commit 19 Oct 2026.

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

Installs per day peak 472 · avg 71 · +351% w/w
a month agotoday
Uptime history 8 days of history · worst day 78%
8 days agonow
100.0%
Uptime 24h
91 of 91 checks
9
Tools
read from the server
428 ms
Response time
average over 24h
613
Installs / week
npm and PyPI

What the code does

We read the source, 5 d ago · tools taken from the live server · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Builds a database query by concatenation integrations/n8n/validate-monitor.mjs:111
for(const [label,change] of [['price',p=>p.price++],['signature',p=>p.signature='A'.repeat(86)+'=='],['metadata',p=>p.confidence=0.01],['wrong symbol',p=>p.symbol='ETH'],['v2 missing',p=>delete p.v2]])test('tampered '+label+' cannot pass policy',()=>{

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add pulse-verity --transport http https://mcp.thepulse.markets/api/index/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.thepulse.markets/api/index/mcp
~/.codex/config.toml
[mcp_servers.pulse-verity]
url = "https://mcp.thepulse.markets/api/index/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "pulse-verity": {
      "url": "https://mcp.thepulse.markets/api/index/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "pulse-verity": {
      "type": "http",
      "url": "https://mcp.thepulse.markets/api/index/mcp"
    }
  }
}

Available tools 9

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

index
get_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.
get_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.
get_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.
list_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.
account
get_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.
recorded
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.
submit
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. 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>.
upgrade
get_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.
verify
verify_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.

Endpoints

URLTransportStateLatencyChecked
https://mcp.thepulse.markets/api/index/mcp streamable-http answering 364 ms 12 min ago

Alternatives to Pulse Verity

same job, measured the same way
Bitculator
by bitculator

Crypto market data for AI agents: live prices, OHLCV, sentiment, indicators and exchanges.

answering
ZebPay MCP Server
by zebpayrajesh

MCP server for ZebPay crypto exchange — fetch prices, balances, and manage orders

16 installs/wk local only
Arzbin MCP Server
by arzbin

Live Iran exchange rates, gold, crypto, and Toman market data for AI agents.

6 tools answering
Agent Data Pro
by orionsmithers

Research articles and live crypto prices for AI agents via x402 on Base.

6 tools answering
Cryptobuddy
by com-cryptobuddy

Australian crypto exchange intelligence for AI agents, with x402 payments on XRPL and Base.

2 tools answering
CoinMarketCap
by coinmarketcap

Official CoinMarketCap MCP server: real-time crypto prices, market cap, rankings and exchange data.

answering
MCP Market Data
by cryptoapis-io

MCP server for cryptocurrency asset prices, exchange rates, and market metadata via Crypto APIs

28 installs/wk local only
PriceFeed
by pricefeed

Real-time & historical crypto and fiat exchange rates, median-aggregated from multiple sources.

4 tools answering

Pulse Verity — questions

Answers built from our own checks of this server.

What can Pulse Verity do?
It exposes 9 tools, read directly from the server on our last check. Among them: get_account_status, get_index_batch, get_index_history, get_index_price, get_recorded_print, get_upgrade_options and 3 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Pulse Verity working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 428 ms. The bar chart above shows every period we have measured.
How do I connect Pulse Verity?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Pulse Verity need an API key?
No. Pulse Verity completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 9 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Pulse Verity?
It answers our handshake in 428 ms on average, which is faster than 32% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Pulse Verity?
The npm package pulse-verity was installed 613 times in the last week. Week over week that is +351%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Pulse Verity open source?
The code is open source: it is published under the MIT licence, written in TypeScript, 3 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at mcp.thepulse.markets, which runs on its operator's own terms.