Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Crypto perps for AI agents: funding, OI, liquidations, order book, CVD, volume profile, footprint.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
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:
https://api.markettrace.ai/mcpRun this in your terminal
claude mcp add --transport http agent-feed https://api.markettrace.ai/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"agent-feed": {
"url": "https://api.markettrace.ai/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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"agent-feed": {
"type": "http",
"url": "https://api.markettrace.ai/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:
https://api.markettrace.ai/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.
We have not read this server’s tool list yet; we check endpoints in rotation.
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
The registry name was verified against the domain markettrace.ai (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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.
The GitHub repo last changed –, and the latest version (1.11.0) reached the registry 21 days ago.
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.
In the same category: Spec Driven Development, Remote Desktop Commander, TF Rooms
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
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.
Live room availability, rates and stay quotes for 12 New Leaf motels in Twin Falls, Idaho.
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.
Read-only crypto perps microstructure for AI agents — normalized cross-exchange market state with self-declared coverage and freshness on every metric. Facts and normalization, no verdicts: the agent interprets.
https://api.markettrace.ai/mcp (Streamable HTTP, OAuth — no API keys)ai.markettrace/agent-feedThis repo is the front door — connection configs, the interface contract, and a thin stdio bridge. The data pipeline itself (4-venue ingest, archives, normalization) is not open source.
9 assets (BTC, ETH, SOL, BNB, XRP, DOGE, HYPE, ZEC, ENA) across Binance, Bybit, OKX, Hyperliquid:
| Tool | What it answers |
|---|---|
get_market_state | One normalized snapshot: funding + its trailing 2-year percentile, OI, volume, CVD, order-book imbalance, liquidations, basis, drivers. *"Is ETH positioning stretched?"* |
get_funding_percentile | Current funding ranked against its own trailing 2-year window (0–100) + same-sign streak. |
get_liquidations_recent | Cross-exchange liquidation notional estimates for a window: USD, long/short split. |
get_ohlcv | Consolidated cross-exchange candles (5m…1d) with per-candle delta (taker buy − taker sell), for ATR, ranges, CVD and RV math. |
get_conditional_outcomes | Measured forward-return history after a stated condition — base rates instead of folklore. *"What happened historically after funding above the 90th percentile?"* |
get_state_history | Time series of any numeric state field from the 15-minute archive — the trend view behind the snapshot. |
get_volume_profile | Volume-profile levels per UTC day from the consolidated tape: POC, value area high/low, value-area width and its rank, a multi-day composite and naked POCs. *"Is price inside yesterday's value area?"* |
get_big_trades | Large aggressive orders (fills sharing venue, side and timestamp summed into one trade): per-side totals plus the biggest prints with venue, price and USD size. *"Were the whale market orders buying or selling?"* |
get_footprint_events | Order-book wall events from the 1-minute footprint: absorbed and pulled walls with peak, executed and closing size in USD, plus thin-book minutes. *"Were bid walls pulled before this drop?"* |
get_stacked_imbalances | Stacked footprint imbalances from the consolidated tape: diagonal buy and sell runs per candle (1m…1h) with price band and USD size. *"Where did aggressive buyers stack up on BTC this morning?"* |
help | A guide to the server itself: every tool grouped by the question it answers, a working example call for each, the symbols, how to read the scales, the limits, and where data without its own tool lives (open interest, CVD, funding rate). *"Which tool gives me open interest?"* |
Data: funding rates, open interest, cumulative volume delta (CVD), order-book depth, liquidations, OHLCV candles with per-candle delta, volume-profile levels, large aggressive orders, order-book wall events, stacked footprint imbalances.
Honesty model: every metric carries a coverage entry (venues, window depth, freshness); thin history answers with disclosed depth instead of made-up numbers; conditional outcomes go history_silent below the evidence floor; every response self-declares its age. Reports history, not predictions.
Claude (web/desktop): Settings → Connectors → *Add custom connector* → https://api.markettrace.ai/mcp → authorize (email magic link).
Every client signs in the same way: it opens a browser, you enter your email, and a sign-in link arrives. Open it on the same device and in the same browser where you started.
Claude Code (adding the server does not sign you in, so run both):
claude mcp add --transport http markettrace https://api.markettrace.ai/mcp
claude mcp login markettrace
Codex:
codex mcp add markettrace --url https://api.markettrace.ai/mcp
codex mcp login markettrace
Cursor: add this to ~/.cursor/mcp.json (or use *Add to Cursor* on https://markettrace.ai/agents) and sign in when Cursor asks:
{
"mcpServers": { "markettrace": { "url": "https://api.markettrace.ai/mcp" } } }
Stdio-only clients (via the standard OAuth-capable bridge):
npx -y mcp-remote https://api.markettrace.ai/mcp
More client configs in examples/mcp-configs.md.
mcp_server.py is a zero-dependency stdio bridge: it starts and answers introspection (initialize, tools/list) with no credentials — the bundled tools.json is a snapshot of the hosted server's own contract. Tool calls are proxied to the hosted endpoint when MARKETTRACE_BEARER is set; without it they return a pointer to the hosted OAuth endpoint instead of data. It holds no methodology — just a client.
Refresh the contract: tools.json is a {version, generated_at, tools} snapshot of the live server's tools/list — regenerate it by capturing that response and stamping the current contract version (mirrors feed.version in get_market_state).
python3 mcp_server.py # Python 3.9+, no dependencies
Or with Docker:
docker build -t markettrace-bridge . && docker run -i markettrace-bridge
Informational market data only — not financial advice. Privacy Policy · Terms of Service · Contact: support@markettrace.ai
The bridge in this repo is MIT-licensed (LICENSE); the hosted service is governed by the Terms above.