EPA Emissions MCP — wraps EPA Envirofacts REST API (free, no auth)
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.
Scored across 36 tools
The descriptions are extraordinarily detailed and do differentiate tools, but the server bundles several near-duplicate families: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research / discover_tools all route questions, and polymarket_edges / polymarket_arbitrage / polymarket_edge_tracker / polymarket_fill_risk / polymarket_kalshi_spread overlap heavily. The beta tool explicitly admits it currently matches ask_pipeworx exactly, which is a real misselection hazard.
All names are snake_case, which is consistent. However, the verb/noun convention is mixed — verb_noun (validate_claim, resolve_entity), noun_verb (entity_profile, tri_facility_releases), bare verbs (remember, forget, recall, subscribe), and prefixed namespaces (polymarket_*, pipeworx_*, tri_*, ghg_*). Readable, but not a single predictable pattern.
36 tools is heavy for any single purpose, and the count is inflated by redundant meta-routing tools and a five-tool Polymarket cluster plus three near-identical ask_pipeworx variants. The breadth suggests a general gateway rather than a focused emissions server, and several tools do not earn a distinct slot.
For the emissions domain, the surface covers sector/facility GHG and TRI releases plus trends, but omits other obvious EPA-adjacent data (air quality/AQI, water quality, Superfund, enforcement) and has no write operations. As a general data gateway it is broad, but the reported server name makes the coverage feel mismatched and partial.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
bet_research2 fields changedInput 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"
+ }
+]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."bet_research2 fields changedInput 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"
+ }
+]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."polymarket_kalshi_spread2 fields changedInput schema / examplesPrevious value: -[
- {
- "topic": "fed"
- },
- {
- "topic": "btc"
- }
-]New value: +[
+ {
+ "topic": "fed"
+ },
+ {
+ "topic": "btc"
+ },
+ {
+ "topic": "bitcoin"
+ },
+ {
+ "topic": "fed rate decision"
+ }
+]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."EPA ECHO MCP — wraps EPA ECHO Web Services (free, no auth)
Air Quality MCP — wraps air-quality-api.open-meteo.com (free, no auth)
NREL MCP — wraps the US National Renewable Energy Laboratory developer API
EPA AirNow MCP — official US real-time AQI + forecast (free key)
Add one secure layer between your agents and this server.