Climate Feeds
Server Details
Climate & Energy Feeds MCP.
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
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-climate-feeds
- GitHub Stars
- 0
- Server Listing
- climate-feeds
TDQS
Scored across 34 tools
Several clusters do nearly the same thing: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded are three versions of the same router (beta is explicitly identical today), and deep_research overlaps them all. The Polymarket tools (arbitrage, edges, edge_tracker, fill_risk, kalshi_spread) and the entity tools (entity_profile, recent_changes, resolve_entity, compare_entities) also blur, so an agent has to read long descriptions to pick.
Names are all snake_case, but the pattern is inconsistent: verb-first (ask_pipeworx, list_feeds, fetch_feed, resolve_entity, validate_claim, subscribe) mixes with noun-first / noun_verb (ai_visibility_check, entity_profile, polymarket_edges, pipeworx_feedback). Readable, but no single predictable convention.
34 tools is heavy for what the surface appears to be, and the set is a grab-bag spanning SEC/EDGAR research, Polymarket betting, npm dependency checks, llms.txt generation, memory, subscriptions, and a couple of climate feeds. Many tools don't earn their place under a 'Climate Feeds' identity.
Some lifecycles are fully covered (memory: remember/recall/forget; subscriptions: subscribe/unsubscribe/list_subscriptions/recent_alerts), and the research/entity surface is broad. But the stated 'Climate Feeds' domain is thin (only list_feeds/read_feed/fetch_feed) and the betting/research side feels tacked on, leaving the overall purpose unclear and coverage hard to bound.
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."
Related MCP Connectors
Related MCP Servers
- AlicenseAqualityBmaintenanceOne-call Australian energy-market plumbing via AEMO — cited, structured responses for market data and analysis, not a data broker.5140 PyPIMIT
- FlicenseNot gradedqualityDmaintenanceMCP server for EmonCMS energy monitoring API, enabling AI assistants to query energy feeds, inputs, and historical data.1-
- AlicenseNot gradedqualityCmaintenanceCO2 & 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
- AlicenseBqualityAmaintenanceProvides real-time European and GB electricity grid data via MCP, including generation, prices, carbon intensity, and grid infrastructure.4421 npm6MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.