Prototipo · Versión preliminar: todos los servidores del registro oficial, sincronizados cada 30 minutos. Las reseñas y las cuentas llegarán en una etapa posterior.
PopNx MCPServidores MCP para quienes usan IA · explicados con palabras sencillas
Modo principiante Activado
ColoresSistemaClaroOscuro
IdiomaไทยEnglish中文日本語한국어EspañolDeutsch
☰ MenúAjustes
Modo principiante Activado
ColoresSistemaClaroOscuro
IdiomaไทยEnglish中文日本語한국어EspañolDeutsch

Coinversaa MCP

de coinversaaversión 0.2.1i★ –iSe ejecuta en tu computadora
Nombre en el registroio.github.Coinversaa/mcp-server

Instalar

Resumen

Descripción del creador (original en inglés)

Crypto intelligence for AI agents. Hyperliquid trader analytics, cohorts, and live market data.

Los tres pilares de PopNx MCP

Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

  • Conexión: Se ejecuta en tu computadora
  • Transporte: stdio
  • Categoría: Marketing y redes sociales
  • Debes completar: COINVERSAA_API_KEY

Instalación

Elige la app de IA que usas y copia la configuración.

Antes de instalar

Los valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.

Necesitas

  • npmNode.js instalado (para el comando npx)

¿Qué app usas?

Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.

Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json

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

Ejecuta esto en tu terminal

claude mcp add coinversaa --env COINVERSAA_API_KEY=your-value -- npx -y @coinversaa/mcp-server

Completa los valores vacíos antes de ejecutarlo.

Abrir en Cursor

O copia la configuración tú

Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json

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

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Abrir en VS Code

O copia la configuración tú

Pégalo en .vscode/mcp.json de tu proyecto

{
  "servers": {
    "coinversaa": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@coinversaa/mcp-server"
      ],
      "env": {
        "COINVERSAA_API_KEY": "your-value"
      }
    }
  }
}

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Valores que debes completar

  • COINVERSAA_API_KEY secreto obligatorio env
    Coinversaa API key (starts with cvsa_). Get one at https://coinversaa.ai/developers

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026

  • ✓ Superada

    El creador coincide con el repo

    El nombre en el registro se verificó con la cuenta de GitHub coinversaa, dueña del repo

  • … Aún sin revisar

    Sigue en mantenimiento

    Todavía no hemos leído este repo en GitHub

  • … Aún sin revisar

    Tiene licencia

    Todavía no hemos leído este repo en GitHub

  • – No aplica

    El endpoint responde

    Este se ejecuta en tu computadora; no hay endpoint en internet

  • – No aplica

    Inicio de sesión con OAuth

    Se ejecuta en tu computadora y usa ajustes locales en su lugar

  • … Aún sin revisar

    Sin instrucciones ocultas en las descripciones de herramientas

    Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet

Comparado con otros en Marketing y redes socialesi

  • Más estrellas que el 0% de los otros 2959 servidores de esta categoría
  • Publicado en el registro más recientemente que el 2% de los otros 2959 servidores de esta categoría
  • Revisiones básicas iguales o mejores que el 100% de los otros 2959 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Preguntas frecuentes

¿Es seguro Coinversaa MCP?

Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.

¿Qué claves o códigos necesita?

Debes completar: COINVERSAA_API_KEY

¿Se ejecuta en mi computadora o en la nube?

Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).

¿Sigue en mantenimiento?

El repo de GitHub cambió por última vez –, y la última versión (0.2.1) llegó al registro hace 8 meses.

¿Qué apps pueden usarlo?

Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.

¿Qué puedo usar en su lugar?

En la misma categoría: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

An MCP server retrieving transcripts of YouTube videos

Se ejecuta en tu computadora★ 495MITActualizado hace 9 días
Instalar

GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.

Se ejecuta en tu computadora★ 244MITActualizado hace 9 días
Instalar

AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.

Se ejecuta en la nube★ 137MITActualizado hace 9 días
Instalar

README del creador

Abrir el README

Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.

Coinversa 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 toolWhat 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 toolWhat 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 toolWhat 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 toolWhat 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 toolWhat 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 toolWhat it answers

| list_assets | "What assets

Solo se muestra el principio; lee el resto en el repo

Pregunta a PopNx