# Coinversaa Pulse

> Read-only crypto intelligence for AI agents. 103 tools (OAuth 2.1 on the hosted endpoint, API key for local stdio) for Hyperliquid trader analytics, builder-fee revenue analytics, position lifecycles with MAE/MFE execution quality, trader archetype discovery, behavioral cohorts, HIP-4 outcome contracts, outcome/perp position context, syncer-backed risk data, live market data, builder dex markets, commodities, stocks, indices, cross-market asset taxonomy, liquidation heatmaps, official per-dex OI, and whale tracking across the full Hyperliquid wallet universe. This skill does not trade, sign transactions, move funds, request private keys, custody assets, or require wallet approvals. Call pulse_global_stats for live coverage totals.

- Skill: `coinversaa/coinversaa-pulse` (Agent Skill, multi-file: 12 files)
- Install (CLI): `npx skillmds@latest add coinversaa/coinversaa-pulse`
- Raw SKILL.md: https://api.skillmd.com/api/skills/coinversaa/coinversaa-pulse/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- License: MIT
- Author: coinversaa (https://skillmd.com/u/coinversaa)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/coinversaa/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](https://coinversa.ai/privacy) and [coinversa.ai/terms](https://coinversa.ai/terms). Support: [chat@coinversaa.ai](mailto: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](https://docs.coinversa.ai/mcp/setup); the snippets below mirror it.

| Method | Where | Auth | Best for |
|--------|-------|------|----------|
| Hosted Remote MCP (recommended) | `https://mcp.coinversa.ai/mcp` | OAuth 2.1 in the browser | Claude.ai, Claude Desktop, Claude Code, Cursor, ChatGPT, Perplexity, any Streamable HTTP client |
| Local stdio MCP | `npx -y @coinversaa/mcp-server@0.11.1` | `COINVERSAA_API_KEY` env var | Codex and other stdio-only clients, development |

### Hosted Remote MCP (OAuth 2.1)

```text
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](https://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):

```json
{
  "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`:

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

#### Claude Code

```bash
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](https://developers.coinversa.ai/keys).

```json
{
  "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

```bash
openclaw skill install coinversaa-pulse
```

---

## Access Tiers

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

| Tier | Typical access | Requests/min | Daily cap | Monthly cap |
|------|----------------|--------------|-----------|-------------|
| Free API key | Public discovery, market data, selected HIP-4 discovery routes | 30 | 1,000 | - |
| Starter | Free routes plus selected trader and HIP-4 analytics | 120 | 2,000 | 50,000 |
| Pro | Starter plus deeper risk, historical, official OI, and overlap analytics | 600 | 20,000 | 500,000 |
| Enterprise | Custom access and limits | Custom | Custom | Custom |

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.

| Dex | What it trades | Collateral | Example symbols |
|-----|----------------|------------|-----------------|
| native HL | Core perps, crypto | USDC | BTC, ETH, SOL, HYPE |
| `xyz` | Commodities, stocks, indices | USDC | xyz:GOLD, xyz:SILVER, xyz:TSLA |
| `flx` | Perps | USDH | flx:BTC, flx:ETH |
| `vntl` | Perps | USDH | vntl:ANTHROPIC, vntl:BTC |
| `hyna` | Perps | USDE | hyna:SOL, hyna:BTC |
| `km` | Energy and commodities | USDH | km:OIL, km:NATGAS |
| `abcd` | Misc markets | USDC | abcd:BITCOIN |
| `cash` | Stocks and equities | USDT0 | cash:TSLA, cash:AAPL |

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.

| Concept | Meaning |
|---------|---------|
| Canonical | The economic-exposure identifier. Example: `GOLD` means gold exposure regardless of venue or ticker. |
| Symbol | What a specific venue lists it as. Examples: `xyz:GOLD`, `hyna:PAXG`, `BTC`, `flx:BTC`. |

Known synonyms:

| Synonym ticker | Canonical | Reason |
|----------------|-----------|--------|
| `PAXG` | `GOLD` | Paxos-issued gold-backed token |
| `XAUT` | `GOLD` | Tether Gold |
| `XAGT` | `SILVER` | Silver-backed token |

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.

| User question | Recommended tool |
|---------------|------------------|
| "What markets exist on the xyz dex?" | `list_markets` |
| "What price is xyz:GOLD right now?" | `market_price` |
| "What assets are available?" | `list_assets` |
| "What venues is GOLD on?" | `list_assets` or `list_asset` |
| "Tell me about PAXG." | `list_asset` |
| "Where does BTC trade?" | `list_asset` |
| "Is gold more crowded on xyz or hyna?" | `pulse_cross_market_asset` |
| "Total OI on BTC across all dexes?" | `pulse_cross_market_asset` |
| "Do venues disagree on ETH direction?" | `pulse_cross_market_asset` |

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`:

| Field | Meaning |
|-------|---------|
| `aggregate.netBias` | Value from `-1` to `1`. Positive means long-heavy. Negative means short-heavy. Magnitude indicates directional conviction. |
| `aggregate.biasRange` | Spread between venues. High values, especially above `0.3`, suggest venues disagree meaningfully. |
| `asset.synonyms` | Tickers mapped into the canonical asset. Useful for explaining that gold may trade as `GOLD`, `PAXG`, or another symbol depending on venue. |
| `venues` | Per-venue breakdown sorted by open interest descending. The first venue is usually the dominant venue. |

---

## HIP-4 Outcome Contracts

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

Outcome side coins use:

```text
#<encoding>
```

where:

```text
encoding = 10 * outcomeId + side
```

Side tokens use:

```text
+<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.

| Tool | Tier | Inputs | Backend route | What it returns / when to use |
|------|------|--------|---------------|-------------------------------|
| `hip4_outcomes` | Free API key | `hours` 1-168, default 24 | `GET /hip4/outcomes` | Recently active outcomes with `outcomeId`, optional question metadata, parsed `priceBinary`, side tokens, coin keys, asset IDs, fills, unique wallets, notional USDH, first/last traded. Use to discover active prediction markets. |
| `hip4_outcome` | Free API key | `outcomeId` | `GET /hip4/outcomes/{outcome_id}` | Detail for one outcome ID from mainnet launch onward. Returns the same outcome shape as discovery, including fallback side tokens if metadata is unavailable. |
| `hip4_outcome_summary` | Starter+ | `outcomeId` | `GET /hip4/outcomes/{outcome_id}/summary` | Two-sided aggregate: side 0/1 contracts, side notional USDH, total notional, realized PnL, fills, unique wallets, first/last traded. |
| `hip4_outcome_recent_trades` | Free API key | `outcomeId`, `hours` 1-168 default 24, `limit` 1-500 default 100 | `GET /hip4/outcomes/{outcome_id}/recent-trades` | Recent real fills only, excluding settlement, pair-redeem, and auction-phase fills. Returns trade time, wallet, `coin`, `sideIndex`, side label, `dirId`, price, size, PnL, and fee. |
| `hip4_questions` | Free API key | none | `GET /hip4/questions` | Hyperliquid `outcomeMeta` question catalog: question IDs, names, descriptions, fallback outcome, named outcome IDs, settled named outcomes, and parsed fields such as class, underlying, expiry, period, and price thresholds. |
| `hip4_recent_settlements` | Free API key | `hours` 1-720 default 168, `limit` 1-200 default 50 | `GET /hip4/settlements/recent` | Recent settlements with outcome ID, settlement time, winning side when determinable, winner/loser fill counts, total winner payout, and total loser loss. |
| `hip4_daily_volume` | Free API key | `days` 1-60, default 14 | `GET /hip4/daily-volume` | Daily trajectory since the requested cutoff: fills, unique trades, unique wallets, contracts, and notional USDH. Use for adoption/activity trend questions. |
| `hip4_most_active` | Free API key | `hours` 1-168 default 24, `limit` 1-50 default 10 | `GET /hip4/most-active` | Top outcomes by recent fill count, with metadata and side tokens when available. Use to rank current outcome-market activity. |
| `hip4_top_traders` | Starter+ | `days` 1-30 default 7, `limit` 1-100 default 25 | `GET /hip4/top-traders` | Outcome trader leaderboard: address, fills, distinct outcomes, total contracts, total notional USDH, and realized PnL. |
| `hip4_trader_outcomes` | Starter+ | `address`, `days` 1-365 default 30 | `GET /hip4/trader/{address}/outcomes` | One wallet's outcome history: outcome ID, side index, side token, fills, net shares, gross bought/sold USDH, realized PnL, first/last traded. |
| `hip4_cross_product_overlap` | Pro+ | `days` 1-30 default 7 | `GET /hip4/cross-product/overlap` | Counts HIP-4 outcome traders, perp traders, overlap count, and overlap percentage. Use to answer whether outcome activity is isolated or shared with perp traders. |
| `hip4_perp_position_context` | Pro+ | `outcomeId`, `days` 1-60 default 14, `limit` 1-100 default 25 | `GET /hip4/outcomes/{outcome_id}/perp-position-context` | Joins current net-positive outcome holders to currently open perp positions on the same underlying. Returns side-level open-position overlap, long/short counts, net underlying position, underlying notional, aligned vs hedge counts, prediction-native counts, and top wallets with signal labels. Use to answer whether outcome traders are directionally exposed, hedged, or prediction-native. |

---

## 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.

| Tool | Tier | Inputs | Backend route | What it returns / when to use |
|------|------|--------|---------------|-------------------------------|
| `builder_leaderboard` | Starter+ | `period` day/week/month default week, `limit` 1-100 default 50, `offset` 0-1000 default 0 | `GET /builders/leaderboard` | Builders ranked by exact ledger revenue, with attributed volume/users/fills, prev-window deltas, and the most common requested fee rate (`feeTenthsBp`). "Which builders earn the most?" |
| `builder_profile` | Starter+ | `builder` 0x-hex, `period` default month, `topCoins` 1-50 default 10 | `GET /builders/{builder}/profile` | One builder: ledger revenue, first/last fee accrual, fee tokens, daily attributed series with biggest day, top coins, total vs all-time-profitable users. 404 if the address has no ledger revenue. |
| `trader_builders` | Starter+ | `address` 0x-hex, `since` default 30d (clamped 90d) | `GET /trader/{address}/builders` | Every builder a wallet trades through, ordered by fees paid, with fills, volume, and first/last seen in the window. |
| `builder_traders` | Pro+ | `builder` 0x-hex, `period` default week, `sort` builderFee/volume/pnl, `limit` 1-500 default 50, `offset` | `GET /builders/{builder}/traders` | The builder's attributed wallets with PnL, fees, volume, equity, and all-time `pnlTier`/`sizeTier` labels (null if untracked). |
| `builder_fills` | Pro+ | `builder` 0x-hex, `since` default 24h (clamped 90d), optional `coin` and `address` filters, `limit` 1-500, `offset` | `GET /builders/{builder}/fills` | Individual attributed fills: time, wallet, coin, marketType (perp/spot/hip4), side, price, size, volume, PnL, builder fee, oid/tid. |
| `builder_cohorts` | Pro+ | `builder` 0x-hex, `period` default week | `GET /builders/{builder}/cohorts` | User-base composition by all-time PnL and size tier (largest first, incl. `untracked`), each with users, share, fees, volume, PnL, fills. |
| `builder_retention` | Pro+ | `builder` 0x-hex (no other params) | `GET /builders/{builder}/retention` | Monthly retention triangle, last 12 calendar months, oldest first: `newWallets` plus `activeWallets[]` per subsequent month (orders plane — counts can exceed attributed-fill user counts). |
| `builder_overlap` | Pro+ | `builder` 0x-hex, `period` default week | `GET /builders/{builder}/overlap` | Top 10 other builders sharing this builder's active users: sharedUsers, share, and fees those users paid to the other builder. |
| `builder_journey` | Pro+ | `builder` 0x-hex (no other params) | `GET /builders/{builder}/journey` | Revenue ramp of the trailing-year acquisition cohort (>= 3 lifetime attributed fills): avg/median lifetime fees per wallet, whale `concentration`, days to peak / 50% / 75% of lifetime revenue, and a peak-day bucket split. |
| `builder_lifecycle` | Pro+ | `builder` 0x-hex (no other params) | `GET /builders/{builder}/lifecycle` | One snapshot of the LIFETIME user base (orders plane) split into five mutually exclusive statuses — active, cooling, switched, dormant, movedOn — plus trueRetention, churn, competitiveLoss, and the fees switched wallets paid rivals in 30d. |
| `builder_heatmap` | Pro+ | `builder` 0x-hex (no other params) | `GET /builders/{builder}/heatmap` | Fixed trailing 84 days as a zero-filled 7x24 UTC weekday-by-hour grid (Sunday first), each cell carrying volumeUsd, feesUsd, and fills totalled over the window. |
| `builder_orders` | Pro+ | `builder` 0x-hex, `period` default week | `GET /builders/{builder}/orders` | Placement-plane intent: totalIntents, action mix, time-in-force mix, reduceOnlyShare, a stop/TP trigger breakdown, and fillConversion (trigger history begins 2026-03-24). |

---

## 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:

| User intent | First tool to call | Follow-up tools |
|-------------|--------------------|-----------------|
| "Give me a quick read on this wallet" | `pulse_trader_demo` | `pulse_trader_lifecycle_summary`, `pulse_trader_token_stats` |
| "Is this trader actually good?" | `pulse_trader_lifecycle_summary` | `pulse_trader_lifecycles`, `pulse_wallet_drawdown_curve`, `pulse_compare` |
| "Show their positions" | `pulse_trader_lifecycles` | `pulse_lifecycle` for a specific lifecycle ID |
| "How much pain do they tolerate?" | `pulse_wallet_drawdown_curve` | `pulse_max_pain_events` |
| "Do they exit well?" | `pulse_perfect_exits` | `pulse_trader_lifecycles` |
| "Who recovered after getting crushed?" | `pulse_survivors` | `pulse_anti_survivors`, `pulse_persistent_winners` |
| "Who is hot right now?" | `pulse_cohort_recent_lifecycle_stats` | `pulse_cohort_recent_positions`, `pulse_cohort_recent_trades` |
| "Which market creates or destroys alpha?" | `pulse_coin_alpha_map` | `pulse_lethal_coins`, `pulse_style_distribution` |

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):

| Display name | Slug | Legacy slug (still accepted) |
|--------------|------|------------------------------|
| Apex | `apex` | `money_printer` |
| Sharps | `sharps` | `smart_money` |
| Grinders | `grinders` | `grinder` |
| Scrapers | `scrapers` | `humble_earner` |
| The Crowd | `crowd` | `exit_liquidity` |
| Bleeders | `bleeders` | `semi_rekt` |
| Trapped | `trapped` | `full_rekt` |
| Blown Out | `blown_out` | `giga_rekt` |

Size tiers (by volume, largest to smallest):

| Display name | Slug | Legacy slug (still accepted) |
|--------------|------|------------------------------|
| Heavyweights | `heavyweights` | `leviathan` |
| Cruiserweights | `cruiserweights` | `tidal_whale` |
| Middleweights | `middleweights` | `whale` |
| Welterweights | `welterweights` | `small_whale` |
| Lightweights | `lightweights` | `apex_predator` |
| Featherweights | `featherweights` | `dolphin` |
| Flyweights | `flyweights` | `fish` |
| Strawweights | `strawweights` | `shrimp` |

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](https://coinversa.ai)
- MCP setup guide: [docs.coinversa.ai/mcp/setup](https://docs.coinversa.ai/mcp/setup)
- API Docs: [coinversa.ai/developers](https://coinversa.ai/developers)
- Privacy: [coinversa.ai/privacy](https://coinversa.ai/privacy) · Terms: [coinversa.ai/terms](https://coinversa.ai/terms)
- GitHub: [github.com/coinversaa/mcp-server](https://github.com/coinversaa/mcp-server)
- npm: [@coinversaa/mcp-server](https://www.npmjs.com/package/@coinversaa/mcp-server)
- Support: [chat@coinversaa.ai](mailto:chat@coinversaa.ai)

---

Built by [Coinversa](https://coinversa.ai) — crypto intelligence for AI agents.