Provides crypto intelligence for AI agents, including Hyperliquid wallet analytics, trade history, behavioral cohorts, and live market data.
Also known as coinversaa/mcp-server, @coinversaa/mcp-server
- Stars
- 10
- Tools
- —
- Downloads, 30 days
- 312
- Latest version
- 0.2.1
- Last commit
- Sep 24, 2026
- License
- MIT
What is Coinversa Pulse MCP?
Coinversa Pulse provides crypto intelligence for AI agents, including Hyperliquid wallet analytics, trade history, behavioral cohorts, and live market data.
Summary generated from the project's README
About Coinversa Pulse MCP server
Coinversa Pulse provides deep crypto intelligence specifically designed for AI agents interacting with the Hyperliquid ecosystem. It allows users to query the entire wallet universe, access indexed trade history with PnL attribution, and analyze behavioral cohorts. The server supports a wide range of data including live market data, L4 order book details, and HIP-4 outcome contracts for prediction markets.
Developers connect to the server using an API key obtained from the Coinversa developer portal. Access to specific tools and rate limits is determined by the user's backend tier, such as Starter or Pro. The server can be used via a hosted connector or local setup. It offers specialized analytics for builder-fee economies, allowing agents to track how different frontends and apps monetize user flow and retain traders across various markets including perps, commodities, and stocks.
What you can do with it
- 1Analyze order book depthAn agent can inspect the current resting size, spread, and imbalance for a specific coin.
- 2Track builder revenue and performanceA developer can request rankings of builders based on their exact on-chain ledger revenue.
- 3Evaluate trader execution qualityAn AI can reconstruct position lifecycles to see the best and worst prices a trader experienced.
- 4Monitor prediction market activityUsers can discover active outcome contracts and inspect their recent settlements.
- 5Identify large resting ordersAn agent can find which specific wallets are holding the largest orders on a particular side of the book.
Written from the project's README. Every use case is checked against a quote from it.
How to install Coinversa Pulse MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Coinversa Pulse MCP in Claude Code
$ claude mcp add --env 'COINVERSAA_API_KEY=<YOUR_COINVERSAA_API_KEY>' mcp-server -- npx -y @coinversaa/mcp-serverInstall Coinversa Pulse MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@coinversaa/mcp-server"
],
"env": {
"COINVERSAA_API_KEY": "<YOUR_COINVERSAA_API_KEY>"
}
}
}
}Install Coinversa Pulse MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@coinversaa/mcp-server"
],
"env": {
"COINVERSAA_API_KEY": "<YOUR_COINVERSAA_API_KEY>"
}
}
}
}Install Coinversa Pulse MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp-server","type":"stdio","command":"npx","args":["-y","@coinversaa/mcp-server"],"env":{"COINVERSAA_API_KEY":"<YOUR_COINVERSAA_API_KEY>"}}'Install Coinversa Pulse MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@coinversaa/mcp-server"
],
"env": {
"COINVERSAA_API_KEY": "<YOUR_COINVERSAA_API_KEY>"
}
}
}
}Install Coinversa Pulse MCP in Codex
$ codex mcp add mcp-server --env 'COINVERSAA_API_KEY=<YOUR_COINVERSAA_API_KEY>' -- npx -y @coinversaa/mcp-serverInstall Coinversa Pulse MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp-server] command = "npx" args = ["-y", "@coinversaa/mcp-server"] [mcp_servers.mcp-server.env] COINVERSAA_API_KEY = "<YOUR_COINVERSAA_API_KEY>"
Install Coinversa Pulse MCP in Gemini CLI
$ gemini mcp add -s user -e 'COINVERSAA_API_KEY=<YOUR_COINVERSAA_API_KEY>' mcp-server npx -- -y @coinversaa/mcp-serverInstall Coinversa Pulse MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@coinversaa/mcp-server"
],
"env": {
"COINVERSAA_API_KEY": "<YOUR_COINVERSAA_API_KEY>"
}
}
}
}Configuration
COINVERSAA_API_KEYRequiredSecretCoinversaa API key (starts with cvsa_). Get one at https://coinversaa.ai/developers
| Name | Description | |
|---|---|---|
| COINVERSAA_API_KEY | Coinversaa API key (starts with cvsa_). Get one at https://coinversaa.ai/developers | RequiredSecret |
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablecoinversaa/mcp-server is public and reachablegithub.com/coinversaa/mcp-server ↗Pass
- Package names this repository as its source@coinversaa/mcp-server names coinversaa/mcp-server as sourcenpmjs.com/package/@coinversaa/mcp-server ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-09-24github.com/coinversaa/mcp-server ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @coinversaa/mcp-serverPass
- No critical advisory in the package or its dependencies99 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubCoinversa Pulse — MCP Server
Crypto intelligence for AI agents. Query the full Hyperliquid wallet universe, indexed trade history with PnL attribution, behavioral cohorts, and live market data through any MCP-compatible client. Call pulse_global_stats to see exact current coverage (tracked wallets, indexed trades, volume, PnL, data window).
Now with HIP-4 outcome contracts and builder dex support — inspect prediction-market style outcome contracts, settlements, commodities (gold, silver, oil), stocks (TSLA, AAPL), and perps across 8 dexes and 369+ markets.
What's new in 0.12.0
L4 order book tools and dataset coverage. Five more tools, and full parity with the hosted connector at https://mcp.coinversa.ai/mcp.
| New tool | What it answers |
|---|---|
book_summary [Pro] |
"What does the resting book for coin X look like right now — depth, spread, imbalance?" |
book_levels [Pro] |
"Where is the resting size stacked, level by level?" |
book_whales [Pro] |
"Which wallets are holding the largest resting orders, and on which side?" |
book_stop_map [Pro] |
"Where are the trigger orders clustered that a move would sweep?" |
data_coverage |
"What window does each dataset cover, and how fresh is it?" |
Tool count: 103 → 107 registered, 106 advertised (see below).
Also in 0.12.0:
builder_heatmapis withheld by default. Its upstream cannot answer inside the client timeout until the hourly rollup is backfilled, so advertising it only produced timeouts. It is still built in: setCOINVERSAA_HIDDEN_TOOLS=(explicitly empty) to advertise everything, or name a different comma-separated list to withhold other tools. Leaving the variable unset withholdsbuilder_heatmap.pulse_market_overviewremoved. It was a deprecated alias forlist_markets, which is the canonical market-discovery tool.- Descriptions and parameters resynced with the hosted connector. Twenty tool descriptions and seven input schemas had drifted;
live_mark_dislocations,pulse_cohort_bias_history,pulse_cohort_performance_daily,hip4_outcomes,hip4_trader_outcomesandpulse_lifecyclegained the paging and filter parameters the hosted connector already had, andlive_coin_risk_historygainedinclude.
What's new in 0.11.1
Builder user-lifecycle, journey, heatmap, and order-intent analytics. 4 more tools over the same builder-fee data, covering where a builder's users stand today, how fast it monetizes a new wallet, when its flow actually trades, and what its users intend at order placement.
| New tool | What it answers |
|---|---|
builder_journey [Pro] |
"How fast and how unevenly does builder X monetize a new user?" |
builder_lifecycle [Pro] |
"How many of builder X's users are still active, and how many did a rival take?" |
builder_heatmap [Pro] |
"What hours does builder X's volume peak, and when is it safe to ship?" |
builder_orders [Pro] |
"Do builder X's users place stops and take-profits, and how much of their order flow actually fills?" |
Tool count: 99 → 103.
Also in 0.11.1:
- Tool titles and annotations — every tool now carries a human-readable
titleand MCP annotations (readOnlyHint: true,destructiveHint: false,idempotentHint: true,openWorldHint: true), so clients can label the tools and treat them as read-only without prompting. - Hosted connector parity — this package now ships exactly the tool set served by the hosted OAuth endpoint at
https://mcp.coinversa.ai/mcp. The obsolete header-authenticated HTTP entrypoint that used to live in this repo has been removed; see Quick Start for the two supported ways to connect.
What's new in 0.11.0
Builder analytics — 8 new tools (91 → 99). The Hyperliquid builder-code economy (the fees frontends, wallet apps, bots, and builder dexes earn on routed order flow) is now a first-class tool family:
builder_leaderboard— builders ranked by exact on-chain ledger revenue, with attributed volume/users and prev-window deltas (Starter)builder_profile— one builder: revenue, daily series, top coins, profitable-user share (Starter)builder_traders— wallets trading via a builder, with exchange-wide cohort tiers (Pro)builder_fills— individual attributed fills through a builder, perp/spot/HIP-4 (Pro)builder_cohorts— a builder's user base split by behavioral tier (Pro)builder_retention— monthly new-user retention triangle (Pro)builder_overlap— which other builders share this one's users (Pro)trader_builders— every builder one wallet trades through, by fees paid (Starter)
Revenue is computed from Hyperliquid's own cumulative builder-fee ledger
(reconciled on-chain); fill-level detail comes from order→fill attribution
with honest coverage caveats in every response (dataNotes). Ask your agent
"which frontends do MetaMask's traders also use?" — no other data source
can answer that.
What's new in 0.10.0
Dual-vocabulary cohort tiers. New canonical tier slugs accepted everywhere
a tier is an input — PnL tiers (apex, sharps, grinders, scrapers,
crowd, bleeders, trapped, blown_out) and weight-class size tiers
(heavyweights … strawweights). Legacy slugs (money_printer,
smart_money, …) remain valid indefinitely; responses are unchanged. No
breaking changes.
What's new in 0.9.0
Entity resolution, tier-aware sessions, and chain-verified answers.
| New tool | What it answers |
|---|---|
pulse_entity_profile [Pro] |
"Who owns this wallet — and what is their REAL combined book across every sub-account?" |
pulse_entity_leaderboard [Pro] |
"Top traders deduped by OWNER, not wallet — a fund running 35 sub-accounts shows as one entity." |
pulse_my_plan |
"What plan is this API key on, what are the limits, and what does upgrading unlock?" |
pulse_exchange_volume |
"24h volume — total and per dex (builder dexes are ~43% and most trackers miss them)." |
pulse_exchange_oi |
"Open interest by dex with long/short split." |
pulse_active_traders |
"How many wallets traded in the last 24h?" |
pulse_exchange_positions |
"How many positions are open right now, per dex?" |
pulse_pnl_leaders |
"Who made and lost the most in the last 24h, exchange-wide?" |
Also in 0.9.0:
- Tier-aware errors — a tier-gated or rate-limited request now explains the caller's tier, the required tier, and carries a direct upgrade link. (Fixes valid free-tier keys being told their key was "rejected" on Pro endpoints.)
- Verified-vs-chain stamps — entity responses carry the chain-state block they were last reconciled against.
Tool count: 83 → 91.
What's new in 0.8.0
Position lifecycles, execution quality, and trader archetypes. v0.8.0 adds 28 tools built on a fully re-derived position-lifecycle dataset — every open→close cycle reconstructed from on-chain fills, now carrying MAE/MFE (the worst adverse and best favorable price each position ever saw). This unlocks execution-quality analysis, not just PnL.
| New tool | What it answers |
|---|---|
pulse_trader_lifecycles |
"Show me every open→close position for this wallet, with entry/exit and hold time." |
pulse_trader_lifecycle_summary |
"What are this wallet's position-level stats — win rate, avg hold, biggest win/loss?" |
pulse_lifecycle |
"Break down lifecycle 12345 into every fill that built and unwound it." |
pulse_trader_demo |
"Give me a quick wallet brief before a deeper dive." |
pulse_wallet_drawdown_curve |
"How far underwater did each of this wallet's positions go before working?" |
pulse_max_pain_events |
"Which winners survived the deepest drawdowns before recovering?" |
pulse_perfect_exits |
"Which exits captured most of the maximum favorable move?" |
pulse_backstop_events |
"What were the most catastrophic individual liquidations?" |
pulse_survivors / pulse_anti_survivors |
"Who blew up and recovered — and who never did?" |
pulse_persistent_winners |
"Who is profitable across multiple distinct months, not just lucky once?" |
pulse_capital_titans |
"Who extracts the most PnL per dollar of fees paid?" |
pulse_one_month_wonders |
"Who had one huge month then gave it back?" |
pulse_newcomer_whales |
"Who just showed up and is already trading big notional?" |
pulse_coin_kings |
"Who is the top earner of each coin?" |
pulse_top_liquidators |
"Who profits most by liquidating others?" |
pulse_lethal_coins |
"Which coins blow people up most often?" |
pulse_coin_alpha_map |
"Per coin, how big are the winner vs loser profit pools?" |
pulse_hour_profitability |
"What UTC hour of close is most profitable?" |
pulse_market_concentration |
"How concentrated is alpha — do the top 1% take everything?" |
pulse_style_distribution |
"Do scalpers or swing traders make more money?" |
pulse_compare |
"Head-to-head: who is the better trader, A or B?" |
pulse_cohort_recent_* |
"What are wallets that are printing RIGHT NOW (last-30-day tier) doing — positions, trades, top lifecycles, concentration?" |
pulse_lifecycles_recent |
"What just closed exchange-wide right now?" (global feed; successor to pulse_recent_closed_positions) |
The legacy closed-position tools (pulse_trader_closed_positions, pulse_trader_closed_position_stats, pulse_recent_closed_positions) are kept for backward compatibility but superseded by the lifecycle tools, which read the corrected position_lifecycles_full table (more history, MAE/MFE, spot).
Tool count: 55 → 83. An API key is required for every tool; backend tiering determines which tools and limits are available.
What's new in 0.7.0
HIP-4 outcome contract intelligence. v0.7.0 adds 12 tools for discovering active outcomes, reading question metadata, inspecting settlements and recent fills, tracking daily volume, ranking outcome traders, measuring outcome/perp overlap, and joining outcome holders to their currently open perp positions on the same underlying asset.
| New tool | What it answers |
|---|---|
hip4_outcomes |
"What outcome contracts are active right now?" |
hip4_outcome |
"What is outcome 123 and what side tokens does it use?" |
hip4_outcome_summary |
"How much volume/PnL has this outcome done across both sides?" |
hip4_outcome_recent_trades |
"Show me recent fills for this prediction market." |
hip4_questions |
"What HIP-4 questions and named outcomes exist?" |
hip4_recent_settlements |
"Which outcomes settled recently and which side won?" |
hip4_daily_volume |
"Is HIP-4 outcome volume growing day by day?" |
hip4_most_active |
"Which outcome contracts are most active?" |
hip4_top_traders |
"Who are the top outcome traders?" |
hip4_trader_outcomes |
"What outcomes did this wallet trade?" |
hip4_cross_product_overlap |
"How much overlap is there between outcome traders and perp traders?" |
hip4_perp_position_context |
"Do outcome 25 traders currently have open BTC perp exposure, and is it aligned or hedged?" |
Tool count: 43 → 55. An API key is required for every tool; backend tiering determines which tools and limits are available. Get a key from coinversa.ai/developers.
What's new in 0.6.0
Canonical cross-market asset taxonomy. The same underlying asset can appear under different tickers on different venues (e.g. GOLD on xyz, PAXG on native Hyperliquid — both track gold). v0.6.0 added 3 tools that resolve synonyms server-side and aggregate across venues, plus a ground-truth OI tool:
| New tool | What it answers |
|---|---|
list_assets |
"What assets are available? Which are listed on 2+ venues?" |
list_asset |
"Where does GOLD trade? Is PAXG the same as GOLD?" |
pulse_cross_market_asset |
"Is gold more crowded on xyz or hyna? Do dexes disagree on BTC direction?" |
live_official_oi |
"What does Hyperliquid itself report for BTC OI — do our numbers match?" |
Synonyms baked in: PAXG → GOLD, XAUT → GOLD, XAGT → SILVER. Prefix grouping (BTC ≡ flx:BTC ≡ hyna:BTC) works automatically.
Other 0.6.0 housekeeping: default API URL points at production; removed stale hard-coded "710K+ wallets / 1.8B+ trades" marketing figures (call pulse_global_stats for current coverage); pulse_market_overview kept as a deprecated alias for the canonical list_markets.
Quick Start
There are two ways to connect. Both expose the same 106 read-only tools available by default and both require a Coinversa API key (cvsa_...) — there is no keyless tier.
| Method | Where | Auth | Best for |
|---|---|---|---|
| Hosted Remote MCP (recommended) | https://mcp.coinversa.ai/mcp |
OAuth 2.1 in the browser — no key handling in the client | Claude.ai, Claude Desktop, Claude Code, Cursor, ChatGPT, Perplexity, any Streamable HTTP client |
| Local stdio MCP (this package) | npx -y @coinversaa/mcp-server@0.12.0 |
COINVERSAA_API_KEY env var |
Codex and other stdio-only clients, air-gapped setups, development |
The canonical, always-current client guide lives at docs.coinversa.ai/mcp/setup. The snippets below mirror it.
Hosted Remote MCP (OAuth)
Paste the URL into your client and leave every auth/header field empty. The client discovers the OAuth flow automatically and opens a Coinversa authorization page in your browser. There you either:
- click Sign in / Sign up & get a key — the developer portal opens in a popup, you pick (or auto-create) a key, and a one-time connect code is handed back to the authorization page; the raw key never reaches the MCP server in this path — or
- paste an existing
cvsa_key directly.
Click Authorize and you are connected. New accounts get 14 days of Pro, no credit card. Revoking a key in the developer portal instantly disconnects every agent that authorized with it.
Claude.ai (web)
- Open claude.ai/customize/connectors?modal=add-custom-connector.
- Name:
Coinversa— URL:https://mcp.coinversa.ai/mcp. Leave the auth fields empty. - Click Add, then Connect; sign in on the Coinversa page and click Authorize.
- In a new chat ask: "What are the global trading stats from Coinversa Pulse?" — Claude should call
pulse_global_stats.
Claude Desktop
Claude Desktop speaks stdio only, so use the mcp-remote shim, which bridges stdio ↔ HTTP and handles the OAuth dance. Edit your config file:
| OS | Path |
|---|---|
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows | %APPDATA%\Claude\claude_desktop_config.json |
| Linux | ~/.config/Claude/claude_desktop_config.json |
{
"mcpServers": {
"coinversa": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.coinversa.ai/mcp"]
}
}
}
Fully quit and reopen Claude Desktop. On first connection mcp-remote opens the Coinversa authorization page in your browser — sign in and click Authorize.
Cursor
Cursor supports HTTP MCP servers natively. Add to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):
{
"mcpServers": {
"coinversa": {
"url": "https://mcp.coinversa.ai/mcp"
}
}
}
Restart Cursor and approve the authorization prompt in your browser. The one-click Install in Cursor deeplink at developers.coinversa.ai/connect works too.
Claude Code
claude mcp add --transport http coinversa https://mcp.coinversa.ai/mcp
Then run /mcp inside Claude Code and choose Authenticate for coinversa; the browser flow is the same as above.
ChatGPT, Perplexity, and other remote clients
Add a custom connector / remote MCP server with URL https://mcp.coinversa.ai/mcp and no headers. The client will open the Coinversa authorization page on first use.
Local stdio MCP (npx + API key)
For stdio-only clients (for example Codex) or when you would rather hold the key yourself, run this npm package locally. Get a key from the developer portal.
{
"mcpServers": {
"coinversa": {
"command": "npx",
"args": ["-y", "@coinversaa/mcp-server@0.12.0"],
"env": {
"COINVERSAA_API_KEY": "cvsa_your_key_here"
}
}
}
}
Or from a shell:
COINVERSAA_API_KEY=cvsa_... npx -y @coinversaa/mcp-server@0.12.0
This runs the same tools locally over stdio, authenticated by the env key instead of OAuth. The stdio server exits at startup if COINVERSAA_API_KEY is missing. No cloning, no building — npx handles everything.
Verify it works
Ask the agent: "Use Coinversa Pulse to show me the top 5 traders on Hyperliquid by total PnL this week." You should see a pulse_leaderboard call with ranked addresses. pulse_my_plan shows which plan the connected key is on and what each tier unlocks. If the agent reports a 401, the authorization expired or the key was revoked — reconnect the connector and it will reopen the authorization page.
Hosted Remote MCP
Endpoint: https://mcp.coinversa.ai/mcp — Streamable HTTP, stateless. Each POST /mcp carries one JSON-RPC request (or batch) and gets its response on that connection; there are no server-side sessions to resume, so GET /mcp and DELETE /mcp return 405 Method Not Allowed. There is no SSE endpoint.
| Endpoint | Method | Purpose |
|---|---|---|
/mcp |
POST |
MCP Streamable HTTP endpoint (requires a valid OAuth access token) |
/health |
GET |
Health check — returns { ok, name, version } |
/.well-known/oauth-authorization-server |
GET |
OAuth 2.1 authorization-server metadata (RFC 8414) |
/.well-known/oauth-protected-resource/mcp |
GET |
Protected-resource metadata (RFC 9728) — this is what clients follow from the 401 on /mcp |
/authorize |
GET |
Authorization endpoint; renders the consent page |
/token |
POST |
Token endpoint (authorization_code + PKCE, refresh_token) |
/register |
POST |
Dynamic client registration (RFC 7591) |
/revoke |
POST |
Token revocation (RFC 7009) |
The hosted server is operated by Coinversa and calls the first-party Coinversa API at https://api.coinversa.ai on your behalf, with the key you authorized. It is not a third-party proxy. It serves the same tool definitions as this package (same names, descriptions, input schemas, titles, and annotations — enforced by tests/toolParity.test.ts); this repository is the source of the npm stdio package, not of the hosted OAuth server itself.
Authentication
The hosted endpoint supports exactly one authentication method: OAuth 2.1 with PKCE (S256) and dynamic client registration. Every conformant client (Claude.ai, Claude Desktop via mcp-remote, Claude Code, Cursor, ChatGPT, Perplexity) handles this automatically from the URL alone.
How it works:
- The client
POSTs to/mcpwithout a token, gets401with aWWW-Authenticateheader pointing at the protected-resource metadata, and discovers the authorization server from there. - The client registers itself via
/register(DCR), then opens/authorizein the browser with a PKCE code challenge. - You see the Coinversa consent page. You either paste a
cvsa_key or click Sign in / Sign up & get a key, which opens the developer portal in a popup and returns a short-lived, single-use connect code to the consent page. In the portal path the raw key never reaches the MCP server — it stores only a key reference that the backend resolves. - The client exchanges the authorization code (plus PKCE verifier) at
/tokenfor tokens.
Token details:
| Token | Format | Lifetime |
|---|---|---|
| Access token | opaque, random | 1 hour |
| Refresh token | opaque, random, rotated on every refresh | 90 days, sliding |
Tokens are stored hashed (SHA-256) on the server. Revoking the underlying API key in the developer portal invalidates every session authorized with it.
There is no header-based API-key authentication on the hosted endpoint. Requests that skip OAuth and put a raw cvsa_ key in an Authorization or custom header are rejected with 401. If you want to authenticate with a key you hold, run the local stdio server instead (see above), which reads COINVERSAA_API_KEY from its environment and sends it to the Coinversa API itself.
Privacy & data handling
The hosted server is a thin, stateless bridge between your MCP client and the Coinversa API.
What it stores (a SQLite database on Coinversa infrastructure):
- OAuth client registrations created through dynamic client registration (client id, redirect URIs, client metadata).
- Access and refresh tokens, stored as SHA-256 hashes — the plaintext token exists only in your client.
- The API-key grant behind each token: either a key id (a reference the backend resolves; the key itself is never stored) when you connected through the developer portal, or the pasted key encrypted at rest with AES-256-GCM under a key-encryption key that lives outside the database.
What it never stores:
- Conversation content. The server only ever sees the tool call in flight, not your chat.
- Tool arguments or results beyond the lifetime of the request being served. Nothing is written to a database, and parameters are not logged.
- Wallet private keys, seed phrases, signatures, exchange credentials, or any custody material — no tool asks for them and none exist.
The local stdio server stores nothing at all: it holds COINVERSAA_API_KEY in memory for the life of the process and forwards each tool call to the Coinversa API.
What tool calls send to the Coinversa API: the parameters you can see in each tool's schema — market symbols, public wallet addresses, cohort names, HIP-4 outcome ids, builder addresses, time windows — plus your API key for authorization and metering. Usage is counted against the key's plan; see Rate Limits.
Scope: every tool is read-only and is annotated as such (readOnlyHint: true, destructiveHint: false). The server cannot place orders, sign transactions, move funds, approve agents, or change any account setting on Hyperliquid or Coinversa.
Revocation: revoke the API key in the developer portal to disconnect every agent that authorized with it, or remove the connector in your client; clients may also call /revoke.
Policies: coinversa.ai/privacy · coinversa.ai/terms. Questions or data requests: chat@coinversaa.ai.
Coinversa Pulse MCP questions
How do I add Coinversa Pulse MCP to Claude Code?
Run claude mcp add --env 'COINVERSAA_API_KEY=<YOUR_COINVERSAA_API_KEY>' mcp-server -- npx -y @coinversaa/mcp-server in your terminal. Add --scope user to make it available in every project.
How do I add Coinversa Pulse MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What kind of market data does it provide?
It provides live market data, L4 order book tools, and coverage for prediction-market style outcome contracts, commodities, and stocks across multiple DEXs.
How can I see the current data coverage?
You can call the pulse_global_stats tool to view exact current coverage, including tracked wallets, indexed trades, volume, PnL, and the data window.
Is an API key required to use the tools?
Yes, an API key is required for every tool, and your backend tier determines which tools and limits are available to you.