Skip to main content
Glama
chanyou0311

aiseg2-mcp

by chanyou0311

Related Servers

Alternatives to aiseg2-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      Read-only MCP server integrating with the Victron VRM API to monitor solar systems, batteries, alarms, and more.
      41
      9 npm
      6
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      Read-only MCP server for querying solar generation, consumption, and DER telemetry from SolarNetwork via the SolarQuery API. Zero-config against a public demo node.
      5
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for EmonCMS energy monitoring API, enabling AI assistants to query energy feeds, inputs, and historical data.
      1
      -
    • A
      license
      A
      quality
      C
      maintenance
      A lean Model Context Protocol (MCP) server that gives AI assistants like Claude structured access to a SolarEdge PV installation via the official SolarEdge Monitoring API.
      4
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server for the Octopus Energy Japan GraphQL API that allows users to retrieve electricity consumption, cost estimates, and contract details. It enables 30-minute interval usage analysis and postal code area searches while ensuring privacy by excluding personal address information.
      3
      17 npm
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Unofficial MCP server for the messdienst24.de utility portal, providing tools to retrieve heating and hot-water consumption data, download PDF reports, and compare usage trends.
      3
      MIT

    TDQS

    A4.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct aspect: instantaneous overview, per-circuit draw, canonical names, daily totals, historical energy, and historical cost. The only slight overlap is get_power_flow's top circuits vs get_circuit_breakdown, but descriptions clearly differentiate summary versus full detail.

    Naming Consistency5/5

    All tools use snake_case verb_noun patterns: get_ for data retrieval and list_ for enumerating resources. The naming is consistent and predictable, following a clear convention.

    Tool Count5/5

    6 tools is well-scoped for a read-only energy monitoring API. Each tool provides a distinct piece of data without being redundant or overwhelming.

    Completeness5/5

    The tool set covers current status, per-circuit breakdown, canonical circuit list, daily cumulative totals, long-term history, and cost history. For a monitoring-focused server, this is complete and leaves no obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues