프로토타입 · 미리 보기: 공식 레지스트리의 모든 서버를 담고 있으며 30분마다 동기화해요. 리뷰와 계정 기능은 다음 단계에서 열려요.
PopNx MCPAI를 쓰는 사람을 위한 MCP 서버 · 쉬운 말로 설명해요
초보자 모드 켜기
색상시스템 설정라이트다크
언어ไทยEnglish中文日本語한국어EspañolDeutsch
☰ 메뉴설정
초보자 모드 켜기
색상시스템 설정라이트다크
언어ไทยEnglish中文日本語한국어EspañolDeutsch

Coinversaa MCP

제작자: coinversaa버전 0.2.1i★ –i내 컴퓨터에서 실행
레지스트리 이름io.github.Coinversaa/mcp-server

설치

개요

제작자가 쓴 설명(영어 원문)

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

PopNx MCP의 세 기둥

이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

  • 연결 방식: 내 컴퓨터에서 실행
  • 전송 방식: stdio
  • 카테고리: 마케팅 및 소셜 미디어
  • 입력해야 할 값: COINVERSAA_API_KEY

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

설치하기 전에

  • 기본 점검: 1개 중 1개 통과
  • 내 컴퓨터에서 내 사용자 계정의 권한(파일, 네트워크, 앱)으로 실행돼요.
  • 직접 입력할 값: COINVERSAA_API_KEY

비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.

필요한 것

  • npmNode.js 설치(npx 명령어용)

어떤 앱을 쓰세요?

위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.

Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요

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

터미널에서 이 명령어를 실행하세요

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

실행하기 전에 빈 값을 채워 주세요.

Cursor에서 열기

또는 설정을 직접 복사하기

프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요

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

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

VS Code에서 열기

또는 설정을 직접 복사하기

프로젝트의 .vscode/mcp.json에 붙여 넣으세요

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

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

직접 입력할 값

  • COINVERSAA_API_KEY 비밀 필수 env
    Coinversaa API key (starts with cvsa_). Get one at https://coinversaa.ai/developers

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검

  • ✓ 통과

    제작자와 저장소 일치

    레지스트리 이름이 GitHub 계정 coinversaa 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요

  • … 아직 점검 안 함

    계속 관리되고 있음

    아직 GitHub에서 이 저장소를 읽어 오지 않았어요

  • … 아직 점검 안 함

    라이선스 있음

    아직 GitHub에서 이 저장소를 읽어 오지 않았어요

  • – 해당 없음

    엔드포인트 응답

    내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요

  • – 해당 없음

    OAuth로 로그인

    내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요

  • … 아직 점검 안 함

    도구 설명에 숨겨진 지시 없음

    내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요

마케팅 및 소셜 미디어 카테고리의 다른 서버와 비교i

  • 이 카테고리의 다른 서버 2959개 중 0%보다 스타가 많아요
  • 이 카테고리의 다른 서버 2959개 중 2%보다 최근에 레지스트리에 공개됐어요
  • 기본 점검 결과가 이 카테고리의 다른 서버 2959개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

자주 묻는 질문

Coinversaa MCP, 안전한가요?

해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.

어떤 키나 코드가 필요한가요?

입력해야 할 값: COINVERSAA_API_KEY

내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?

내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).

아직 관리되고 있나요?

GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.2.1)은 8개월 전 레지스트리에 올라왔어요.

어떤 앱에서 쓸 수 있나요?

Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Node.js도 있어야 해요.

대신 쓸 수 있는 건 뭐가 있나요?

같은 카테고리에는: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

MCP YouTube Transcript

제작자: jkawamoto

An MCP server retrieving transcripts of YouTube videos

내 컴퓨터에서 실행★ 495MIT9일 전 업데이트
설치

Google Analytics MCP

제작자: surendranb

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

내 컴퓨터에서 실행★ 244MIT9일 전 업데이트
설치

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

클라우드에서 실행★ 137MIT9일 전 업데이트
설치

제작자의 README

README 열기

제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.

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

앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요

PopNx에게 묻기