Skip to main content
Glama
SakethSripada

KalTrader MCP

by SakethSripada
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to KalTrader MCP

No user-submitted related servers found.

    Related Servers

    • kalshi

      evan-thedev
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to read Kalshi prediction market data, manage portfolios, and place or cancel trades only with explicit user approval.
      MIT

    • hyperliquid-mcp

      edkdev
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to securely trade on Hyperliquid perpetual exchange, including order placement, position management, market data retrieval, and vault operations via natural language.
      21
      MIT

    • kalshi-kernel

      copyleftdev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to interact with Kalshi event contracts and perpetual markets via a safety-focused MCP interface, with paper trading by default, strict schemas, and fail-closed behavior.
      Apache 2.0

    • ai-trader

      whchien
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants like Claude to run backtests, fetch market data, list strategies, and analyze trading algorithms via natural language.
      1,068
      GPL 3.0

    • Hunch

      FaustasRi
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that exposes Kalshi prediction markets as tools for AI agents, enabling conversational trading with safety features like demo mode, preview-before-place, and hard caps.
      MIT

    • Alpaca MCP Server

      wizkax
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural language trading operations through AI assistants, supporting stocks, options, crypto, portfolio management, and real-time market data.
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 60 tools

    Disambiguation5/5

    Each tool has a clearly distinct resource+action combination. The GET endpoints are differentiated by resource type (markets, events, series, orders, etc.), and write operations (create, amend, cancel, decrease, transfer) are scoped to specific resources. The paper trading tools are explicitly marked as simulated, and the meta tools (list/describe/call endpoint) serve a unique discovery purpose, so there is no meaningful ambiguity.

    Naming Consistency4/5

    The majority of tools follow a consistent get_* or verb_noun pattern (e.g., kalshi_get_market, kalshi_create_order_v2). However, there are minor deviations: 'kalshi_paper_order' and 'kalshi_paper_portfolio' lack a verb prefix, 'kalshi_stream_collect' reverses the verb, and 'kalshi_intra_exchange_instance_transfer' is a noun phrase. These are few relative to the total and do not significantly impede readability.

    Tool Count1/5

    With 60 tools, this server far exceeds the well-scoped threshold. Many endpoints could be served by the generic kalshi_call_endpoint or consolidated into parameterized tools. The count is an extreme mismatch for typical tool-set expectations and likely overwhelms an agent.

    Completeness5/5

    The tool surface is exceptionally complete for the Kalshi trading API, covering market data, order management (create, amend, cancel, decrease, batch), portfolio (balance, positions, fills, settlements), subaccounts, and paper trading. The generic kalshi_call_endpoint ensures that even endpoints without dedicated tools are accessible, leaving no obvious gaps.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources