Skip to main content
Glama
ajibadedapo

FlowProof

by ajibadedapo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Related Servers

Alternatives to FlowProof

No user-submitted related servers found.

    Related Servers

    • pipen-mcp

      pwwang
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes pipen bioinformatics pipelines as MCP tools, allowing AI assistants to discover and run complex workflows through a progressive disclosure interface.
      117 PyPI
      1
      MIT

    • Researcher AI

      samsamurai301
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI-assisted scientific research workflow management through MCP, including project creation, ideation, experiment execution, and artifact handling, with integration for ChatGPT, Codex, and Claude Code.
      Apache 2.0

    • SciAgentKit

      ehsansyh
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP-native scientific skills for reproducible computational biology and AI-driven drug-discovery workflows. It combines deterministic scientific tools with an MCP server to give AI agents real computational capabilities.
      Apache 2.0

    • n8n MCP Server

      MrBozkay
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to programmatically create, manage, and orchestrate n8n workflows through a standardized MCP interface.
      MIT

    • provmcp

      AbhiAdhikari
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables provenance capture and replay verification for scientific MCP tool calls, using a signed hash-chained ledger and data-source release resolution.
      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

    A4.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a distinct purpose: listing, describing, running, status checking, result retrieval, and provenance. No two tools overlap in function, so an agent can easily select the correct one.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (list_pipelines, describe_pipeline, run_pipeline, get_run_status, get_results, get_provenance). The style is uniform and predictable.

    Tool Count5/5

    Six tools is well-scoped for a pipeline management server, covering discovery, execution, monitoring, results, and provenance without excess or redundancy.

    Completeness4/5

    The workflow from listing pipelines to retrieving results and provenance is fully covered. A cancel/abort run operation is missing, but the core lifecycle is otherwise complete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources