Pulse Verity logo

Pulse Verity

Read signed crypto index prices, verify receipts, discover assets, and retrieve settlement prints through MCP.

Install Pulse Verity

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "pulse-verity": {
      "command": "npx",
      "args": [
        "-y",
        "pulse-verity"
      ],
      "env": {
        "PULSE_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 9 tools correctly (2d ago).

Overview

The pulse-verity MCP server connects AI agents to the Pulse Verity Index for signed, verifiable cryptocurrency index prices. It provides read-only price, batch, catalog, settlement-print, and local verification tools, plus a private feedback submission tool. Run it locally with npx or connect to the hosted MCP endpoint; a key is optional for BTC, ETH, and SOL samples but required for broader data access. Reach for it when an agent needs verifiable index data rather than trading, transfers, or price updates.

Use cases

  • Read current signed BTC, ETH, or SOL index prices
  • Verify returned crypto price receipts locally
  • Query batches of up to 100 index symbols
  • Find a recorded settlement print near a timestamp
  • Submit private API reports for human review

Key features

  • Signed cryptocurrency index prices
  • Batch reads with per-symbol errors
  • Paginated asset catalog discovery
  • Recorded settlement-print lookup
  • Local public-key verification
  • Private feedback reports

Tools9

What Pulse Verity lets your agent do. Expand a tool for its parameters.

Verified live~3.7k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

9/9 checks healthy over the last 54d

What it can do

From the 9 tools this server returned when we ran it; 9 declare their own safety hints.

Handles credentials · 2Makes network requests · 9Read-only tools · 9
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age60 days
Maintainers1

Observed 2026-10-28 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · pulse-verity (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars4Stargazers on the source repository.
Last commit12d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed9Callable tools this server registers over MCP.

How Pulse Verity works

What pulse-verity MCP server does

The pulse-verity MCP server gives an AI agent access to the Pulse Verity Index, which provides signed cryptocurrency index prices. Its primary operations read current values, retrieve several symbols at once, browse the available asset catalog, and find a recorded signed print near a specified time.

The package also includes local verification for price receipts and their signed quality fields using the published public key. This lets an agent check a returned print without sending the verification request through an authenticated service. A separate feedback operation submits a private API report for human review and returns a tracking receipt.

Only feedback changes remote state, and it does not trade, transfer funds, or modify prices. The package does not include Pulse platform engine code.

Tools and capabilities

The available tools are:

  • get_index_price(symbol) returns the current signed index value.
  • get_index_batch(symbols) accepts 1–100 symbols and reports successful signed rows alongside errors for individual symbols.
  • list_index_assets(limit, offset, band?, status?) returns one catalog page, including coverage and measured cadence.
  • get_settlement_print(symbol, at) finds the recorded signed print nearest to a requested moment.
  • verify_print(print) checks a price and its signed quality fields locally against the published public key.
  • submit_verity_feedback(report) sends a private report for human review and returns a receipt.

The pulse-verity MCP server can start without configuration. In that mode, the free sample supports BTC, ETH, and SOL current-price requests. A free developer key expands access to catalog, batch, and settlement-print requests, subject to usage limits. Signature verification does not require a key.

Setup and configuration

For local use, run npx -y pulse-verity through an MCP client's stdio configuration. Set PULSE_API_KEY in the client's private environment when keyed access is needed. The key is optional for the sample data and should not be placed in repository files or chat messages.

The hosted endpoint is https://mcp.thepulse.markets/api/index/mcp. Remote clients can authenticate with a bearer developer key, while Claude's hosted connection uses OAuth 2.1 with dynamic registration and PKCE. Hosted calls count against the key in the same way as REST calls.

The repository documents configurations for Claude Desktop, Cursor, Grok Build, Gemini CLI, Codex CLI, Windsurf, VS Code, and Claude Code. Cursor, Grok Build, and Gemini CLI package or launch the pinned pulse-verity@1.3.1 release; those local routes require Node.js and npm. Claude Desktop can use the supplied .mcpb bundle.

Limitations and notes

Without a key, only the BTC, ETH, and SOL sample price path is available. Catalog, batch, and settlement-print access depends on a free developer key and service limits. Feedback additionally requires a developer key and an enabled feedback service.

The local process makes GET requests to Pulse's MCP and index endpoints for data and public-key reads. Feedback uses POST. A configured key is sent only to the Pulse origin for keyed requests. The documented server does not read project files or send separate telemetry.

The pulse-verity MCP server is for index data and verification; it is not a trading or fund-transfer interface. Hosted plugin and marketplace availability can depend on the relevant client or directory review process.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Pulse Verity

pulse-verity is an MCP server that connects AI agents to the Pulse Verity Index for signed cryptocurrency index prices. Its main tools read current prices, query batches, list assets, retrieve settlement prints, verify signed receipts locally, and submit private feedback reports. It cannot trade, transfer funds, or change prices.

Run `npx -y pulse-verity` through your MCP client's stdio configuration. Claude Desktop can open the provided `.mcpb` bundle, and remote clients can use the hosted endpoint at `https://mcp.thepulse.markets/api/index/mcp`. Node.js and npm are needed for the npx-based installations.

No key is needed for BTC, ETH, and SOL sample price requests or signature verification. Set `PULSE_API_KEY` for catalog, batch, and settlement-print access, subject to usage limits. Feedback also requires a developer key and an enabled feedback service.

Yes, pulse-verity works with Cursor through its plugin package or a manual stdio MCP configuration. The Cursor plugin uses the pinned `pulse-verity@1.3.1` package and requires Node.js 18 or newer. Configure `PULSE_API_KEY` in Cursor to access non-sample requests.

Yes, the `verify_print(print)` tool verifies a price and its signed quality fields locally with the published public key. This verification path works without an API key and does not require sending the verification request through an authenticated service.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewPulse Verity AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/pulse-verity?style=directory)](https://allmcps.com/mcp/pulse-verity)
HTML Embed
<a href="https://allmcps.com/mcp/pulse-verity"><img src="https://allmcps.com/api/badge/pulse-verity?style=directory" alt="Pulse Verity on AllMCPs" /></a>