Skip to main content
Glama
zachegner

EPA Envirofacts MCP Server

by zachegner
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to EPA Envirofacts MCP Server

No user-submitted related servers found.

    Related Servers

    • Jana MCP Server

      Jana-Earth-Data
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides natural language access to environmental data including air quality measurements, greenhouse gas emissions, and facility records. It enables users to perform geographic searches, trend analysis, and proximity-based queries using data from sources like OpenAQ and Climate TRACE.
      MIT

    • energy-emissions-mcp

      akkapur
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to retrieve and rank US facility greenhouse gas emissions from EPA's GHGRP via Envirofacts by state, county, and year, returning totals and citable source details.
      1
      Apache 2.0

    • EPA MCP Server

      cyanheads
      A
      license
      Not graded
      quality
      A
      maintenance
      Access EPA environmental data — facility compliance (ECHO), toxic releases (TRI), Superfund sites, drinking water systems, environmental justice screening (EJScreen), and real-time air quality (AirNow) via MCP.
      471 npm
      2
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap. The environmental_summary_by_location provides a comprehensive overview, get_chemical_release_data focuses on TRI chemical releases, get_facility_compliance_history_tool handles compliance history, search_facilities_tool searches for facilities, and health_check is a system utility. The descriptions clearly differentiate their scopes and use cases.

    Naming Consistency3/5

    The naming is mixed with some inconsistencies. environmental_summary_by_location and get_chemical_release_data follow a verb_noun pattern, but get_facility_compliance_history_tool and search_facilities_tool append '_tool' unnecessarily, and health_check is a simple compound. While readable, the deviation from a single convention reduces predictability.

    Tool Count5/5

    With 5 tools, this is well-scoped for an EPA data server. Each tool serves a distinct and essential function: summary, chemical data, compliance, facility search, and health check. The count is appropriate, avoiding both thin coverage and bloat, and aligns with the server's purpose of providing environmental data access.

    Completeness4/5

    The tool set covers core EPA data domains well, including summaries, chemical releases, facility compliance, and facility search, with no dead ends. A minor gap exists in lacking update or delete operations, but this is reasonable for a read-only data server. Agents can effectively query and analyze environmental data without significant workarounds.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources