Skip to main content
Glama

Related Servers

Alternatives to trading-swarm-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      A local-first, deterministic, read-only MCP server that audits test suites for false-green tests, tautological assertions, and mock-contract drift, ensuring tests truly validate production code. It provides tools to detect test fidelity issues, verify mock drift, and synthesize strict mock contracts.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides MCP tools for local code validation with execution evidence, enabling users to run planned checks on projects and receive JSON results that distinguish passing, failing, and incomplete outcomes.
      396 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for natural-language daily stock/ETF strategy backtesting. It provides constrained tools for strategy specification, data validation, queue-based backtests, and verifiable result artifacts.
      1
      Apache 2.0

    TDQS

    A3.9/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool targets a distinct artifact or check: order validation, feature audit, rebalance planning, cost conversion, genome validation, sizing explanation, promotion verdict, and portfolio optimization. There is mild thematic overlap in the risk/sizing family (validate_order, explain_sizing, plan_rebalance all touch risk gates), but descriptions make the boundaries clear enough that misselection is unlikely.

    Naming Consistency5/5

    Every tool follows a uniform dot-prefixed snake_case convention (warden.<name>). Most are verb_noun (validate_order, audit_features, plan_rebalance, validate_genome, explain_sizing, optimize_portfolio), with a couple noun-first variants (cost_check, promotion_verdict) that remain clearly readable and consistent in style.

    Tool Count5/5

    Eight tools is well-scoped for a risk/validation gatekeeper domain. Each tool covers a distinct responsibility (order gating, feature audit, rebalance, cost model, genome identity, sizing, promotion, optimization) with no obvious redundancy.

    Completeness4/5

    The surface covers the core risk-gating lifecycle from order validation through rebalance planning, cost modeling, sizing, and promotion verdicts, and explicitly documents that it never routes trades (a deliberate boundary, not a gap). Minor gaps exist around state/query operations (e.g., fetching current floors or drift history), but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues