Skip to main content
Glama
J-X0

barrowman-associates-timeseries-mcp

by J-X0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to barrowman-associates-timeseries-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • WaveGuard

      gpartin
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that exposes GPU-accelerated anomaly detection to AI assistants via the Model Context Protocol. Provides two MCP tools: waveguard_scan (send training + test data in one call, returns per-sample anomaly scores and top explanatory features) and waveguard_health (check API and GPU status). Works on time series, JSON, numbers, text, and images — fully stateless.
      3
      4
      MIT

    • incident-mcp

      yoojung2
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables incident detection and analysis by identifying anomalies in metric time series and surfacing root-cause candidates and recommended actions. Supports both mock (synthetic) and VictoriaMetrics backends with identical MCP tool contracts for seamless development-to-production switching.
      MIT

    • mcp-live-telemetry

      Younes-Alaoui-Ismaili
      A
      license
      A
      quality
      B
      maintenance
      Exposes live industrial IoT telemetry to any MCP client, streaming simulated sensor data from a fleet of machines and detecting anomalies, with the ability to inject faults on demand.
      4
      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 1 tool

    Disambiguation5/5

    With only a single tool, there is no possibility of confusion between tool purposes. The analyze_series tool has a clear, specific mandate to detect and explain changepoints.

    Naming Consistency5/5

    The sole tool follows a clear verb_noun convention (analyze_series). No conflicting naming styles exist since there is only one tool.

    Tool Count2/5

    A single tool feels too few for a server branded as a timeseries MCP. The broader domain typically requires multiple operations, making the tool count significantly under-scoped.

    Completeness2/5

    The server offers only changepoint analysis and lacks supporting operations such as data retrieval, transformation, or lifecycle management. This creates significant gaps for workflows that require more than the single analysis.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources