Skip to main content
ClaudeWave
MarketTrace avatar
MarketTrace

markettrace-agent-feed

Ver en GitHub

Front door for the MarketTrace agent-feed — read-only crypto perps microstructure MCP for AI agents. Hosted at api.markettrace.ai/mcp (ai.markettrace/agent-feed in the MCP registry).

MCP ServersRegistry oficial0 estrellas0 forksPythonMITActualizado 1mo ago
Install in Claude Code / Claude Desktop
Method: NPX · mcp-remote
Claude Code CLI
claude mcp add markettrace-agent-feed -- npx -y mcp-remote
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "markettrace-agent-feed": {
      "command": "npx",
      "args": ["-y", "mcp-remote"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
Casos de uso

Resumen de MCP Servers

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

- **Hosted MCP**: `https://api.markettrace.ai/mcp` (Streamable HTTP, OAuth — no API keys)
- **Official registry**: [`ai.markettrace/agent-feed`](https://registry.modelcontextprotocol.io/v0/servers?search=ai.markettrace)
- **Docs**: https://markettrace.ai/agents

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**:

| Tool | What it answers |
|---|---|
| `get_market_state` | One normalized snapshot: funding + multi-year percentile, OI, volume, CVD, order-book imbalance, liquidations, basis, drivers. *"Is ETH positioning stretched?"* |
| `get_funding_percentile` | Current funding ranked against its own multi-year history (0–100) + same-sign streak. |
| `get_liquidations_recent` | Cross-exchange liquidation totals for a window: USD, long/short split. |
| `get_ohlcv` | Consolidated cross-exchange candles (5m…1d) for ATR/range/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. |

**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 connector* →
`https://api.markettrace.ai/mcp` → authorize (email magic link).

**Claude Code:**

```bash
claude mcp add --transport http markettrace https://api.markettrace.ai/mcp
```

**Stdio-only clients** (via the standard OAuth-capable bridge):

```bash
npx -y mcp-remote https://api.markettrace.ai/mcp
```

More client configs in [`examples/mcp-configs.md`](examples/mcp-configs.md).

## Local stdio bridge (this repo)

[`mcp_server.py`](mcp_server.py) is a zero-dependency stdio bridge: it starts
and answers introspection (`initialize`, `tools/list`) with no credentials —
the bundled [`tools.json`](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`).

```bash
python3 mcp_server.py            # Python 3.9+, no dependencies
```

Or with Docker:

```bash
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](https://markettrace.ai/privacy) ·
[Terms of Service](https://markettrace.ai/terms) ·
Contact: support@markettrace.ai

The bridge in this repo is MIT-licensed ([LICENSE](LICENSE)); the hosted
service is governed by the Terms above.
ai-agentsbinancebybitcryptofunding-ratehyperliquidliquidationsmarket-datamcpmcp-servermodel-context-protocolokxopen-interestorder-bookorderflowperpetual-futurestrading

Lo que la gente pregunta sobre markettrace-agent-feed

¿Qué es MarketTrace/markettrace-agent-feed?

+

MarketTrace/markettrace-agent-feed es mcp servers para el ecosistema de Claude AI. Front door for the MarketTrace agent-feed — read-only crypto perps microstructure MCP for AI agents. Hosted at api.markettrace.ai/mcp (ai.markettrace/agent-feed in the MCP registry). Tiene 0 estrellas en GitHub y se actualizó por última vez 1mo ago.

¿Cómo se instala markettrace-agent-feed?

+

Puedes instalar markettrace-agent-feed clonando el repositorio (https://github.com/MarketTrace/markettrace-agent-feed) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.

¿Es seguro usar MarketTrace/markettrace-agent-feed?

+

MarketTrace/markettrace-agent-feed aún no ha sido auditado por nuestro agente de seguridad. Revisa el repositorio original en GitHub antes de usarlo en producción.

¿Quién mantiene MarketTrace/markettrace-agent-feed?

+

MarketTrace/markettrace-agent-feed es mantenido por MarketTrace. La última actividad registrada en GitHub es de 1mo ago, con 0 issues abiertos.

¿Hay alternativas a markettrace-agent-feed?

+

Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.

Despliega markettrace-agent-feed en tu cloud

Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.

¿Mantienes este repo? Añade un badge a tu README

Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.

Featured on ClaudeWave: MarketTrace/markettrace-agent-feed
[![Featured on ClaudeWave](https://claudewave.com/api/badge/markettrace-markettrace-agent-feed)](https://claudewave.com/repo/markettrace-markettrace-agent-feed)
<a href="https://claudewave.com/repo/markettrace-markettrace-agent-feed"><img src="https://claudewave.com/api/badge/markettrace-markettrace-agent-feed" alt="Featured on ClaudeWave: MarketTrace/markettrace-agent-feed" width="320" height="64" /></a>

Más MCP Servers

Alternativas a markettrace-agent-feed