EPA Envirofacts MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level (DEBUG, INFO, WARNING, ERROR) | INFO |
| RETRY_ATTEMPTS | No | Number of retry attempts for failed requests | 3 |
| REQUEST_TIMEOUT | No | Request timeout in seconds | 300 |
| EPA_API_BASE_URL | No | Base URL for EPA Envirofacts API | https://data.epa.gov/efservice/ |
| GEOCODING_API_KEY | No | API key for geocoding service | |
| GEOCODING_SERVICE | No | Geocoding service to use | nominatim |
| GEOCODING_USER_AGENT | No | User agent string for geocoding requests | |
| MAX_RESULTS_PER_QUERY | No | Maximum results per API query | 1000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkB | System health and API connectivity check. Returns: Health status information including EPA API connectivity |
| environmental_summary_by_locationA | Get comprehensive environmental data for a location. Provides environmental summary including nearby regulated facilities, chemical releases, water quality violations, and hazardous waste sites within a specified radius. Args: location: Address, city, or ZIP code radius_miles: Search radius in miles (default: 5.0) Returns: Comprehensive environmental summary |
| search_facilities_toolA | Search for EPA-regulated facilities using various filters. Search for facilities in the EPA's Facility Registry Service using facility name, NAICS code, state, ZIP code, or city. At least one search parameter must be provided. Args: facility_name: Partial or full facility name (uses contains matching) naics_code: NAICS industry code state: Two-letter state code (e.g., 'NY', 'CA') zip_code: 5-digit ZIP code city: City name limit: Maximum results to return (default: 100) Returns: List of facilities with registry ID, name, address, coordinates, active programs, industry codes, and status information |
| get_facility_compliance_history_toolA | Get compliance and enforcement history for an EPA-regulated facility. Retrieves compliance status, violations, and enforcement history for EPA-regulated facilities across RCRA and TRI programs. Supports both FRS registry IDs and program-specific IDs with intelligent fallback logic. Args: registry_id: FRS Registry ID or program-specific ID (RCRA Handler ID, TRI Facility ID) program: Optional program filter ('TRI' or 'RCRA') years: Historical years to include (default: 5) Returns: Complete compliance history with facility information, compliance records, violations, and summary statistics |
| get_chemical_release_dataA | Query TRI chemical releases with flexible search parameters. Provides comprehensive chemical release data from the Toxics Release Inventory (TRI), allowing searches by chemical name, CAS number, state, county, and year. Args: chemical_name: Chemical name (partial match) cas_number: CAS Registry Number (exact match) state: Two-letter state code county: County name (filtered client-side) year: Reporting year (None for most recent available) limit: Maximum results to return (default: 100) Returns: Comprehensive chemical release data with aggregations |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
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.
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.
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.
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.