`pulse_asset_catalog`

Pack: pulse-verity · Endpoint: https://gateway.pipeworx.io/pulse-verity/mcp

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/pulse_asset_catalog for the schema, then POST the same URL with its arguments for the data.

Which crypto assets the Pulse Verity Index covers, at what grade, across how many venues, and how fast each one actually updates — cadence measured per asset from its own update intervals rather than from a poll schedule. Filter by coverage band (real-time, five-second, ten-second, slow, unavailable) or status (consensus, blended, indicative). Call this to find out whether a symbol is covered, and how thin it is, before quoting it. NOTE: these rows are UNSIGNED, including their prices — read a verifiable number through pulse_signed_price. Requires a Pulse API key via _apiKey. Example: pulse_asset_catalog({ limit: 5 }).

Parameters

Name	Type	Required	Description
`limit`	number	no	Rows to return, max 500 (default 50).
`offset`	number	no	Row offset for paging.
`band`	string	no	Cadence band: real-time, five-second, ten-second, slow, unavailable.
`status`	string	no	Coverage grade: consensus, blended, indicative.

Example call

Arguments

{
  "limit": 5
}

curl

curl -X POST https://gateway.pipeworx.io/pulse-verity/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"pulse_asset_catalog","arguments":{"limit":5}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('pulse_asset_catalog', {
  "limit": 5
});

More examples

{
  "limit": 20,
  "status": "consensus"
}

Connect

Add this to your MCP client config, or use one-click install buttons:

{
  "mcpServers": {
    "pulse-verity": {
      "url": "https://gateway.pipeworx.io/pulse-verity/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

pulse_asset_catalog