Pulse Verity MCP connector for AI agents

CALL ANY TOOL

9 tools for crypto index prices in Pulse Verity: read signed prices singly or in batches, pull candle history and recorded prints, verify signatures, list covered assets, and check plan and usage.

pulseveritymcp_get_account_status

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.

Parameters

Name

Type

Required

Description

—

No parameters required

pulseveritymcp_get_index_batch

Batch get index

pulseveritymcp_get_index_history

Get index history

pulseveritymcp_get_index_price

Get index price

pulseveritymcp_get_recorded_print

Print get recorded

pulseveritymcp_get_upgrade_options

Get upgrade options

pulseveritymcp_list_index_assets

List index assets

pulseveritymcp_submit_verity_feedback

Submit verity feedback

pulseveritymcp_verify_print

Print verify

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.

Parameters

Name

Type

Required

Description

at

string

Required

Timestamp from the print, unchanged

grade

string

Required

No description.

price

string

Required

No description.

signature

string

Required

ECDSA P-256 signature in base64

symbol

string

Required

Crypto ticker symbol, e.g. BTC, ETH, SOL

assetId

string

Optional

No description.

cadence

string

Optional

No description.

closeDay

string

Optional

No description.

confidence

string

Optional

No description.

dispersionBps

string

Optional

No description.

engine

string

Optional

No description.

interval

string

Optional

No description.

kid

string

Optional

Signing key identifier, when provided by the API

kind

string

Optional

No description.

priceText

string

Optional

Exact signed price text, when provided by the API; preserve unchanged

sig

string

Optional

No description.

sources

string

Optional

No description.

tier

string

Optional

No description.

v2

object

Optional

The v2 block from the print, unchanged: it signs the whole record, quality fields included

Build your Agent

Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.

import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Pulse Verity tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["pulseveritymcp"], toolNames: [
    "pulseveritymcp_get_index_price",
    "pulseveritymcp_get_index_history",
    "pulseveritymcp_verify_print"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Get the current signed ETH price, pull its 30 day history, and verify the print" }] });

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["pulseveritymcp"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Get the current signed ETH price, pull its 30 day history, and verify the print" }],
  tools,
});

// Execute the tool call with the user's vaulted Pulse Verity OAuth token
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["pulseveritymcp"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Get the current signed ETH price, pull its 30 day history, and verify the print" }],
  tools,
});

// Tool call runs with the user's vaulted Pulse Verity OAuth token
await sk.tools.executeTool(msg.content, "user_123");

import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["pulseveritymcp"] }, pageSize: 100,
});

const agent = new Agent({
  name: "crypto_data_agent",
  model: "gemini-2.5-pro",
  instruction: "Pulse Verity tools scoped to this user",
  tools,
});

await agent.run("Get the current signed ETH price, pull its 30 day history, and verify the print");

Try these prompts

Copy any prompt into your agent. Each maps directly to a Pulse Verity MCP tool. Click to copy, paste into your agent, done.

Signed prices

Copy the prompt

Copied

What is the current signed index price for BTC?

Copy the prompt

Copied

Get signed prices for BTC, ETH, and SOL in one request.

Copy the prompt

Copied

Which crypto symbols does Pulse Verity cover right now?

History and verification

Copy the prompt

Copied

Show daily candles for ETH over the last 30 days.

Copy the prompt

Copied

What was the recorded signed print for BTC at 12:00 UTC yesterday?

Copy the prompt

Copied

Verify this signed print and tell me whether the full record is valid.

Plan and feedback

Copy the prompt

Copied

What plan am I on and how many calls do I have left this month?

Copy the prompt

Copied

What upgrade options does Pulse Verity offer?

Copy the prompt

Copied

Report a stale price for SOL to the Pulse Verity team.

SEE HOW AUTH WORKS

Each user signs in to Pulse Verity once, and Scalekit stores and refreshes their tokens. Credentials stay vaulted, every call is scope checked, and every action is logged.

1

Authorize

Your user connects

Pulse Verity MCP

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

2

Store

Their

Pulse Verity MCP

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

3

Resolve

When your agent calls a

Pulse Verity MCP

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

4

Audit

Every

Pulse Verity MCP

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other finance and analytics connectors.

GTM and RevOps Teams

Competitive intelligence briefing agent

Scans Gong calls for competitor mentions, matches each one to its Notion battlecard, and DMs every affected rep a single Slack digest per cycle. Every call runs as the PMM who owns the briefing, never a shared bot.

GTM and RevOps Teams

Revenue forecast commentary

Pulls open pipeline from Salesforce and HubSpot, calculates coverage against quota, flags at-risk stages, posts commentary to Slack, and logs every snapshot to Google Sheets.

Test other agents

See the same per-user auth pattern across other finance and analytics connectors.

GTM

Competitive intelligence briefing agent

Scan Gong calls for competitor mentions, match each one to its Notion battlecard, and DM every affected rep a single Slack digest.

GTM

Revenue forecast agent

Score pipeline coverage against quota across Salesforce and HubSpot, post forecast commentary to Slack, log snapshots to Sheets.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared Pulse Verity token looks fine in a demo. In production every price lookup and verification looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.

// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Pulse Verity today. Ten connectors tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Pulse Verity as the user or through a shared service account?

As the user. Each user signs in to Pulse Verity once, and Scalekit stores and refreshes their tokens. Every price read and verification in your audit trail is attributed to that user, not a shared service account.

Where is the Pulse Verity OAuth token stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.

Can I limit what the agent does in Pulse Verity?

Yes. Eight of the 9 tools are read-only. Filter by tool name in listScopedTools to expose only what you want, for example the price and history tools without pulseveritymcp_submit_verity_feedback, which writes a report for human triage. Scalekit also enforces scope checks before every API call.

What happens when a user revokes Pulse Verity access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Do Pulse Verity calls count against a usage allowance?

Yes, the monthly allowance is account-wide, so every connected app on the account shares it. pulseveritymcp_get_account_status reports your plan, calls used, and calls remaining, and it does not count toward the allowance.

Pulse Verity MCP server for AI agents

Tools your crypto data agent reaches for on Pulse Verity, scoped per user.