Skip to main content
Glama
CodeNinja1126

KETI FLOW MCP

by CodeNinja1126
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to KETI FLOW MCP

No user-submitted related servers found.

    Related Servers

    • GridWatch MCP

      mohithchow
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server exposing distributed industrial asset data (battery storage, EV chargers, solar arrays) with tools for asset status, geospatial search, alerts, anomaly explanation, and load simulation.
      556 npm
      MIT

    • motor-telemetry-mcp

      0xcf02
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes industrial motor telemetry data to AI agents via MCP and REST, enabling natural-language queries about motor status, health, and alerts. Provides a single tool and resource for retrieving real-time motor metrics and escalating critical conditions.
      MIT

    • ML MCP Server

      pktcopilot2
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables training and using machine learning models on local CSV datasets or data from other MCP servers, supporting tasks like forecasting, regression, classification, and anomaly detection.
      -

    • Energy Prediction MCP Server

      Davad122
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI-powered analysis and prediction of household energy consumption through machine learning models, providing historical consumption breakdowns, price queries from Spanish electricity markets, and personalized energy optimization recommendations.
      -
    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/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools address completely different physical devices (blower vs. pump), so there is no ambiguity in their purposes. Each has a clear and distinct function.

    Naming Consistency5/5

    Both tools follow the same pattern of 'get_optimal_<device>_<control/angle>', using consistent verb_noun structure and snake_case. The minor difference in the last word (angle vs control) does not break consistency.

    Tool Count3/5

    With only 2 tools, the server is very narrowly scoped. While this may be acceptable for a focused use case, it feels minimal for a general flow control system, suggesting the surface is thin.

    Completeness2/5

    The tools cover only optimization for two specific devices. There are no tools for monitoring current state, setting parameters, or managing other equipment, leaving significant operational gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources