Skip to main content
Glama
mitchallen

Synthetic Orders MCP Server

by mitchallen

Related Servers

Alternatives to Synthetic Orders MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables validation of USDⓈ-M Futures trade intents by normalizing natural-language orders, fetching live Binance market and account state, applying deterministic risk rules, and producing tamper-evident preflight receipts before execution.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Pit Officer is free, open-source pre-trade risk control for AI trading agents over MCP. Manage accounts, limits, brokers and orders from a web panel. OpenPit checks each order and rejects limit breaches before broker submission. Limits cover order size, rate, spending and P&L stops that block new orders until unblocked. Runs locally in Docker; agents never hold broker keys.
      2
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables stock assessment and replenishment by exposing three deterministic tools: inspect stock positions, raise replenishment orders, and check order status. Includes an auditable local client and follows a security-first design with limited API surface.
      -
    • A
      license
      A
      quality
      C
      maintenance
      Provides an in-memory mock commerce backend for shopping agents, enabling product search, order creation, simulated payment, automatic shipping/delivery progression, and refund workflows. It lets developers test full shopping-agent lifecycles deterministically without real products, credentials, or funds.
      7
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables users to search simulated NSE instruments, get quotes and account state, preview trades, and place or cancel orders only after explicit confirmation, using short-lived previews and persistent JSON account state.
      8
      MIT

    TDQS

    A4.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: check_target verifies API connectivity, preview_order generates a single order without sending, and send_orders generates and sends multiple orders. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (check_target, preview_order, send_orders). The naming is predictable and uniform.

    Tool Count5/5

    With 3 tools, the server is well-scoped for its purpose of generating and sending synthetic orders. Each tool serves a distinct function without redundancy or unnecessary bloat.

    Completeness5/5

    The tool set covers the essential workflow: checking the target, previewing an order, and sending orders. The ability to replay seeds in send_orders addresses the need for reproducibility, leaving no obvious gaps in the stated domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues