Climate Feeds
Server Details
Climate & Energy Feeds MCP.
The last two health checks of this connector failed. 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
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-climate-feeds
- GitHub Stars
- 0
- Server Listing
- climate-feeds
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 47 tools
Individual descriptions are unusually detailed and do differentiate most tools, but real overlap remains: ask_pipeworx_beta is explicitly stated to be identical to ask_pipeworx, and the prediction-market cluster (polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread, prediction_calibration, updown_venue_compare) has boundaries an agent must parse long paragraphs to resolve. discover_tools vs suggest_questions vs ask_pipeworx is another trio with fuzzy entry-point overlap.
All identifiers are snake_case, which keeps it readable, but the verb pattern is mixed: verb_noun (resolve_entity, validate_claim, list_feeds, read_feed, forget), bare-noun (entity_profile, company_facts, polymarket_edges, pipeworx_trending), and noun_verb (ai_visibility_check, prediction_calibration, updown_divergence_rate). No single predictable convention lets an agent guess a name.
47 tools is far past a well-scoped surface, and several earn their place only as duplicates or near-duplicates (ask_pipeworx / _beta / _grounded, plus the meta tools discover_tools, suggest_questions, pipeworx_trending, pipeworx_feedback). The count also badly mismatches the server's stated identity as 'Climate Feeds,' where only three tools (list_feeds, read_feed, fetch_feed) are actually about feeds.
Judged as a general data platform the surface is broad, but judged against the stated domain (climate/energy feeds) it is notably thin: list/read/fetch exist with keyword filtering, but there is no create/update/delete for feeds, no cross-feed search, and no history. The rest of the catalog (subscriptions, memory, prediction markets, company data) is well covered internally but is largely unrelated to the server's stated purpose, making the real gaps hard to assess.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Related MCP Servers
- AlicenseAqualityFmaintenanceOne-call Australian energy-market plumbing via AEMO — cited, structured responses for market data and analysis, not a data broker.5196 PyPIMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for EmonCMS energy monitoring API, enabling AI assistants to query energy feeds, inputs, and historical data.1MIT
- AlicenseNot gradedqualityDmaintenanceCO2 & Climate Intelligence MCP — live EU ETS carbon price, real-time grid carbon intensity, 50 blockchain carbon footprints (Bitcoin 1513 kWh/tx vs VeChain 0.00024 kWh/tx), VeChain DNV ISO14040/14044 certified. 11 tools.MIT
- AlicenseBqualityBmaintenanceProvides real-time European and GB electricity grid data via MCP, including generation, prices, carbon intensity, and grid infrastructure.4470 npm7MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.