Skip to main content
Glama
MeilinP

alpha-lab-mcp

by MeilinP

Related Servers

Alternatives to alpha-lab-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables 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.
      5
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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

    B3.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues