Skip to main content
Glama
Younes-Alaoui-Ismaili

mcp-live-telemetry

by Younes-Alaoui-Ismaili
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-live-telemetry

No user-submitted related servers found.

    Related Servers

    • forge-sandbox

      FoundryNet
      A
      license
      Not graded
      quality
      A
      maintenance
      A local, keyless MCP server simulating Forge's industrial telemetry kernel, enabling agents to normalize vendor-specific machine data, forecast breaches, and test integrations against realistic equipment data without credentials or persistence.
      MIT

    • connected-car-mcp

      somusathya
      A
      license
      A
      quality
      C
      maintenance
      Provides telemetry, rule-based anomaly detection, and maintenance recommendations for a synthetic connected-vehicle fleet through five narrow MCP tools, enabling fleet monitoring and analysis without external APIs.
      5
      MIT

    • digital-twin-mcp

      xici001
      A
      license
      A
      quality
      C
      maintenance
      Exposes digital twin device data capabilities as MCP tools, allowing MCP clients to query device status, read real-time metrics, fetch time-series data, and check alerts. Includes a simulated PLC driver with a clean interface for connecting real devices via OPC-UA, Modbus, or gateway APIs.
      6
      MIT

    • 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.
      851 npm
      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.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a unique and clearly distinct purpose: listing devices, retrieving telemetry, detecting anomalies, and injecting faults. There is no overlap.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (list_devices, get_telemetry, get_anomalies, simulate_fault), making them predictable and easy to learn.

    Tool Count5/5

    With 4 tools, the set is concise but covers all essential operations for a telemetry monitoring and simulation domain. Each tool serves a necessary role without redundancy.

    Completeness4/5

    The tool surface covers listing, reading telemetry, anomaly detection, and fault injection. A minor gap is the absence of a tool to cancel an active fault, though faults self-reset after a given duration.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources