GroundTruth - Environmental Records
v1.0.1Federal environmental records near any US location, with dates and provenance; never a safety score.
Endpoint health
online- Last checked
- 11/20/2026, 4:18:02 AM
- Latency
- 184 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:ai.agentlookups%2Fgroundtruth
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"ai.agentlookups/groundtruth": {
"url": "https://env.agentlookups.ai/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
4 shown · authentication unknown
List FCC broadband availability for a location
broadband_availability
Fixed broadband availability for a US location from the FCC Broadband Data Collection (BDC), counted per 2020 Census block: each provider and technology the FCC data lists in the block, with advertised maximum download and upload tiers in Mbps and how many of the block's locations each covers (residential and business-only counts). FCC data as of 2026-06-30 (release J26_10nov2026). Wired and fixed wireless service comes first; satellite service is listed last, in its own section. Where a point is in no Census block with FCC data, counts are for the surrounding H3 cell. A block where the FCC records no locations (often a park, a plaza or a street) lists no providers; the building's own address finds the block it sits in. Speeds are advertised maximums reported by providers, not measured speeds. The FCC data has no street addresses, so it cannot confirm service at one house. Input is either a street address (geocoded by the US Census geocoder) or lat/lon coordinates.
Schema valid · SHA-256 527171851fcf…
View input schema
{ "type": "object", "properties": { "address": { "description": "US street address incl. city/state (alternative to lat/lon)", "type": "string" }, "lat": { "description": "Latitude (US)", "maximum": 90, "minimum": -90, "type": "number" }, "lon": { "description": "Longitude (US; negative except Guam, NMI and the western Aleutians)", "maximum": 180, "minimum": -180, "type": "number" } } }Look up public water systems for an area
drinking_water
Public water systems for a US location, from EPA's quarterly drinking-water data (SDWA; GroundTruth checks for a new quarter monthly), with health-based violation summaries, counts of missed or late required tests (monitoring and reporting violations), and each system's latest lead 90th percentile. Input is a street address or lat/lon coordinates (the US Census geocoder gives the county and place, and the point is checked against EPA's Community Water System Service Area Boundaries; a point outside every boundary returns no systems and a message that the home may use a private well or the map may miss its system), or a two-letter state with an optional county and/or city. Each system carries match_basis: service_area_boundary, zip, city, county or state. Some of EPA's boundaries come from states and water systems and the rest are modeled by EPA, so matching is approximate; the user's water bill names their actual utility. Systems are listed by population served, and the order does not say which system serves a given home.
Connections
streamable-http
https://env.agentlookups.ai/mcp