Saltar al contenido
Logo de MarketIntell

Servidor MCP de MarketIntell

Qué servidores del registro oficial de MCP son de MarketIntell, si responden y qué ofrecen. Un programa comprobó cada dato; nada está copiado de la página del producto.

leído el 2026-10-13

← Volver a MarketIntell

De quién es el servidor
  • Nombre en el registroai.marketintell/marketintellverificado en el registro MCP

El nombre en el registro está bajo marketintell.ai. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

Cuando le preguntamoscomprobado el 2026-10-13
  • Estadorespondecomprobado el 2026-10-13
  • Herramientas17
  • El servidor se llamamarketintell
  • Versión del servidor0.1.0
  • Versión del protocolo2025-06-18

El 2026-10-13 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 679 ms.

Herramientas que ofrece17 herramientas · leído el 2026-10-13
  • chat

    Run a query through MarketIntell's brain (auto-routes to T1 fast agent or T2 CoT pipeline based on intent). Returns synthesized analysis with citations and trade setup when relevant.

  • chat_deep

    Run a query through MarketIntell's T3 supervisor — parallel specialists across technical/derivatives/macro/social/onchain/etc. plus synthesis. Slower (~25-40s) and costlier than `chat`. Pro tier only.

  • alpha_signals

    Fetch recent alpha signals — automated market intelligence. Crypto signals every ~10 min; equities (Beta) every ~30 min during US market hours. Filter by domain to narrow.

  • signal_performance

    Realized signal accuracy — rolling 30-day win rate over CLOSED trade signals, where a win is a real take-profit / in-profit expiry (net positive after fees & leverage) and a loss is a real stop-loss / losing expiry. Win-rate is over…

  • screener

    Token screening — find trending tokens, top gainers, and top losers. Use this to discover what's moving in the market right now.

  • portfolio_list

    List all portfolios owned by the authenticated key. Returns id, name, holdings, timestamps.

  • portfolio_create

    Create a new portfolio for the authenticated key. Holdings are token symbol + amount (+ optional entry_price and notes).

  • portfolio_analyze

    Compute PnL + risk assessment for a portfolio you own. Returns per-holding pnl, risk_assessment, and top_risks.

  • sessions_list

    List the authenticated key's recent chat sessions. Useful to resume prior conversations.

  • billing_status

    Return the authenticated key's plan, daily quota usage, monthly LLM-cost-cents, and cap. Mirrors GET /v1/billing/status.

  • health

    MarketIntell system health — uptime, cache stats, memory, provider circuit-breaker states.

  • register_challenge

    Step 1 of MCP self-signup. Returns a proof-of-work challenge. Solve locally (find a nonce whose sha256 has the required leading zero hex chars), then call `register` with { challenge_id, nonce, name }.

  • register

    Step 2 of MCP self-signup. Submit the challenge id + solved nonce to provision a fresh Free-tier API key. The key is shown ONCE — store it. Pro upgrades go through Stripe checkout; this tool only issues Free keys.

  • execute_propose_intent

    Propose a trade intent to the user's connected broker. Writes a pending row the user reviews + approves. Requires `trade` scope. Use this when an agent wants to act on a signal without placing the order itself.

  • execute_approve_intent

    Approve a pending trade intent and place the order at the broker. Returns the executed_order audit row. Requires `trade` scope.

  • execute_list_intents

    List the caller's recent trade intents (pending, executed, rejected). Requires `trade` scope.

  • execute_read_portfolio

    Read the caller's connected broker account snapshot — equity, cash, buying power, open positions. Requires `trade` scope.

Cómo conectar

Añade el servidor a la configuración de tu cliente MCP. Claude Desktop, Cursor y la mayoría de los demás clientes leen este formato:

{
  "mcpServers": {
    "marketintell": {
      "type": "http",
      "url": "https://api.marketintell.ai/mcp"
    }
  }
}

También se distribuye por: npm

Cada línea es algo que un programa encontró al buscar: la entrada del registro, la respuesta del propio servidor, una especificación que se puede leer. Si falta una línea, es que no la encontramos, no que no exista.