Skip to main content
Glama
mpmsds123

alpha-lab-mcp

by mpmsds123
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to alpha-lab-mcp

No user-submitted related servers found.

    Related Servers

    • alpha-lab-mcp

      MeilinP
      A
      license
      B
      quality
      B
      maintenance
      Enables local, offline ledger and replay operations for alpha research via five typed stdio tools, allowing status checks, report retrieval, method-card listing, replay execution, and run stopping without exposing live or submission capabilities.
      5
      MIT

    • MarketSage

      roshanrana
      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

    • flameox

      morluto
      A
      license
      C
      quality
      A
      maintenance
      Enables coding agents to query, compare, and audit local profiler traces, benchmarks, memory captures, and execution evidence without uploading code or data, using CLI and MCP interfaces.
      111
      115 PyPI
      114
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: run stop, run status, run report, method-card listing, and replay execution. Even the three run_* tools are clearly separated by whether they write state, read status, or render output.

    Naming Consistency4/5

    All names consistently use the alpha_ prefix, snake_case, and an object_operation structure. Minor inconsistency remains because stop, list, and execute are true verbs while status and report are nominalized operations.

    Tool Count5/5

    Five tools is a well-scoped size for this server's purpose. Each tool covers a distinct function with no apparent redundancy.

    Completeness4/5

    The set covers the core run workflow: execute/resume, stop, status, and report, plus method-card listing. However, there is no run-listing tool and no method-card detail or mutation tools, so agents must already know run IDs to operate effectively.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources