Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
제작자가 쓴 설명(영어 원문)
Read-only Hyperliquid, funding-rate and cross-exchange perpetual spread tools.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
MDL_POSITION_INDEX_URL, MDL_POSITION_INDEX_PATH필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요
{
"mcpServers": {
"market-depth-lab": {
"command": "npx",
"args": [
"-y",
"market-depth-lab-mcp-server"
],
"env": {
"MDL_POSITION_INDEX_URL": "your-value",
"MDL_POSITION_INDEX_PATH": "your-value"
}
}
}
}터미널에서 이 명령어를 실행하세요
claude mcp add market-depth-lab --env MDL_POSITION_INDEX_URL=your-value --env MDL_POSITION_INDEX_PATH=your-value -- npx -y market-depth-lab-mcp-server실행하기 전에 빈 값을 채워 주세요.
프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"market-depth-lab": {
"command": "npx",
"args": [
"-y",
"market-depth-lab-mcp-server"
],
"env": {
"MDL_POSITION_INDEX_URL": "your-value",
"MDL_POSITION_INDEX_PATH": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"market-depth-lab": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"market-depth-lab-mcp-server"
],
"env": {
"MDL_POSITION_INDEX_URL": "your-value",
"MDL_POSITION_INDEX_PATH": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
MDL_POSITION_INDEX_URL envMDL_POSITION_INDEX_PATH env이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검
레지스트리 이름이 GitHub 계정 derkcc 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.2.2)은 3개월 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Node.js도 있어야 해요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, Starreel
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Turn a script into a finished, downloadable short-drama episode — via MCP or REST.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
Read-only Hyperliquid and cross-exchange market research for AI agents.
🌐 Project website and live dashboards: [marketdepthlab.com](https://marketdepthlab.com)
Every MCP result points back to [Market Depth Lab](https://marketdepthlab.com), where the public dashboards, methodology and related research live.
Market Depth Lab MCP gives Claude, Codex, Cursor and other MCP clients nine structured tools for public Hyperliquid and cross-exchange market data. It does not request a private key, wallet signature, exchange login or permission to trade.
Independent open-source software. Not affiliated with or endorsed by
Hyperliquid. Research information only; not financial advice.
structuredContent.| Tool | What it answers |
|---|---|
list_active_hyperliquid_twaps | Which public TWAP schedules are active, and what is their estimated current notional? |
analyze_hyperliquid_wallet | What positions, balances, orders, leverage and PnL are visible for this public address? |
calculate_hyperliquid_fees | What would the estimated fee be for this notional, role and fee tier? |
get_hype_market_snapshot | What is HYPE worth now, and how do spot and perps compare? |
hyperliquid_summarize_large_trader_positions | How is the monitored large-trader cohort positioned by market? |
hyperliquid_list_top_position_holders | Which monitored addresses have the largest positions in one market? |
hyperliquid_list_funding_rates | Who pays funding now, and what is the exact trailing-24h sum for the returned markets? |
scan_cross_exchange_funding_spreads | Where is the largest normalized funding difference across Binance USD-M, OKX and Hyperliquid, after a user-supplied cost estimate? |
scan_cross_exchange_perp_price_spreads | Where do current perpetual best bids and asks diverge across venues, after fee estimates and a visible top-of-book capacity check? |
The three concepts are deliberately separate:
hyperliquid_list_funding_rates describes the current Hyperliquid main and HIP-3 funding universe, including exact trailing-24h sums for the returned page.scan_cross_exchange_funding_spreads normalizes one-hour and eight-hour settlement intervals, then compares a lower-funding long leg with a higher-funding short leg. Its annualized number is a comparison, not a forecast.scan_cross_exchange_perp_price_spreads compares public top-of-book quotes. It reports both entry-fee and round-trip-fee views, plus the smaller visible notional on the selected bid/ask levels. OKX contract counts are converted with the public instrument ctVal before notional is calculated.The scanners are original TypeScript implementations informed by the read-only monitoring workflow used in Market Depth Lab's local research. They do not vendor or modify the reference Python projects.
Neither scanner places orders. A row is a screening candidate, not proof of executable or risk-free arbitrage. Funding can change; REST snapshots are not simultaneous; Binance/OKX normally settle in USDT while Hyperliquid main perps settle in USDC; and deeper-book slippage, transfers, margin, liquidation, venue access and close-out prices remain outside the estimate.
The public package is market-depth-lab-mcp-server.
Use this configuration in an MCP client that supports local stdio servers:
{
"mcpServers": { "market-depth-lab": { "command": "npx", "args": ["-y", "market-depth-lab-mcp-server"] } } }
npx downloads the published package and starts the local read-only MCP process. No exchange login, wallet connection or API key is required.
git clone https://github.com/derkcc/market-depth-lab-mcp.git
cd market-depth-lab-mcp npm ci npm run build
Use the absolute path to dist/index.js in your MCP client:
{
"mcpServers": { "market-depth-lab": { "command": "node", "args": ["/absolute/path/to/market-depth-lab-mcp/dist/index.js"] } } }
Use the source checkout when you want to review or modify the implementation; use the npm configuration above for the shortest installation path.
Show the five Hyperliquid markets with the highest absolute current funding.
Include trailing 24h funding and explain who pays whom.
Compare BTC, ETH, SOL and HYPE funding on Binance, OKX and Hyperliquid.
Assume a 24-hour holding period and 12 bps of total round-trip costs. Show the current annualized spread, projected net carry and break-even hours.
Scan BTC, ETH and SOL perpetual top-of-book spreads across Binance, OKX and
Hyperliquid. Use round-trip taker fees, require at least $5,000 visible at the selected levels, and explain every non-execution boundary.
Analyze 0x... on Hyperliquid. Summarize gross exposure, effective leverage,
largest position and recent realized PnL. Do not give trading advice.
Within the monitored cohort, list the top BTC positions and separate longs
from shorts. State the cohort boundary before the ranking.
Estimate round-trip taker fees for a $25,000 tier-zero perpetual position.
| Capability | Data path |
|---|---|
| HYPE, wallet and Hyperliquid funding | Your local MCP process → public Hyperliquid info API |
| Cross-exchange funding spreads | Your local MCP process → public Binance USD-M, OKX and Hyperliquid market-data APIs |
| Cross-exchange price spreads | Your local MCP process → public Binance USD-M and OKX book-ticker APIs plus Hyperliquid l2Book |
| Active TWAPs | Your local MCP process → public HypurrScan endpoint, plus Hyperliquid price references |
| Large positions and top holders | Your local MCP process → Market Depth Lab's rolling read-only position index |
| Fee calculator | Runs locally; no network request |
The server has no analytics or telemetry. A wallet address submitted to analyze_hyperliquid_wallet is sent directly from your machine to the public Hyperliquid API. Position-index calls use https://data.marketdepthlab.com/v1/positions/latest.
Public exchange endpoints can be unavailable in some regions. Both cross-exchange tools expose per-venue available, partial or unavailable coverage and their error messages. They never silently claim that a two-venue or three-venue comparison was complete.
Market Depth Lab rotates through a monitored pool of public addresses. The index is useful for cohort-level market structure, but it is:
Every position tool reports the snapshot time, age, monitored-address count, staleness state and coverage boundary.
All variables are optional.
| Variable | Default | Purpose |
|---|---|---|
MDL_POSITION_INDEX_URL | https://data.marketdepthlab.com/v1/positions/latest | Remote read-only position index |
MDL_POSITION_INDEX_PATH | unset | Load a local JSON snapshot instead of the remote index |
MDL_MAX_SNAPSHOT_AGE_HOURS | 24 | Mark a position snapshot stale after this age |
MDL_REJECT_STALE | false | Return an error instead of labeled stale data |
MDL_HTTP_TIMEOUT_MS | 15000 | Per-request network timeout |
When MDL_POSITION_INDEX_PATH is set, the two position tools do not make a network request. Other live-data tools still use public upstream APIs.
npm ci
npm run check npm test npm pack --dry-run
The test suite performs an in-memory MCP handshake, verifies the nine tool definitions and calls the local fee tool through the protocol. Live upstream smoke tests should be run before each release, but are intentionally excluded from deterministic CI.
MIT