_ registry / mcp streamable-http · checked 6m ago

groundtruth

https://env.agentlookups.ai

Registry code: cbc989fd99165a3c

api record

Environmental records near a US location from GroundTruth's monthly snapshot of EPA data: National Priorities List (Superfund) sites, facilities from the newest Toxics Release Inventory reporting year, facilities with a current significant-noncompliance flag, and public water systems with health-based violation summaries. location_scores returns 0-1 layer scores for a location, and broadband_availability lists the FCC's fixed broadband filings for its Census block. Records carry distances, provenance gives each dataset's source and snapshot date, and each result includes honesty notes that…

endpoint
https://env.agentlookups.ai/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is groundtruth live?
Yes — it answered the hub's last check (checked 6m ago). It answered 100% of checks over the last 30 days.
Is groundtruth free to use?
Not measured yet.
What tools does groundtruth have?
4 tools: location_scores, environment_near, drinking_water, broadband_availability.
Is groundtruth safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.6%

90 days 99.3%· all time 99.3%

latency
339ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 542 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • find superfund and toxic sites near a us location
  • check drinking water violations
  • get location environment scores
  • check broadband availability
takes → gives
text → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
4 never probed 0 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • location_scores reads unknown 12h ago

    Layer scores for a US location: school quality, natural hazards, groundwater contamination, Superfund proximity, air quality, highway noise, walkability, crime, and climate pleasantness (pleasant days/year). Scores are 0-1 with 1.0 = favorable; null = cannot score that layer here. The scores are model estimates drawn from public datasets, not safety ratings. no_coverage marks a layer that is null because this location lies outside that layer's data, and caveats.<layer> says why. When a layer's number has limits the score alone does not show (a proxy, partial source data), caveats.<layer> states them. Superfund proximity weighs each cleanup site by the nearer of the area EPA maps for it and the one point EPA lists for it; where EPA maps no area, a site that stretches out (a canal, a plume) can be closer than the score reflects. The scores are not a safety assessment, and an absence of adverse signals is not a clean bill of health. Coverage: Superfund/toxic-release proximity national; air quality, groundwater, and natural hazards a San Francisco Bay Area grid (lat 37.0 to 38.6, lon -122.8 to -121.4, which also takes in Sacramento), null elsewhere; highway noise Bay Area; walkability California; schools all 50 states and DC (2023-2025 results); climate CONUS (gridMET 4km, 2015-2024); Alaska, the Florida Keys, Hawaii, Puerto Rico and the US Virgin Islands (Daymet V4, 2011-2020); within 40 km of 3 NOAA weather stations in American Samoa, the Northern Mariana Islands and Guam (2016-2025); null elsewhere; crime police incident feeds inside the city limits of San Francisco; Oakland; Chicago; New York City; Los Angeles; Dallas; Washington, DC; and Kansas City, Missouri only. School scores draw on the Stanford Education Data Archive (SEDA), whose terms require naming it as the source: Reardon, S. F., Ho, A. D., Shear, B. R., Fahle, E. M., Kalogrides, D., Saliba, J. (2024). Stanford Education Data Archive (Version 5.0). [https://purl.stanford.edu/cs829jn7849] [https://doi.org/10.25740/cs829jn7849] (also in citations.school_quality). Input is either a street address (geocoded by the US Census geocoder) or lat/lon coordinates.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "lat": {
          "type": "number",
          "maximum": 90,
          "minimum": -90,
          "description": "Latitude (US)"
        },
        "lon": {
          "type": "number",
          "maximum": 180,
          "minimum": -180,
          "description": "Longitude (US; negative except Guam, NMI and the western Aleutians)"
        },
        "address": {
          "type": "string",
          "description": "US street address incl. city/state (alternative to lat/lon)"
        }
      }
    }
    arguments 21 lines
  • environment_near reads unknown 22h ago

    Environmental records within a radius of a US location, from GroundTruth's monthly snapshot of three EPA datasets: National Priorities List (Superfund) sites, facilities from the newest Toxics Release Inventory (TRI) reporting year, and active facilities with a current significant-noncompliance or high-priority-violation flag in EPA ECHO. Each record carries its distance, and provenance gives each dataset's source and snapshot date (as_of). A Superfund distance runs to the nearer of the area EPA maps for the site (distance_to: epa_site_boundary, 0 with inside_site_boundary true inside it) and the one point EPA lists for the site (distance_to: epa_listed_point); each record gives both. Where EPA maps no area, a site that stretches out (a canal, a river, an underground plume) can reach closer than its point. Input is either a street address (geocoded by the US Census geocoder) or lat/lon coordinates. Results are records, not a safety assessment. An empty list means the snapshot holds no such record within the radius. EPA holds other records this tool does not search (Superfund sites not on the NPL, earlier TRI years, facilities without a current noncompliance flag), and an empty result does not mean the area is free of contamination.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "lat": {
          "type": "number",
          "maximum": 90,
          "minimum": -90,
          "description": "Latitude (US)"
        },
        "lon": {
          "type": "number",
          "maximum": 180,
          "minimum": -180,
          "description": "Longitude (US; negative except Guam, NMI and the western Aleutians)"
        },
        "address": {
          "type": "string",
          "description": "US street address incl. city/state (alternative to lat/lon)"
        },
        "radius_km": {
          "type": "number",
          "maximum": 50,
          "description": "Search radius in km (default 10, max 50)"
        }
      }
    }
    arguments 26 lines
  • drinking_water reads unknown 22h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "lat": {
          "type": "number",
          "maximum": 90,
          "minimum": -90,
          "description": "Latitude (US)"
        },
        "lon": {
          "type": "number",
          "maximum": 180,
          "minimum": -180,
          "description": "Longitude (US; negative except Guam, NMI and the western Aleutians)"
        },
        "city": {
          "type": "string",
          "description": "City served (optional)"
        },
        "state": {
          "type": "string",
          "description": "Two-letter state code, e.g. MD (with county and/or city; not sent with address or lat/lon)"
        },
        "county": {
          "type": "string",
          "description": "County name (optional), e.g. Kings, Prince George's County, Richmond city"
        },
        "address": {
          "type": "string",
          "description": "US street address incl. city/state (alternative to state or lat/lon)"
        }
      }
    }
    arguments 33 lines
  • broadband_availability reads unknown 22h ago

    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_24oct2026). 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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "lat": {
          "type": "number",
          "maximum": 90,
          "minimum": -90,
          "description": "Latitude (US)"
        },
        "lon": {
          "type": "number",
          "maximum": 180,
          "minimum": -180,
          "description": "Longitude (US; negative except Guam, NMI and the western Aleutians)"
        },
        "address": {
          "type": "string",
          "description": "US street address incl. city/state (alternative to lat/lon)"
        }
      }
    }
    arguments 21 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id cbc989fd99165a3c.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/cbc989fd99165a3c/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/cbc989fd99165a3c/badge.svg)](https://brick.blue/agent/cbc989fd99165a3c?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on agentlookups.ai 5 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.