oegb-kraken-mcp
Related Servers
Alternatives to oegb-kraken-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to query UK energy tariffs and products via the Octopus Energy public API.141 npmMIT
- AlicenseAqualityDmaintenanceEnables retrieval of electricity and gas consumption data from Octopus Energy accounts through their API, with support for date range filtering, pagination, and grouping by time periods.21ISC
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to inspect, query, and diagnose deployments, releases, runbooks, tasks, tenants, and infrastructure inside an Octopus instance through its APIs. Supports read-only and write-gated modes, toolset selection, and structured REST access for both interactive use and automation.501 npmMIT
- FlicenseNot gradedqualityCmaintenanceProvides read-only access to Shelly Cloud energy data, including live power, lifetime energy, and historical consumption with cost, enabling AI agents to monitor electricity usage without device control.1-
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to inspect, query, and diagnose problems within an Octopus Deploy instance, with tools for projects, deployments, releases, runbooks, tasks, tenants, Kubernetes, targets, certificates, accounts, and approvals, plus a structured REST backstop. Runs read-only by default-optional write and delete modes so assistants can also create releases, deploy, and run runbooks under confirmation.501 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to inspect, query, and diagnose an Octopus instance and perform release, deployment, runbook, and feature-toggle operations via curated tools and a REST backstop.501 npmMIT
TDQS
Scored across 5 tools
Each tool targets a distinct resource/action: product listing, product lookup, tariff rates, consumption, and account lookup. The descriptions explicitly cross-reference which tool feeds which (e.g. product codes to get_product, tariff codes to get_tariff_rates), leaving no meaningful overlap. An agent can select the right tool from the name alone.
All names follow a clean snake_case verb_noun pattern: list_products, get_product, get_consumption, get_tariff_rates, get_account. The lone 'list' prefix is semantically appropriate for a collection endpoint, not an inconsistency.
Five tools is well-scoped for a read-only Octopus Energy API surface: discovery, product detail, rates, account, and consumption. No tool feels redundant or extraneous, and nothing essential is obviously missing at this scope.
The lifecycle for reading products, tariffs, accounts, and consumption is covered with clear chaining via identifiers. Minor gaps exist: no standalone get_tariff metadata tool, no account listing/search to discover account numbers, and no meter-point lookup—though these are workaroundable and likely outside the intended read-only scope.