Ir para o conteúdo
Logo de MarketIntell

Servidor MCP de MarketIntell

Quais servidores do registro oficial de MCP são de MarketIntell, se respondem e o que oferecem. Um programa verificou cada item; nada foi copiado da página do produto.

lido em 2026-10-13

← Voltar para MarketIntell

De quem é o servidor
  • Nome no registroai.marketintell/marketintellverificado no registro MCP

O nome no registro fica sob marketintell.ai. O registro só libera esse espaço de nomes para quem prova controle do domínio por DNS ou HTTP.

Quando perguntamosverificado em 2026-10-13
  • Estadorespondeverificado em 2026-10-13
  • Ferramentas17
  • O servidor se chamamarketintell
  • Versão do servidor0.1.0
  • Versão do protocolo2025-06-18

Em 2026-10-13 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 679 ms.

Ferramentas que oferece17 ferramentas · lido em 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.

Como conectar

Adicione o servidor à configuração do seu cliente MCP. Claude Desktop, Cursor e a maioria dos outros clientes leem este formato:

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

Também distribuído por: npm

Cada linha é algo que um programa encontrou ao procurar: o registro, a resposta do próprio servidor, uma especificação que se lê. Linha ausente quer dizer que não encontramos, não que não exista.