Back to Browse

Markettrace Agent Feed MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

Crypto perps data for AI agents: funding rates, open interest, liquidations, order book, CVD.

About

Crypto perps data for AI agents: funding rates, open interest, liquidations, order book, CVD.

Remote endpoints: streamable-http: https://api.markettrace.ai/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 0 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

Endpoint verified · Requires authentication · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "ai-markettrace-agent-feed": {
      "url": "https://api.markettrace.ai/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

MarketTrace agent-feed

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.

This 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.


What it serves

6 assets (BTC, ETH, SOL, BNB, XRP, DOGE) across Binance, Bybit, OKX, Hyperliquid:

ToolWhat it answers
get_market_stateOne normalized snapshot: funding + multi-year percentile, OI, volume, CVD, order-book imbalance, liquidations, basis, drivers. "Is ETH positioning stretched?"
get_funding_percentileCurrent funding ranked against its own multi-year history (0–100) + same-sign streak.
get_liquidations_recentCross-exchange liquidation totals for a window: USD, long/short split.
get_ohlcvConsolidated cross-exchange candles (5m…1d) for ATR/range/RV math.
get_conditional_outcomesMeasured forward-return history after a stated condition — base rates instead of folklore. "What happened historically after funding above the 90th percentile?"
get_state_historyTime series of any numeric state field from the 15-minute archive — the trend view behind the snapshot.

Data: funding rates, open interest, cumulative volume delta (CVD), order-book depth, liquidations, OHLCV candles.

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.

Connect

Claude (web/desktop): Settings → Connectors → Add custom connectorhttps://api.markettrace.ai/mcp → authorize (email magic link).

Claude Code:

claude mcp add --transport http markettrace 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.

Local stdio bridge (this repo)

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

Things to ask

  • "What's the market state for BTC — is positioning stretched?"
  • "What happened historically after funding above the 90th percentile?"
  • "How did open interest build over the last 3 days?"
  • "How much got liquidated on ETH in the last hour — longs or shorts?"

Terms

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.

Reviews

No reviews yet

Be the first to review this server!

Markettrace Agent Feed MCP Server - Crypto perps data for AI agents: funding rates, open | MCP Marketplace