alpha-lab-mcp
Related Servers
Alternatives to alpha-lab-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables offline-first alpha research by providing a local stdio interface to query run status and reports, list approved method cards, execute replay runs, and stop runs, all without any submission capability.5MIT
- FlicenseAqualityAmaintenanceEnables coding agents to discover schemas, prepare simulations, inspect retained evidence, compare runs, and manage authorized synthetic tools through a standalone stdio client.194 npm-
- AlicenseNot gradedqualityCmaintenanceExposes four stdio tools that let an agent research an application's documented interface, produce a validated single-use plan, and execute read-only operations against public HTTP JSON APIs, static HTML/JSON/text sources, and host-configured CLIs. Runs in-process with no listening port, accounts, or model dependency, returning bounded results while keeping inputs and outputs inside a host-enforced research-plan-execute lifecycle.MIT
- AlicenseNot gradedqualityBmaintenanceProvides LLM clients with market intelligence tools over stdio, including market snapshots, price history, sentiment scoring, evidence search, and research briefs, with saved-run resource access.AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables authenticated users to manage paper-trading accounts, place and cancel orders with simulated fills, view positions and P&L, search instruments, fetch bars, and run quant-strategy lifecycles over stdio or streamable HTTP.MIT
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to search local repositories and retrieve bounded, cited source chunks, look up full indexed chunks, and inspect index statistics through read-only MCP tools over stdio.MIT
TDQS
Scored across 5 tools
Each tool targets a distinct action: stopping a run, reading status, rendering a report, listing method cards, or executing replay. There is no meaningful overlap; even run_status and run_report are clearly separated by output type.
All tools share the alpha_ prefix and snake_case, and most follow an alpha_<resource>_<action> pattern. The pattern is slightly weakened by noun-like action words such as status and report, but it remains predictable and readable.
Five tools is a well-scoped size for a focused lab-run management server. Each tool has a clear role, and the count is neither bloated nor too thin.
The run lifecycle is partially covered with status, stop, report, and replay execution, but there is no run listing, standard run creation, or method-card update/review operation. Agents may need external context to select or manage runs.