Cex Watch

What is Cex Watch about?

Cex Watch aggregates publicly available REST endpoints from Binance, OKX, Bybit, Coinbase, and Kraken. It exposes four MCP tools—listing exchanges, fetching the latest trading pairs, comparing spot taker fees, and checking API health—so AI assistants can answer exchange‑related questions without relying on closed‑source SaaS or API tokens.

How to use Cex Watch?

1. Install – via pip (pip install cex-watch-mcp) or by cloning the repository and installing in editable mode.
2. Run the server – execute cex-watch-mcp which starts a stdio‑based MCP server.
3. Configure your AI client – add an entry to the MCP configuration pointing to the command (e.g., uvx cex-watch-mcp).
4. Ask questions – prompt the AI with the supported tool names such as list_exchanges, get_latest_listings, compare_fees, or get_exchange_status.

Key Features

• Unified access to five major CEXs through a single MCP server.
• Four built‑in tools covering exchange enumeration, active listings, fee comparison, and health monitoring.
• Daily snapshots stored in the repository via GitHub Actions for historical diffing.
• Fully auditable adapters (~80 lines each) that hit only documented public endpoints.
• Zero authentication – no API keys or SaaS backends required.

Use Cases

• Enabling AI chat assistants to provide up‑to‑date exchange information for users.
• Tracking fee changes across exchanges for arbitrage or cost‑analysis bots.
• Detecting API outages or latency spikes in real time.
• Comparing available trading pairs when building portfolio tools.
• Historical research by cloning the repo and diffing daily JSON dumps.

FAQ

Q: Do I need an API key? A: No. All data comes from public REST endpoints.

Q: Which exchanges are supported? A: Binance, OKX, Bybit, Coinbase, and Kraken (more planned).

Q: Can I get real‑time updates? A: Currently the server polls daily; a WebSocket‑based streaming tool is planned for v0.3.

Q: How do I add a new exchange? A: Follow the docs/adding-new-exchange.md guide – implement an ~80‑line adapter and register it.

Q: Is the data stored permanently? A: Daily snapshots are committed to the data/ folder; you can clone the repo to retain the history.

cex-watch-mcp

An open MCP server for monitoring centralized crypto exchanges. No backend SaaS. No API token. Every data source is a public REST endpoint you can audit.

Why this exists

CEX monitoring tools today are either:

• Closed-source SaaS (you pay a token, you trust a backend you can't see), or
• Per-exchange one-offs (one script per exchange, never reused)

cex-watch-mcp is a small MCP server that gives an AI assistant unified, auditable access to a fixed set of CEX data dimensions. Every adapter is ~80 lines hitting a documented public endpoint. Read the source, run it yourself.

It plays nicely alongside broader news servers like opennews-mcp — they cover 84 sources across news/onchain/listings; this one stays narrow on CEXes and stays open.

What it does

Exposes 4 MCP tools to your AI assistant:

Tool	What it answers
list_exchanges	"Which exchanges does this server cover?"
get_latest_listings	"What pairs is OKX currently trading?"
compare_fees	"Which CEX has the cheapest spot taker fee right now?"
get_exchange_status	"Is Binance API healthy? What's the latency?"

Currently covers Binance, OKX, Bybit, Coinbase, Kraken. New adapters are ~80 lines — see docs/adding-new-exchange.md.

Install

Option 1 — Claude Desktop / Cursor / Cline

Add to your MCP config (location varies by client; see examples/):

{
  "mcpServers": {
    "cex-watch": {
      "command": "uvx",
      "args": ["cex-watch-mcp"]
    }
  }
}

Option 2 — pip + run directly

pip install cex-watch-mcp
cex-watch-mcp        # stdio MCP server

Option 3 — clone + run from source

git clone https://github.com/Zanecex101/cex-watch-mcp
cd cex-watch-mcp
pip install -e .
cex-watch-mcp

Example prompts

Once connected, ask your AI:

• "List the exchanges cex-watch covers."
• "Compare BTCUSDT spot fees across exchanges."
• "Is the Binance API healthy right now? What about Kraken?"
• "How many active spot pairs does OKX list today?"

Daily data dump

A GitHub Actions workflow runs the snapshot every day at 00:05 UTC and commits the result to data/:

data/
├── listings/2026-05-01.json     # active pairs per exchange
├── fees/2026-05-01.json         # default-tier maker/taker bps
├── status/2026-05-01.json       # health snapshot
└── latest.json                  # convenience symlink to today's roll-up

Anyone can git clone and diff day-over-day to find listing changes, fee bumps, or outages.

How it differs from opennews-mcp

	cex-watch-mcp	opennews-mcp
Open-source backend	✅ Every adapter visible in this repo	❌ Backend at 6551.io is closed
Auth required	❌ None (public APIs only)	✅ API token from 6551.io
Coverage	Narrow: CEX data only	Broad: 84+ sources, news + onchain + listings
Real-time	Not yet (polling-only v0.1)	✅ WebSocket subscriptions

opennews-mcp is the kitchen sink. cex-watch-mcp is the small auditable knife.

Roadmap

• v0.1 ← current. 5 exchanges × 4 tools, daily snapshots.
• v0.2 Add Bitget, KuCoin, Gate.io, MEXC, HTX. Withdrawal fee per coin.
• v0.3 WebSocket subscribe_listings tool (stream new pair events).
• v0.4 Anomaly detection: flag fee bumps, sudden delistings, API outages.

Issues and PRs welcome. See docs/adding-new-exchange.md for the contributor walkthrough.

Author

Built by Zane — independent crypto exchange researcher. Also editor at Cex101, where he writes multilingual exchange reviews.

License

MIT — see LICENSE.