Pulse Verity

Pulse Verity Index

Signed crypto prices built for AI agents. pulse-verity is an MCP server for signed crypto reference prices from the Pulse Verity Index, with local receipt verification. Try limited BTC, ETH and SOL samples without an account or API key. A valid signature authenticates the signed fields; it does not prove price accuracy, freshness or suitability for trading.

View the GitHub MCP Registry listing · Developer access and plans

Listed in the GitHub MCP Registry and the official MCP Registry as io.github.PulseBet/pulse-verity. A listing is not an endorsement by GitHub or the registry.

Two ways to start:

• Fastest, no install: connect the hosted server and sign in with Google. Your developer account and key are created for you.
• Try without an account: the three steps below run the npm package with no key and verify a signed BTC sample.

First signed BTC sample: install, read, verify

1. Install in Claude Code. With Claude Code, Node.js 18 or newer and npm available, run this command in your terminal. It registers the pinned stdio server; npx downloads and starts the package when your client connects.

claude mcp add pulse-verity -- npx -y pulse-verity@1.3.6

Start a new Claude Code session. Leave PULSE_API_KEY unset for this keyless workflow. If you already configured a Verity server, review that client's saved configuration rather than registering a duplicate. For VS Code, Cursor, Codex and other clients, see manual MCP configuration.

2. Request a sample. Paste this prompt into your connected agent and approve the two read/verification tool calls if your client asks:

Read a BTC sample using Pulse Verity, verify the unchanged signed receipt, and report its timestamp, sample status and verification scope.

The first tool call is get_index_price with these arguments:

{ "symbol": "BTC" }

3. Verify that same receipt. The agent should pass the successful price object from structuredContent (or the equivalent text JSON) directly to verify_print as its top-level tool arguments, including the complete v2 block when present. Do not round price, rewrite priceText, remove signed fields or fetch a replacement price to verify. Do not pass the outer MCP content/structuredContent envelope or wrap the receipt in a print property.

Check the original observation's at timestamp and sample: true, then inspect the verifier's valid, recordValid and verificationScope. full-record requires recordValid: true; price-only authenticates only the legacy price fields. Sample status and other envelope metadata are not signed. A missing, stale, rate-limited or invalid response is not a successful verified sample.

Verification runs locally after fetching Pulse's published public-key ring over HTTPS. It needs the matching key to remain published; it is not a promise of a fully offline first run. See signature coverage for the exact fields and trust boundary.

Without a key vs. developer access

Create or sign in to your account at the developer portal, then view available plans. Configure keys only in your client's private settings, never in a prompt or committed configuration. Developer access does not imply unlimited usage or availability of every asset. Request limits and account access explains temporary rate limits and monthly allowances.

Tools and integration guides

For workflow and framework setup, see the integration examples: Vercel AI SDK, n8n, LangChain/LangGraph, Google ADK, CrewAI, Dify, Flowise and Langflow.

For the CrewAI Flow template, open the Python project and run the documented crewai install and crewai flow kickoff commands from that directory. The Flow reads one index price and verifies its signed record without an LLM.

It exposes read-only data, verification and account tools, and one private feedback tool:

get_index_history reads dataset: "verified" (the default, built from prints Pulse signed live) or "reconstructed" (rebuilt history, not signed at the historical time, at interval 1h or 1d). Candles and metrics are unsigned summaries. Each verifiedObservations row carries symbol, price (the exact signed text), at, grade, signature and kid, which verify_print checks as a price-only print. A kid of null can be passed as it is or left out; a row whose signature or grade is null cannot be verified. How far back history reaches depends on your plan: when a request starts earlier, rangeClamped is true and from shows 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, because a page there can count hours and each hour can carry up to four signed prints (open, high, low and close). Pass pagination.nextCursor as cursor for the next page. When a symbol identifies more than one asset, pass assetId as the server writes it: native: : or contract: : , for example contract:eip155:1:0x....

Only the feedback tool writes a report. It requires a developer key and an enabled feedback service; it cannot trade, transfer funds or change prices. This package contains no Pulse platform engine code.

Connect the hosted server (sign in with Google, no key to copy)

The hosted MCP runs on Pulse's side at https://mcp.thepulse.markets/api/index/mcp. Nothing is installed locally. Signing in creates your Pulse Verity developer account and its key for you (Developer plan, no charge), so there is no key to copy or paste.

• Claude (web, desktop, mobile): Settings → Connectors → Add custom connector → paste the URL → Connect, then sign in (Continue with Google, or email).
• ChatGPT: Settings → Connectors → Create → paste the URL. Same sign-in.
• Claude Code: claude mcp add --transport http pulse-verity https://mcp.thepulse.markets/api/index/mcp, then run /mcp in Claude Code and sign in.
• Claude plugin: see the Claude plugin guide.
• Grok Bot and the xAI API: see Use Pulse Verity with Grok.

Sign-in is standard OAuth 2.1 (dynamic client registration, PKCE). Discovery documents live at /.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource/api/index/mcp. Every hosted call counts against your developer account's allowance exactly like a REST call.

A client without OAuth sign-in can send an existing developer key as a header instead. Keep it in the client's private configuration, never in chat:

• Claude Code: claude mcp add --transport http pulse-verity https://mcp.thepulse.markets/api/index/mcp --header "Authorization: Bearer pidx_your_key"
• Any client with remote MCP support: { "url": "https://mcp.thepulse.markets/api/index/mcp", "headers": { "Authorization": "Bearer pidx_your_key" } }

Add a developer key locally

A developer key enables catalogue access, batch reads and recorded prints, subject to your account's allowance. Sign up at thepulse.markets/developers (Developer plan, no charge; Continue with Google skips the email step), then create a key. Keep it in PULSE_API_KEY in your MCP client's private configuration; never share it in chat.

claude mcp add pulse-verity \

--env PULSE_API_KEY=pidx_your_key_here \ -- npx -y pulse-verity@1.3.6

For any stdio MCP client:

{

"mcpServers": { "pulse-verity": { "command": "npx", "args": ["-y", "pulse-verity@1.3.6"], "env": { "PULSE_API_KEY": "pidx_your_key_here" } } } }

Install locally in other clients

Claude hosted MCP plugin

The Claude plugin combines a guided price-check skill with the hosted HTTP MCP connection. Sign in through the host's OAuth flow using your own Verity developer account; this plugin does not need Node/npm or a local API-key environment. See the Claude plugin guide for setup, data handling and verification boundaries. The root stdio configuration remains for other clients. This plugin is separate from the Desktop MCPB. Source availability does not imply directory approval, publication or a successful authenticated connection.

Cursor marketplace package

This repository includes .cursor-plugin/plugin.json and mcp.json for Cursor's plugin loader. The plugin is pinned to pulse-verity@1.3.6 package with npx; Node.js 18 or newer is required. No platform engine code or private repository access is included.

The PULSE_API_KEY variable is optional and defaults to an empty string, so limited BTC, ETH and SOL samples work without a key. Configure your developer key through Cursor's plugin configuration to enable catalogue, batch and recorded-print requests. Never put a real key in these repository files.

Marketplace availability is subject to Cursor's review. The configuration below remains available for manual MCP installation.

Grok Build plugin

For a keyless sample task and the distinct Grok Bot / xAI API connection routes, see Use Pulse Verity with Grok.

Install directly from the public repository:

grok plugin install PulseBet/pulse-verity --trust

Start a new Grok Build session, then ask for the current Bitcoin index price. The plugin starts npx -y pulse-verity@1.3.6; Node.js 18 or newer and npm are required. Limited BTC, ETH and SOL samples work without an API key. To enable catalogue, batch and recorded-print requests, set PULSE_API_KEY in the environment that launches Grok Build, then start a new session. Get a developer key at [the dev