SkillAgentSearch skills...

mcp-server

Hyperliquid trading intelligence for AI agents — 106 available MCP tools: builder analytics (revenue, retention, audience overlap, user journey), cohort analytics, position lifecycles, liquidation heatmaps, trader profiling, HIP-4 outcome contracts, and live market data.

Install / Use

claude mcp add Coinversaa -- npx -y github:Coinversaa/mcp-server

If the server publishes to npm under a different name, use that package instead — check the repo README.

About this skill
🔌

MCP Server

Model Context Protocol server

Quality Score

75/100

Supported Platforms

Claude Code
Claude Desktop
Cursor

Tags

Our assessment of mcp-server

mcp-server scores 75/100 on our quality scale, 858th of 978 AI & Machine Learning skills we index.

Its MCP Server is 50 KB long, well organised into 47 sections with 6 code examples: long enough that it reads more like full documentation than a focused instruction file, which agents can find harder to follow.

It has 10 GitHub stars, so there is little community track record yet; judge it on its content.

Substance
21/30
Structure
20/20
Description
15/15
Adoption
4/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 17 days ago, so mcp-server is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 97/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.

Automated pattern scan on 2026-10-12. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

mcp-server compared with similar skills

All 4 of these similar skills score higher than mcp-server; compare them before choosing.

SkillScoreStarsUpdatedFormat
mcp-server (this skill)by Coinversaa751017d agoMCP Server
claude-memby thedotmack10099.7ktodayCLAUDE.md
Agent-Reachby Panniantong10095.9k3d agoCLAUDE.md
Understand-Anythingby Egonex-AI10085.9k1d agoCLAUDE.md
headroomby headroomlabs-ai10075.1ktodayCLAUDE.md

Frequently asked questions

How do I install mcp-server?
Run claude mcp add Coinversaa -- npx -y github:Coinversaa/mcp-server. The install tabs above show the steps for each supported agent.
Which AI agents does mcp-server work with?
It is written for Claude Code, Claude Desktop and Cursor, as a MCP Server file. Other agents that read the same format can often use it too.
Is mcp-server safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is MIT-licensed and scores 97/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is mcp-server still maintained?
The repository was last updated 17 days ago, so mcp-server is actively maintained.

Coinversa Pulse — MCP Server

<a href="https://glama.ai/mcp/servers/Coinversaa/mcp-server"><img src="https://glama.ai/mcp/servers/Coinversaa/mcp-server/badge" alt="MCP Server" /></a>

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_heatmap is 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: set COINVERSAA_HIDDEN_TOOLS= (explicitly empty) to advertise everything, or name a different comma-separated list to withhold other tools. Leaving the variable unset withholds builder_heatmap.
  • pulse_market_overview removed. It was a deprecated alias for list_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_outcomes and pulse_lifecycle gained the paging and filter parameters the hosted connector already had, and live_coin_risk_history gained include.

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 title and 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

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars10
CategoryAI
Updated17d ago
Forks1

Languages

JavaScript

Trust signals

97/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 info