Facility Compliance — EPA ECHO: Facility Profiles, Violations & Enforcement
link.morningbrief/facility-compliancemorningbrief.linkstreamable-httpv1.0.0Scanned
EPA facility compliance: 3.2M regulated facilities, unified compliance profiles. No key.
6 tools: 6 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
Anlyon alternative
Run the operations that matter as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Only reads 6Show 6 read-only tools
get_county_compliance_summarySummarize EPA-regulated facilities in one US county: how many facilities (and how many active), how many have been inspected, formal enforcement actions and total penalties, how ma…No findings
Why it is in this group
- The name "get_county_compliance_summary" says "get": a word for reading.
Description, as the server wrote it Summarize EPA-regulated facilities in one US county: how many facilities (and how many active), how many have been inspected, formal enforcement actions and total penalties, how many facilities are currently in violation or significant violation, plus the worst facilities in the county (significant violations first). County is the facility's physical county from EPA/FRS coordinates, with official Census county names. A county summary is a screening view of an area, not a verdict on a specific property.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_facilityLook up one US regulated facility by its EPA Facility Registry Service (FRS) Registry ID.No findings
Why it is in this group
- The name "get_facility" says "get": a word for reading.
Description, as the server wrote it Look up one US regulated facility by its EPA Facility Registry Service (FRS) Registry ID. Returns ONE unified profile across all EPA programs the facility belongs to — Clean Air Act (CAA), Clean Water Act/NPDES (CWA), Safe Drinking Water Act (SDWA), hazardous waste (RCRA), Toxics Release Inventory (TRI), and Greenhouse Gas (GHG) — with address and county, current compliance status, inspection and enforcement history, penalties, and per-program detail. Data is EPA ECHO. This is screening data, not a Phase I Environmental Site Assessment.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_state_compliance_summarySummarize EPA-regulated facilities for a whole US state: facility and county counts, inspections, formal enforcement actions, total penalties, facilities currently in violation or …No findings
Why it is in this group
- The name "get_state_compliance_summary" says "get": a word for reading.
Description, as the server wrote it Summarize EPA-regulated facilities for a whole US state: facility and county counts, inspections, formal enforcement actions, total penalties, facilities currently in violation or significant violation, and the counties with the most facilities in violation. Data is EPA ECHO.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_facilities_with_violationsList facilities whose current EPA compliance status is a violation (Violation Identified, Significant Violation, or Violation), worst first: significant violations first, then most…No findings
Why it is in this group
- The name "list_facilities_with_violations" says "list": a word for reading.
Description, as the server wrote it List facilities whose current EPA compliance status is a violation (Violation Identified, Significant Violation, or Violation), worst first: significant violations first, then most quarters in noncompliance, then largest penalties. Filter by state, by county (requires state), or by program (CAA, CWA, SDWA, RCRA, TRI, GHG). Useful for screening an area or a program for current environmental compliance problems.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_programsList the EPA programs unified in this dataset (Clean Air Act, Clean Water Act/NPDES, Safe Drinking Water Act, RCRA hazardous waste, Toxics Release Inventory, Greenhouse Gas Reporti…No findings
Why it is in this group
- The name "list_programs" says "list": a word for reading.
Description, as the server wrote it List the EPA programs unified in this dataset (Clean Air Act, Clean Water Act/NPDES, Safe Drinking Water Act, RCRA hazardous waste, Toxics Release Inventory, Greenhouse Gas Reporting) with what each covers, how many facilities belong to each, and how many of those facilities are currently in violation.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
search_facilitiesSearch EPA-regulated facilities by name fragment, and optionally narrow by city, state (two-letter code), ZIP code prefix, county name (requires state; official county name, case-i…No findings
Why it is in this group
- The name "search_facilities" says "search": a word for reading.
Description, as the server wrote it Search EPA-regulated facilities by name fragment, and optionally narrow by city, state (two-letter code), ZIP code prefix, county name (requires state; official county name, case-insensitive), program (CAA, CWA, SDWA, RCRA, TRI, GHG), current compliance status, or active facilities only. Results are ordered by enforcement significance (formal actions, then penalties), and each result shows the facility's programs, compliance status, inspection count, formal action count, and total penalties.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 2, 2026, 00:20 UTC, unchanged since Nov 2, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2024-11-05
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http facility-compliance https://facilities.morningbrief.link/mcpclaude mcp add --transport http facility-compliance https://facilities.morningbrief.link/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__facility-compliance__get_facility",
"mcp__facility-compliance__search_facilities",
"mcp__facility-compliance__get_county_compliance_summary",
"mcp__facility-compliance__get_state_compliance_summary",
"mcp__facility-compliance__list_facilities_with_violations",
"mcp__facility-compliance__list_programs"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as facility-compliance. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://anlyon.dev/api/v1/servers/link.morningbrief/facility-compliance/verify?hash=3f06d6cfdcd2b3951d61d76ed30056a9acb5e7cd1d72c6586391dde5c7732002" | jq -e '.changed == false'Pinned hash 3f06d6cfdcd2, from Nov 2, 2026, 00:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/link.morningbrief/facility-compliance/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/link.morningbrief/facility-compliance)Source: MCP Registry. Synced Nov 2, 2026, 00:17 UTC.