Skip to main content
The Coinversa MCP server exposes the Pulse tools to AI agents over the Model Context Protocol. You install it once in your client, and the agent gets first-class access to Hyperliquid trader analytics, HIP-4 outcomes, live risk, and the cross-market asset registry. The MCP is the agent interface — a curated set of tools wrapping the REST API. If you need direct programmatic access to the full endpoint surface (including endpoints not yet exposed as tools) or x402 pay-per-call, use the REST API directly. Both use the same API key. Hosted MCP endpoint: https://mcp.coinversa.ai/mcp Source: github.com/Coinversaa/mcp-server The hosted endpoint uses OAuth: paste the URL into your client and it opens a Coinversa authorization page in your browser. Sign in — or create an account right there — and connect a key in one click: existing accounts pick any of their keys from a list (no need to have the value saved), new accounts get a key created automatically. New accounts get 14 days of Pro, no credit card. No headers, no config beyond the URL.
Prefer pasting? The authorization page also accepts a saved cvsa_ key directly. The two paths differ in what the server holds: connecting with a code hands over a single-use, 2-minute reference and the server stores only that reference, never the key, while a pasted cvsa_ key is held by the server for the life of the grant. Keys stay revocable any time from the developer portal — revoking a key instantly disconnects every agent that authorized with it.

Claude.ai (web)

No local install. Coinversa is listed in Claude’s connector directory; adding it by URL as a custom connector works the same way.

From the Claude connector directory

1

Find Coinversa

Search for Coinversa in Claude’s connectors directory and connect it.
2

Authorize

Claude opens the Coinversa authorization page. Sign in and pick a key — or sign up and one is created for you — then click Authorize.

Alternative: custom connector URL

2

Fill in the form

  • Name: Coinversa
  • URL: https://mcp.coinversa.ai/mcp
Leave the auth fields empty — Claude discovers the OAuth flow automatically.
3

Authorize

Claude opens the Coinversa authorization page. Sign in and pick a key — or sign up and one is created for you — then click Authorize.
4

Verify

Open a new chat and ask: “What’s the global trading stats from Coinversa Pulse?” — Claude should call pulse_global_stats.

Claude Desktop

Use the same Coinversa connector you added in Claude (Settings → Connectors); it is available in Claude Desktop and renders interactive views.

Alternative: local config

Claude Desktop can also read MCP servers from a local JSON config. This path runs the tools through mcp-remote and does not render interactive views.
1

Locate your config file

2

Add the Coinversa entry

If the file already has other mcpServers, just add coinversa alongside them — don’t replace the whole block.
3

Restart and authorize

Fully quit (Cmd+Q / right-click → quit), then reopen. On first connection mcp-remote opens the Coinversa authorization page in your browser — sign in and click Authorize. Look for the Coinversa tool icon in the chat input.
Why mcp-remote? Entries in claude_desktop_config.json are launched as local stdio processes; mcp-remote is a small shim that bridges stdio ↔ HTTP and handles the OAuth dance for you.

Cursor

One click: Add Coinversa Pulse to Cursor. Cursor opens with the server filled in; approve it, then sign in with your Coinversa account when Cursor asks. Coinversa Pulse is also listed on cursor.directory. Or by hand: Cursor supports HTTP MCP servers natively. Add to your ~/.cursor/mcp.json:
Restart Cursor, approve the authorization prompt in your browser, and the Coinversa tools appear in the agent’s tool palette.

Perplexity

Use Perplexity’s Custom Connectors.
1

Open connectors

2

Add custom connector

  • URL: https://mcp.coinversa.ai/mcp
No headers needed.
3

Authorize

Perplexity opens the Coinversa authorization page — sign in (or create a free account; every new account gets 14 days of Pro) and click Authorize.
Perplexity shows tool results as text; interactive charts and maps are a Claude feature. Every tool returns the same data, including market_recent_candles candle rows.

Other clients (stdio / npx)

For any stdio-based MCP client, run the published server directly with your API key from the developer portal:
This runs the same tools locally over stdio, authenticated by the env key instead of OAuth. The stdio package returns text only unless you set MCP_APPS_ENABLED=1 and your client supports MCP Apps.

Interactive views (MCP Apps)

In clients that support MCP Apps, four tools can render an interactive view instead of only text: Asking for a chart — “show me the ETH 1h chart with RSI” — makes market_recent_candles render an interactive chart instead of only candle rows. It adds Coinversa layers — entry profile, average entries, liquidation levels, Apex vs Crowd and its hourly history, and opt-in biggest trades — and a Share button that exports the chart or a cohort positioning card as an image. Text-only clients get the same data as text. See the tool catalog. Interactive views render in Claude on web, desktop and mobile (iOS/Android). Claude asks you to allow the view once (choose Always allow to skip future prompts). Add the connector on web or desktop first; it then works on mobile. Claude Desktop caches views, so fully quit and reopen it to pick up updates.

Verify it works

Regardless of client, ask the agent:
What’s the global trading stats from Coinversa Pulse?
You should see the agent call pulse_global_stats and return Pulse’s coverage and trading totals — this check works on every plan, Free included. If it says “no tool available,” the install didn’t take — restart the client.

Troubleshooting

Your authorization expired or the key behind it was revoked. Reconnect the connector (your client will reopen the authorization page). If you revoked the key on purpose, sign in during authorization and pick another key — or create a fresh one right there.
The MCP connection didn’t initialize. For Claude Desktop, check Console.app on macOS for mcp errors. For Cursor, check the MCP panel in settings. Most often: missing -y on the npx command, or a JSON syntax error in the config.
You may have an aggressive prompt or you share a key with a bot. The MCP and direct-API calls share one quota — see authentication. Ask the agent to call pulse_my_plan to see your tier and limits, and bump to Starter or Pro if you genuinely need more.
Clone Coinversaa/mcp-server and run bun run remote. Set COINVERSAA_KEK (openssl rand -base64 32, keep it stable), and COINVERSAA_SERVICE_KEY (or COINVERSAA_ALLOW_NO_SERVICE_KEY=1 for local development; only the paste-a-key path then works). Set COINVERSAA_API_URL if you also host the backend, and MCP_APPS_ENABLED=1 for interactive views. See the README for the full environment table.