Skip to main content
Glama
imjszhang

Open Science MCP

by imjszhang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Open Science MCP

No user-submitted related servers found.

    Related Servers

    • GnosisLab

      cloudcell
      A
      license
      A
      quality
      A
      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
      2
      Apache 2.0

    • openreality-mcp

      reality-opened
      A
      license
      A
      quality
      A
      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
      187
      BSD 2-Clause "Simplified"

    • bourne mcp

      KozakHou
      A
      license
      A
      quality
      A
      maintenance
      Provides MCP access to plan and execute reproducible computational experiments with immutable execution plans, artifact provenance, verification checks, and support for direct, Slurm, and PBS backends.
      17
      Apache 2.0

    • research-bridge

      MrWolffy
      A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients to drive local Codex on a target Git repository: inspect repo state, start and follow up on tasks, review events and diffs, and record audit evidence for research governance.
      27
      2
      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

    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

    ActivityMaintained
    ResponsivenessNo issues

    Resources