Skip to main content
Glama
AdithyanandanArun

HandoffOS

by AdithyanandanArun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to HandoffOS

No user-submitted related servers found.

    Related Servers

    • mmc-mcp by modelmycontext

      mmc-mcpofficial

      modelmycontext
      F
      license
      Not graded
      quality
      F
      maintenance
      MCP server that lets AI agents execute structured business processes by exposing process steps as tools with a sequenced event bus to prevent skipping steps.
      1
      -

    • docintel-mcp

      reshma449
      A
      license
      Not graded
      quality
      C
      maintenance
      A document intelligence MCP server that extracts text and structured fields from business documents, routes low-confidence extractions to a human review queue, and enables searching across processed documents.
      MIT

    • SupplyChainMCP

      amitverma102
      F
      license
      Not graded
      quality
      B
      maintenance
      Enterprise-grade MCP server for intelligent supply chain analytics, enabling managers to investigate forecast accuracy, vendor performance, demand trends, and root causes using natural language.
      -
    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.2/5.0

    Scored across 13 tools

    Disambiguation3/5

    Most tools are distinct, but what_if_multi and simulate_resolution both simulate without changing live workflow state, differing mainly in scope (multi-node vs. single resolution), which could confuse an agent. Other tools are clearly separated by action and resource.

    Naming Consistency4/5

    The naming convention is overwhelmingly verb_noun (ingest_event, detect_blockers, execute_action), but 'what_if_multi' breaks the pattern by not starting with a verb. No camelCase or mixed conventions exist, so the inconsistency is minor.

    Tool Count5/5

    Thirteen tools is well within the optimal 3-15 range and each tool addresses a distinct aspect of workflow management, from simulation and execution to audit and comparison, so the count feels appropriately scoped.

    Completeness3/5

    The set covers core workflow operations like simulation, execution, rollback, prediction, and audit, but lacks an explicit approval tool even though plan_next_actions references approvals. Additionally, workflow retrieval is only implicit through compare_workflows, leaving a moderate gap in the lifecycle.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources