trading-swarm-mcp
Related Servers
Alternatives to trading-swarm-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceA 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
- AlicenseNot gradedqualityBmaintenanceEnables local static analysis of deployed AI model artifacts over MCP, exposing audit, diff, capabilities, and rule-explanation tools without uploading model bytes.199 npm2Apache 2.0
- AlicenseAqualityAmaintenanceLocal-first production-readiness MCP server for AI-built apps. It runs read-only checks, produces an evidence-based readiness score, and guides fixes before launch.1111 npm7Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to run local, read-only audits that detect risky GitHub workflows, undocumented environment variables, possible credentials, and conflicting dependency configuration before merging.63 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides 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 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP 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.1Apache 2.0
TDQS
Scored across 8 tools
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.
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.
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.
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.