Coinversaa Pulse

Coinversa Pulse

Coinversa Pulse is a read-only crypto intelligence MCP skill for AI agents.

It lets MCP-compatible clients query Hyperliquid market data, trader behavior, position lifecycles, execution quality, cohort analytics, liquidation data, open interest, builder dex markets, HIP-4 outcome contracts, cross-market asset exposure, and wallet-level trading history.

This skill is designed for market research and analytics only.

It does not place trades, sign transactions, manage wallets, move funds, approve agents, custody assets, or request private keys.

For current wallet and trade coverage numbers, call pulse_global_stats.

Coinversa indexes Hyperliquid's clearinghouse directly and computes analytics that are difficult to obtain from public web sources or generic blockchain APIs.

Builder dex support: 369+ markets across 8 dexes, including commodities, stocks, indices, and perps.

HIP-4 support: outcome-contract discovery, question metadata, recent fills, settlements, daily volume, top outcome traders, wallet outcome history, outcome/perp trader overlap, and current open perp-position context for outcome holders.

Safety Boundary: Read-Only Analytics Only

Coinversa Pulse is a market-data and analytics MCP server.

This skill does not expose any tools for:

• Trading
• Order placement
• Wallet signing
• Transaction signing
• Fund movement
• Token transfers
• Account approvals
• Hyperliquid agent wallet approval
• Backend signer approval
• Custody or control of assets
• Managing margin or leverage settings

No private key, seed phrase, wallet signature, exchange credential, or Hyperliquid account approval is required to use this skill.

Users should not approve a Hyperliquid agent wallet, backend signer, trading agent, or any account-level trading permission for this MCP skill. No such approval is needed for Coinversa Pulse.

If Coinversa offers trading or execution functionality through another product, app, or integration, that functionality is outside the scope of this MCP skill and should be reviewed separately.

Data & Privacy

Coinversa Pulse sends MCP tool requests to Coinversa's hosted API at https://api.coinversa.ai by default.

Depending on the tool used, requests may include:

• Market symbols
• Wallet addresses
• Cohort names
• HIP-4 outcome IDs
• Time windows
• API-key-authenticated usage metadata
• Requested analytics parameters

Do not submit private, sensitive, or nonpublic information unless you are comfortable sending it to Coinversa's API.

Coinversa Pulse does not require private keys, seed phrases, wallet signatures, exchange credentials, or Hyperliquid account approvals.

The hosted remote server (https://mcp.coinversa.ai/mcp) is a stateless bridge to the Coinversa API. It stores OAuth client registrations, SHA-256-hashed access/refresh tokens, and the key grant behind each token (a key id when you connected through the developer portal, or the pasted key encrypted at rest with AES-256-GCM). It does not store conversation content, and it does not persist or log tool arguments or results beyond the request in flight.

Policies: coinversa.ai/privacy and coinversa.ai/terms. Support: chat@coinversaa.ai.

Setup

An API key is required for every tool. There is no keyless tier.

The canonical client guide is docs.coinversa.ai/mcp/setup; the snippets below mirror it.

Hosted Remote MCP (OAuth 2.1)

https://mcp.coinversa.ai/mcp

Streamable HTTP, stateless (POST /mcp). Authentication is OAuth 2.1 with PKCE and dynamic client registration only — paste the URL, leave auth/header fields empty, and the client opens a Coinversa authorization page. There you sign in (or sign up; new accounts get 14 days of Pro) and pick a key, or paste an existing cvsa_ key, then click Authorize. API keys sent in HTTP headers are not accepted by the hosted endpoint.

Claude.ai (web)

Open claude.ai/customize/connectors?modal=add-custom-connector, set Name Coinversa and URL https://mcp.coinversa.ai/mcp, leave the auth fields empty, then connect and authorize in the browser.

Claude Desktop

Claude Desktop is stdio-only, so use the mcp-remote shim. Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS), %APPDATA%\Claude\claude_desktop_config.json (Windows), or ~/.config/Claude/claude_desktop_config.json (Linux):

{
  "mcpServers": {
    "coinversa": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.coinversa.ai/mcp"]
    }
  }
}

Fully quit and reopen Claude Desktop; authorize in the browser window that opens.

Cursor

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "coinversa": {
      "url": "https://mcp.coinversa.ai/mcp"
    }
  }
}

Claude Code

claude mcp add --transport http coinversa https://mcp.coinversa.ai/mcp

Then run /mcp and authenticate coinversa.

ChatGPT, Perplexity, other remote clients

Add a custom connector with URL https://mcp.coinversa.ai/mcp and no headers.

Local stdio MCP (API key)

For stdio-only clients, or when you prefer to hold the key yourself. Get a key at developers.coinversa.ai/keys.

{
  "mcpServers": {
    "coinversa": {
      "command": "npx",
      "args": ["-y", "@coinversaa/mcp-server@0.11.1"],
      "env": {
        "COINVERSAA_API_KEY": "cvsa_your_key_here"
      }
    }
  }
}

Shell equivalent: COINVERSAA_API_KEY=cvsa_... npx -y @coinversaa/mcp-server@0.11.1

OpenClaw

openclaw skill install coinversaa-pulse

Access Tiers

All tools require an API key. Backend tiering is enforced by the Coinversa API.

Rate-limit headers may include X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-RateLimit-Tier, and X-RateLimit-Daily-Remaining.

Builder Dex Markets

Hyperliquid supports multiple builder dexes beyond the native perps exchange. Each dex has its own markets, collateral token, and symbol format.

Coinversa Pulse exposes analytics and market-data views for these markets.

Native Hyperliquid markets use simple symbols like BTC, ETH, and SOL.

Builder dex markets use prefixed symbols like xyz:GOLD, cash:TSLA, and hyna:SOL.

Use list_markets to discover all available symbols and the dex each symbol belongs to.

Coinversa Pulse only exposes analytics and market-data views. It does not place orders, sign transactions, approve agent wallets, manage margin, or execute trades.

Assets & Cross-Market Taxonomy

The same underlying asset can appear under different tickers on different venues. Coinversa exposes a canonical asset registry so agents and API consumers do not have to reinvent the grouping logic.

Known synonyms:

Wrappers like WBTC, WETH, stETH, and wstETH are not aggregated with their native tickers by default because they can have meaningfully different risk and liquidity profiles.

Asset tools accept both canonicals and synonyms. For example, list_asset({ canonical: "PAXG" }) and list_asset({ canonical: "GOLD" }) return the same canonical asset view.

Key fields from pulse_cross_market_asset:

HIP-4 Outcome Contracts

HIP-4 outcome contracts are prediction-market style side tokens indexed from Hyperliquid.

Outcome side coins use:

#<encoding>

where:

encoding = 10 * outcomeId + side

Side tokens use:

+<encoding>

Use HIP-4 tools when users ask about outcomes, prediction markets, questions, settlements, side-token fills, outcome trader leaderboards, overlap between outcome traders and perp traders, or whether outcome holders currently have open perp exposure to the same underlying asset.

Builder Analytics Tools

Builders (frontends, bots, HIP-3 dexes) charge per-order builder fees on Hyperliquid. Revenue figures are exact, from Hyperliquid's on-chain cumulative builder-fee ledger; volume/user/fill detail comes from order-fill attribution and slightly undercounts because trigger-order (stop/TP) fills are not yet attributed — each response carries a dataNotes explanation and a verified ledger-block stamp. builderName comes from a curated registry and is omitted when unknown. Tier labels on builder_traders / builder_cohorts are ALL-TIME exchange-wide legacy slugs, not the 30d-rolling pulse cohort tiers.

Tools

103 total read-only analytics tools:

• 43 existing Hyperliquid market, trader, cohort, risk, cross-market asset, and live analytics tools
• 12 HIP-4 outcome-contract tools
• 27 position-lifecycle, execution-quality, trader-archetype, market-structure, comparison, and recent-cohort tools
• 9 entity-resolution, exchange-aggregate, PnL-leader, and plan-introspection tools
• 12 builder-analytics tools (ledger-exact revenue leaderboard/profile, traders, fills, cohorts, retention, overlap, user lifecycle, journey economics, activity heatmap, order intent, and per-wallet builder lookup)
• All tools require a Coinversa API key
• The Coinversa API enforces tier-specific access

Risk Tools Freshness

Syncer-backed risk tools are best treated as beta recent-intelligence tools.

These include:

• live_risk_overview
• live_coin_risk_snapshot
• live_coin_risk_history
• live_mark_dislocations
• live_recent_liquidations
• live_liquidation_summary
• live_oi_history
• live_cohort_bias_history

For venue-reported open interest, use live_official_oi, which is pulled from Hyperliquid's Info API, as a cross-check.

These tools are best for research, LLM training, liquidation analysis, open interest trend work, crowding detection, market-structure analysis, and recent risk analysis.

They are best queried over recent windows such as 7d or 30d.

Freshness depends on sync coverage and may lag real time.

Do not treat syncer-backed analytics as guaranteed live execution truth or exact historical accounting.

Position Lifecycles & Execution Quality

For new wallet-level position analysis, prefer the 0.8 lifecycle tools over the legacy closed-position tools.

A lifecycle is one reconstructed position from open to close, including scale-ins, scale-outs, entry/exit VWAP, realized PnL, fees, hold duration, liquidation state, and related fills. Most lifecycle routes use a 90-day rolling window and exclude spot pairs by default unless an includeSpot option is present.

Recommended workflow:

Legacy tools:

• pulse_trader_closed_positions
• pulse_trader_closed_position_stats
• pulse_recent_closed_positions

Use them when the user explicitly asks for the old closed-position payload or a global recent-closed feed. Otherwise, prefer lifecycle tools.

Tool Groups

Pulse — Trader Intelligence

• pulse_global_stats — Global Hyperliquid stats: total traders, trades, volume, PnL, and data coverage period.
• list_markets — Market discovery for native and builder dex symbols.
• pulse_market_overview — Deprecated alias for list_markets.
• pulse_leaderboard — Ranked trader leaderboard.
• pulse_hidden_gems — Underrated high-performing traders.
• pulse_most_traded_coins — Most actively traded coins.
• pulse_biggest_trades — Biggest winning or losing trades.
• pulse_recent_trades — Biggest recent trades in a time window.
• pulse_token_leaderboard — Top traders for a specific coin.
• pulse_coin_alpha_map — Winner/loser profit pools per coin.
• pulse_hour_profitability — PnL heatmap by UTC close hour.
• pulse_market_concentration — How concentrated alpha is across wallets.
• pulse_style_distribution — PnL split by hold-duration style.

Pulse — Trader Profiles

Tools taking address expect a full Ethereum address: 0x plus 40 hex characters.

• pulse_trader_profile
• pulse_trader_performance
• pulse_trader_demo
• pulse_trader_lifecycle_summary
• pulse_trader_lifecycles
• pulse_lifecycle
• pulse_wallet_drawdown_curve
• pulse_trader_trades
• pulse_trader_daily_stats
• pulse_trader_token_stats
• pulse_trader_closed_positions — legacy; prefer pulse_trader_lifecycles.
• pulse_trader_closed_position_stats — legacy; prefer pulse_trader_lifecycle_summary.

Pulse — Lifecycle Discovery

• pulse_max_pain_events
• pulse_perfect_exits
• pulse_backstop_events
• pulse_survivors
• pulse_anti_survivors
• pulse_persistent_winners
• pulse_capital_titans
• pulse_one_month_wonders
• pulse_newcomer_whales
• pulse_coin_kings
• pulse_top_liquidators
• pulse_lethal_coins
• pulse_compare

Pulse — Cohort Intelligence

PnL tiers (by profitability, best to worst):

Size tiers (by volume, largest to smallest):

Tool inputs accept both slug vocabularies (new slugs are normalized before the API call). API responses currently still emit legacy slugs.

Tools:

• pulse_cohort_summary
• pulse_cohort_positions
• pulse_cohort_trades
• pulse_cohort_history
• pulse_cohort_bias_history
• pulse_cohort_performance_daily
• pulse_cohort_recent_positions
• pulse_cohort_recent_trades
• pulse_cohort_recent_lifecycle_stats
• pulse_cohort_recent_top_positions
• pulse_cohort_recent_alpha_concentration

Market — Live Data

• market_price
• market_positions
• market_orderbook
• market_historical_oi
• market_recent_candles

Live — Real-Time Analytics

• live_liquidation_heatmap
• live_risk_overview
• live_coin_risk_snapshot
• live_coin_risk_history
• live_mark_dislocations
• live_recent_liquidations
• live_liquidation_summary
• live_long_short_ratio
• live_cohort_bias
• live_oi_history
• live_official_oi
• live_cohort_bias_history
• pulse_recent_closed_positions

Builder Analytics

Builder addresses are 0x plus 40 hex characters, like wallets. See the Builder Analytics Tools table above for tiers and inputs.

• builder_leaderboard — Builders ranked by exact ledger revenue with attributed metrics and deltas.
• builder_profile — One builder's revenue, daily series, top coins, and user profitability.
• builder_traders — A builder's attributed wallets with all-time cohort tiers.
• builder_fills — Individual attributed fills through a builder.
• builder_cohorts — A builder's user base split by behavioral tier.
• builder_retention — Monthly new-user retention triangle.
• builder_overlap — Which other builders share this builder's users.
• trader_builders — Every builder one wallet trades through.
• builder_journey — How fast and how unevenly a builder monetizes a new user.
• builder_lifecycle — Where every wallet that ever traded via a builder stands today.
• builder_heatmap — 7x24 UTC weekday-by-hour activity grid over the trailing 12 weeks.
• builder_orders — What a builder's users intend at placement time, before anything fills.

Example Prompts

• "What are the top 5 traders on Hyperliquid by PnL?"
• "Show me what the apex tier is holding right now."
• "What are the biggest trades in the last 10 minutes?"
• "Find underrated traders with 70%+ win rate."
• "Where are the BTC liquidation clusters?"
• "Show me the exchange-wide risk overview on Hyperliquid this week."
• "Which coin looks the most crowded right now?"
• "Show me ETH liquidation events from the last 7 days."
• "Give me BTC risk history with OI, liquidations, and cohort rotation."
• "Are smart money traders long or short ETH right now?"
• "What markets are available on the xyz dex?"
• "What's the price of xyz:GOLD?"
• "Which venues trade gold?"
• "Is PAXG the same as GOLD?"
• "Total open interest on BTC across all dexes?"
• "Which HIP-4 outcome contracts are most active today?"
• "Show me recent trades for outcome 123."
• "Which HIP-4 outcomes settled recently?"
• "Who are the top HIP-4 outcome traders this week?"
• "For outcome 25, are Yes traders already long BTC or mostly prediction-native?"
• "Did outcome traders overlap with perp traders over the last 7 days?"

Security Notes

Coinversa Pulse is intentionally read-only.

When installing any MCP server:

• Prefer the hosted OAuth endpoint; it keeps the API key out of client config files.
• Install from the official package source.
• Use the pinned package version shown in this document.
• Use a separate API key for this MCP skill where possible.
• Rotate API keys if they may have been exposed.
• Do not provide private keys, seed phrases, wallet signatures, exchange credentials, or account approvals.
• Review the tools exposed by the MCP client before use.
• Remove the MCP server when no longer needed.

Links

• Website: coinversa.ai
• MCP setup guide: docs.coinversa.ai/mcp/setup
• API Docs: coinversa.ai/developers
• Privacy: coinversa.ai/privacy · Terms: coinversa.ai/terms
• GitHub: github.com/coinversaa/mcp-server
• npm: @coinversaa/mcp-server
• Support: chat@coinversaa.ai

Built by Coinversa — crypto intelligence for AI agents.