Verify Signed Crypto Index Prices with MCP (Pulse Verity)

Verify Signed Crypto Index Prices with MCP (Pulse Verity)

Get a cryptographically VERIFIED crypto index price in n8n—this manual workflow fetches a signed index record from Pulse Verity and verifies the full record signature before outputting a confirmed result.

What this workflow does

This n8n workflow is designed to prevent accidental changes to signed crypto index data. When you run it manually, it:

• Accepts a crypto symbol (e.g., BTC) and validates it matches the required 1–20 character A–Z / 0–9 format.
• Calls the Pulse Verity Index hosted MCP endpoint (get_index_price) to retrieve a signed price record for the requested symbol.
• Preserves the returned signed record exactly—including canonical fields and signature—so the record is verified as-is.
• Verifies the exact preserved record by calling the same Pulse Verity Index MCP endpoint (verify_print).
• Stops with an error unless verification confirms a full-record match.
• Outputs a VERIFIED payload containing the signed fields, the signed print, and verification metadata.

Use cases

• Operators that need tamper-evident index prices for dashboards or alerts.
• SaaS workflows that must validate index data before storing or publishing it.
• Automation engineers integrating Pulse Verity pricing feeds into n8n with signature verification.

Technical details

• Requires: n8n with MCP Client 1.1, Edit Fields 3.4, and Code 2.
• Setup: Create a developer key at https://thepulse.markets/developers and store it as an n8n Bearer Auth credential.
• MCP calls: Uses Pulse Verity Index endpoint functions get_index_price and verify_print.
• Customization: Change the example symbol (e.g., BTC) in the “Choose symbol” step.

Built for secure, verified crypto index price retrieval using n8n automation and Pulse Verity MCP.