Octopus Energy
Server Details
Octopus Energy public API MCP — UK energy tariffs & products.
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 28.8% over 42 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-octopus-energy
- GitHub Stars
- 0
- Server Listing
- mcp-octopus-energy
TDQS
Scored across 35 tools
Most tools have distinct purposes, but there is significant overlap among ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research—all route questions to data sources with varying grounding and depth. Similarly, polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, and polymarket_fill_risk all relate to Polymarket trading edges but are positioned as separate tools, making it easy to choose the wrong one for a given analysis. Descriptions help guide selection but the boundaries are not crisp.
The vast majority of tools follow a consistent snake_case verb_noun or noun_noun pattern (e.g., list_products, product_details, entity_profile, scan_competitor_ai_presence). A few names like ask_pipeworx, remember, and forget are less descriptive but still fit a coherent style. No camelCase mixing.
35 tools is heavy for a single MCP server, even though the domain (Pipeworx data gateway plus Octopus Energy utilities) is broad. Several tools are experimental or meta (ask_pipeworx_beta, pipeworx_trending, suggest_questions) and could be folded into others. The count feels on the edge of unmanageable.
The tool set covers a wide range of operations: question answering, entity resolution, comparisons, research, memory management, subscriptions, and multiple data domains including energy tariffs and prediction markets. Lifecycle operations for subscriptions (subscribe/unsubscribe/list) and memory (remember/recall/forget) are fully present. Gaps exist for direct querying of some data sources without going through the higher-level wrapper tools, but the surface is largely complete for the intended use cases.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "market": "when-will-bitcoin-hit-150k" - }, - { - "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k" - } -]New value: +[ + { + "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination" + }, + { + "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination" + } +] - changed
Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
2 tool updates
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "market": "will-bitcoin-reach-100k-in-july-2026" - }, - { - "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026" - } -]New value: +[ + { + "market": "when-will-bitcoin-hit-150k" + }, + { + "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k" + } +] - changed
Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
- Changed
polymarket_kalshi_spread2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "topic": "fed" - }, - { - "topic": "btc" - } -]New value: +[ + { + "topic": "fed" + }, + { + "topic": "btc" + }, + { + "topic": "bitcoin" + }, + { + "topic": "fed rate decision" + } +] - changed
Input schema / properties / topic / descriptionPrevious value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."
1 tool update
- Changed
entity_profile3 fields changed- changed
Input schema / properties / type / descriptionPrevious value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon." - changed
Input schema / properties / type / enumPrevious value: -[ - "company" -]New value: +[ + "company", + "ticker" +] - changed
Input schema / properties / value / descriptionPrevious value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."
Related MCP Connectors
Energi Data Service (Energinet) MCP — Denmark's official open energy data.
Carbon MCP — UK Carbon Intensity API (free, no auth)
Elexon BMRS Insights MCP — Great Britain electricity grid & market data.
NESO MCP — Great Britain electricity grid open data (api.neso.energy)
Related MCP Servers
- AlicenseBqualityAmaintenanceProvides real-time European and GB electricity grid data via MCP, including generation, prices, carbon intensity, and grid infrastructure.44216 npm6MIT
- AlicenseAqualityDmaintenanceAn 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.317 npm1MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for real-time electricity prices, carbon intensity, and energy analytics across 41+ zones in Europe, Great Britain, the United States, and Australia. Query live prices, compare zones, check gas storage levels, get green scores, find optimal charging windows, and access advanced analytics. Free Basic tier requires no API key. Install via npx gridpulse-mcp or connect directly via Streamab-
- AlicenseAqualityBmaintenanceOne-call Australian energy-market plumbing via AEMO — cited, structured responses for market data and analysis, not a data broker.5130 PyPIMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.