Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
WhaleScope MCP
Overview
Description from the maker (original English)
Binance Futures market intelligence: funding, OI, order book, klines, cross-exchange comparison.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://whalescope-mcp.jaringan.dev/mcpRun this in your terminal
claude mcp add --transport http whalescope https://whalescope-mcp.jaringan.dev/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"whalescope": {
"url": "https://whalescope-mcp.jaringan.dev/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"whalescope": {
"type": "http",
"url": "https://whalescope-mcp.jaringan.dev/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://whalescope-mcp.jaringan.dev/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account osindo-dev, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- … Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Otheri
- More stars than 0% of the other 18352 servers in this category
- Published to the registry more recently than 20% of the other 18352 servers in this category
- Basic checks equal to or better than 100% of the other 18352 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is WhaleScope MCP safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 3 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, Hunter Killer
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated 2 days ago
Install
Hunter Killer
by Irishman-Management-LLC
Liquidation walls, snapshot age, evidence labels and a public record. Managed OAuth.
Runs in the cloudUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
WhaleScope MCP — Binance Futures Market Intelligence
🇮🇩 Bahasa Indonesia | 🇬🇧 English
MCP server yang menyediakan data publik Binance USDS-M Futures (funding rate, open interest, long/short ratio, taker volume, candlestick, order book, volatility) plus pembanding Binance Spot (harga, order book, candlestick, CVD) sebagai tools yang bisa dipanggil Claude. Semua data yang disajikan bersifat publik read-only — tidak ada order/trading, tidak ada akses ke data akun pribadi.
Quick Deploy
Tombol ini clone repo + bikin Worker di akun Cloudflare kamu sendiri, termasuk provision KV namespace & D1 database baru otomatis (Cloudflare generate id/database_id baru buat akun kamu, gak perlu bikin manual). Bukan zero-touch sepenuhnya — biar jujur soal apa yang masih manual: setelah klik, kamu TETAP perlu set secret (Cloudflare gak bisa nebak value dari layanan eksternal) — lihat .dev.vars.example di repo ini buat daftar lengkap, atau Setup Proxy Vercel di bawah. PROXY_URL/PROXY_SECRET WAJIB (semua 46 tool butuh).
Tujuan
Menyediakan gambaran positioning pasar Binance Futures — bukan cuma harga, tapi juga *siapa* yang lagi buka posisi apa (retail vs top trader), *seberapa crowded* leverage-nya, dan *di harga berapa* likuiditas menumpuk — langsung dalam percakapan dengan Claude, tanpa perlu buka dashboard exchange terpisah.
Manfaat
- Satu pintu buat banyak sinyal. Funding rate, open interest, order book, dan order flow — semua lewat satu MCP connector, bukan gonta-ganti tab.
- Bisa bedain retail vs whale.
binance_get_top_trader_ratiokasih breakdown murni top-trader (terpisah daribinance_get_long_short_ratioyang blended) — berguna buat lihat kalau posisi retail dan whale lagi divergen. - Native Binance di mana itu penting. Harga, funding rate, klines, order book — semua lewat jalur native Binance (bukan derivasi pihak ketiga), supaya presisi terjaga terutama untuk pair kecil/kurang likuid.
- Gratis buat pemakaian personal — lihat bagian Biaya.
Kelebihan
- 29 tools mencakup lima sudut analisis: bias arah pasar, area harga kunci (order book), konfirmasi eksekusi (order flow/aggressor), pembanding Futures-vs-Spot (leverage-driven vs demand riil), dan market-wide scan (funding rate ekstrem lintas semua pair, atau bandingkan metrik across beberapa pair) — plus tool composite (
binance_analyze_pair) buat overview cepat tanpa banyak tool call, dan config/histori (threshold per-pair, basis time-series) yang tersimpan di Workers KV. - Read-only terhadap data pasar Binance — tidak ada order/trading. Satu- satunya tool yang menulis state (
binance_set_pair_threshold) cuma nyimpen preferensi threshold kamu sendiri di Workers KV, tidak menyentuh akun Binance/data pihak luar sama sekali. - Transparan soal keterbatasan tiap tool (lihat bagian di bawah), bukan dibungkus seolah semua data sempurna.
- Infrastruktur cukup dengan free tier (Cloudflare Workers + Vercel Hobby) untuk pemakaian personal — 100% Binance-native, tidak ada dependensi agregator pihak ketiga lagi.
Kekurangan
- Sebagian besar tool request/response. Funding/OI/klines/order book/ratio semua snapshot atau histori periodik. Data streaming yang ada terbatas:
binance_get_realtime_liquidations+binance_get_contract_events(via stream gateway VPS, lihat di bawah) — tidak ada push tick-by-tick untuk harga / order book. - Liquidation: SAMPLED, bukan lengkap. Sejak 2026-08-28 ada
binance_get_realtime_liquidations— WebSocket!forceOrder@arr(dstream.binance.com) di-buffer always-on di VPS Oracle Singapore (stream-gateway/, di luar Cloudflare — worker Cloudflare sendiri masih di-WAF-block dari Binance). Binance men-throttle stream ini maks 1 event/symbol/detik, jadi ini SAMPEL likuidasi, bukan tiap satu. Tetap cukup buat konfirmasi cluster stop-hunt dibinance_detect_mm_activity(proxy ke-3, price-anchored & sisi-hunt). Tidak ada histori liquidation jauh ke belakang (buffer 24 jam). - Setup awal butuh proxy Vercel (wajib) — bukan pasang-langsung-jalan, ada langkah konfigurasi manual sekali di awal.
- Tidak ada data wallet on-chain atau data dari exchange selain Binance Futures USDS-M.
Sumber data: satu jalur, 100% Binance native.
- Binance native, lewat proxy relay Vercel. Domain Binance (
fapi.binance.com) memblokir traffic dari Cloudflare Workers di level WAF (403, company-wide — sudah dites langsung dari worker ini, bukan asumsi). Vercel pakai IP pool berbeda, jadi tidak kena block yang sama. Worker Cloudflare relay lewat proxy kecil diproxy/(project Vercel terpisah, lihatproxy/README.md). Ini jalur untuk funding rate (current & histori), klines/OHLCV, bias multi-timeframe, realized volatility, statistik 24 jam, order book depth, aggregate trades, open interest (current & histori), long/short ratio (blended & top-trader), taker buy/sell volume ratio, dan harga spot (proxy juga relay ke Binance Spot APIapi.binance.comlewat parametermarket=spot, lihatproxy/README.md).
Konsekuensinya, worker ini butuh PROXY_URL/PROXY_SECRET (proxy Vercel, wajib buat semua 46 tool) — lihat bagian Setup di bawah.
Caching & state, tanpa kredensial tambahan. Response upstream (funding rate, klines, OI, dll — kecuali order book & aggregate trades yang butuh freshness ketat) di-cache bertingkat (5 detik-1 jam tergantung endpoint) lewat Cache API bawaan Cloudflare Workers, tidak perlu setup apapun. Threshold custom per-pair tersimpan di Workers KV (binding CONFIG_KV). Time-series (basis+funding+OI, dan 6 skor sinyal binance_detect_mm_activity) tersimpan di D1 (binding DB) — diisi otomatis oleh Cron Trigger tiap 5 menit untuk watchlist tetap 50 pair (SNAPSHOT_WATCHLIST di src/shared.ts, diurutkan market cap, mis. BTCUSDT, ETHUSDT, SOLUSDT, BNBUSDT, XRPUSDT, dst).
Cross-exchange, tanpa proxy tambahan. whalescope_compare_funding_across_exchanges akses Bybit/OKX/Hyperliquid LANGSUNG dari worker (dites dari edge Cloudflare beneran, gak kena WAF/geo-block kayak Binance) — gak ada kredensial atau setup tambahan buat 3 exchange itu.
Yang disediakan
| Tool | Fungsi | Sumber |
|---|---|---|
binance_get_funding_rate | Funding rate terkini + basis (deviasi mark vs index price) | Binance native |
binance_get_funding_rate_history | Tren funding rate dari waktu ke waktu | Binance native |
binance_get_spot_price | Harga spot Binance + basis riil vs mark price futures (beda dari basis di atas yang vs index price). Error jelas kalau pair futures-only (tidak listed di Spot) | Binance native (Spot) |
binance_scan_funding_extremes | Scan funding rate SEMUA pair Futures sekaligus (1 call bulk), kembalikan top pair paling crowded long/short | Binance native |
binance_get_open_interest | OI snapshot terkini | Binance native |
binance_get_open_interest_history | Tren OI naik/turun | Binance native |
binance_get_long_short_ratio | Rasio long vs short agregat (blended, semua trader) + tren | Binance native |
binance_get_top_trader_ratio | Rasio long/short KHUSUS top trader (breakdown murni, akun atau size posisi) | Binance native |
binance_get_order_book_depth | Snapshot order book (bid/ask), spread, wall terbesar | Binance native |
binance_get_order_book_imbalance | Imbalance volume bid vs ask di depth 5/10/20, dengan label bias (BULLISH/BEARISH/SEIMBANG) | Binance native |
binance_get_agg_trades | Trade individual granular (buy/sell aggressor) untuk deteksi absorption | Binance native |
binance_get_taker_volume_ratio | Tekanan beli/jual agresif (taker volume), statistik resmi Binance | Binance native |
binance_get_klines | Candlestick OHLCV per timeframe, dukung startTime/endTime (histori jauh ke belakang, buat backtest, maks 1500 candle/panggilan) | Binance native |
binance_get_multi_timeframe_bias | Bias Bullish/Bearish/Sideways di 5 timeframe sekaligus (1m/5m/15m/1h/1d) | Binance native |
binance_get_realized_volatility | Realized volatility historis (15m/1h) dari log-return, untuk kalibrasi lebar grid | Binance native |
binance_get_24hr_ticker | Ringkasan statistik 24 jam (rolling window resmi) | Binance native |
binance_get_spot_ticker_24hr | Statistik 24 jam versi Spot (harga, %change, VWAP, volume, jumlah trade) — bandingkan dengan versi Futures di atas | Binance native (Spot) |
binance_get_spot_book_ticker | Best bid/ask + qty real-time Spot, lebih ringan dari full order book | Binance native (Spot) |
binance_get_spot_order_book | Order book depth Spot (bid/ask, spread, wall terbesar) | Binance native (Spot) |
binance_get_spot_klines | Candlestick OHLCV Spot per timeframe, dukung startTime/endTime (maks 1000 candle/panggilan) | Binance native (Spot) |
binance_get_spot_agg_trades | Trade individual granular Spot (CVD riil, bukan leverage) | Binance native (Spot) |
binance_get_spot_avg_price | Harga rata-rata bergerak Spot (window beberapa menit, lebih stabil dari last-trade) | Binance native (Spot) |
binance_check_spot_listing | Cek apakah pair listed di Binance Spot + status trading — dipakai sebelum panggil tool Spot lain untuk pair yang belum pasti | Binance native (Spot) |
binance_analyze_pair | Overview cepat 1 pair (composite): funding, tren OI, tren top trader, taker volume, order book, bias harga — 6 tool sekaligus dalam 1 call | Binance native |
binance_compare_symbols | Bandingkan 1 metrik (funding rate, %change 24h, OI, top trader ratio, taker ratio) across 2-10 pair sekaligus, diurutkan dari paling ekstrem | Binance native |
binance_set_pair_threshold | Set threshold funding/basis custom per-pair (override default ±0.03%/±0.05%), tersimpan di Workers KV | Workers KV |
binance_get_pair_threshold | Cek threshold custom yang sudah di-set untuk sebuah pair | Workers KV |
binance_get_basis_history | Histori basis+funding+OI time-series (snapshot Cron tiap 5 menit ke D1) — selalu tersedia untuk watchlist tetap 50 pair, best-effort untuk pair lain yang sering di-query — deteksi "basis melebar lalu kembali" tanpa cek manual berkali-kali | D1 + Cron Trigger |
binance_get_orderbook_delta | 2 snapshot order book ~1-2 detik terpisah, bandingkan wall antar snapshot untuk deteksi spoofing RIIL (wall hilang tanpa harga crossing level itu) — beda dari binance_get_order_book_depth yang cuma 1 snapshot | Binance native |
binance_detect_mm_activity | Skor + tier (Weak/Moderate/Strong/Extreme) dari 6 sinyal MM/whale sekaligus (absorption, spoofing 2-snapshot RIIL, stop-hunt simetris + OI-drop proxy + trade-volume-concentration proxy, basis arbitrage, OI divergence, funding extreme) — ganti 5-6 tool call manual. Stop-hunt TETAP tanpa data liquidation riil (dihapus permanen), lihat Keterbatasan | Binance native |
binance_market_regime | Klasifikasi kondisi pasar: TRENDING_UP/DOWN, RANGING, BREAKOUT, ACCUMULATION, DISTRIBUTION — pakai ADX(14), tren OI, CVD, spike volatilitas/volume | Binance native |
binance_backtest_signal | Validasi empiris sinyal binance_detect_mm_activity: win rate/avg return/max drawdown dari histori sinyal D1 (watchlist tetap), forward return dihitung on-demand dari klines historis | D1 + Binance native |
whalescope_backtest_pipeline_decisions | Uji maju keputusan full_pipeline yang tersimpan di pipeline_decision_log (entry-alert Phase 2 + persist=true): win rate / avg return / SL-touch per keputusan (TRADE/WATCH/NO_TRADE) dan bucket skor (lt_40 / 40_55 / gte_55). Forward return on-demand dari klines, bukan kolom precompute, bukan auto-tune bobot | D1 + Binance native |
| binance_analyze_smart_money | Skor div
Only the beginning is shown; read the rest in the repo