Skip to main content
Glama
Open Science MCP

Open Science MCP

by imjszhang

Related Servers

Alternatives to Open Science MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents and MCP clients to run research as an explicit scientific process: forming hypotheses, designing and executing sealed experiments, capturing observations and artifacts, linking claims to supporting evidence, and reviewing provenance. Exposes coordinated MCP services so users can inspect, reproduce, and audit every step from question to conclusion rather than trusting an opaque final answer.
      46
      21
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to scaffold trading strategies, run backtests locally or in cloud workspaces, fetch session analytics, and manage research labs against an algorithmic trading platform backend.
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients and agents to list tunable OpenROAD Flow Scripts parameters, launch guarded flow runs, retrieve setup/hold timing, power, area, utilization, and DRC metrics, and read timing, DRC, or congestion report tails.
      -
    • A
      license
      C
      quality
      B
      maintenance
      Enables AI clients to create and read structured research records—projects, questions, specifications, implementations, executions, artifacts, evidence, evaluations, comparisons, analyses, and reports—through MCP while keeping scientific judgments and approvals human-controlled.
      37
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to drive Open Reality OS end-to-end: upload scans, follow reconstruction jobs, sync scenes as context, run measurements and path planning, execute scene agents, and export robot-training data to disk.
      41
      24 npm
      656
      BSD 2-Clause "Simplified"

    TDQS

    A3.7/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: status inspection, project management, session listing/reading, run lifecycle (start/get/wait/cancel), plan access, and artifact retrieval. No two tools overlap in function; get_run and wait_run serve different needs (status vs. waiting).

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using lowercase with underscores (e.g., list_projects, start_run, cancel_run). The naming is predictable and unambiguous.

    Tool Count5/5

    With 12 tools, the count is well within the ideal range for a domain-specific server. Each tool serves a distinct purpose in the research workflow, covering projects, sessions, runs, plans, and artifacts without redundancy.

    Completeness4/5

    The tool surface covers the core lifecycle: project creation, session listing/reading, run initiation and control, plan viewing, and artifact access. Minor gaps exist (e.g., no update/delete for projects, no explicit run listing), but these do not block primary workflows and are likely handled via other means.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues