GroundTruth - Environmental Records
REMOTE · ENV.AGENTLOOKUPS.AI · SCANNED SEP 21
Federal environmental records near any US location, with dates and provenance; never a safety score.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 496 tokens (~165/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the GroundTruth - Environmental Records MCP server?
GroundTruth - Environmental Records is a hosted endpoint at https://env.agentlookups.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · env.agentlookups.ai
claude mcp add --transport http ai-agentlookups-groundtruth 'https://env.agentlookups.ai/mcp'
{
"mcpServers": {
"ai-agentlookups-groundtruth": {
"url": "https://env.agentlookups.ai/mcp"
}
}
} {
"servers": {
"ai-agentlookups-groundtruth": {
"type": "http",
"url": "https://env.agentlookups.ai/mcp"
}
}
} [mcp_servers.ai-agentlookups-groundtruth] url = "https://env.agentlookups.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-agentlookups-groundtruth": {
"type": "remote",
"url": "https://env.agentlookups.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-agentlookups-groundtruth --url 'https://env.agentlookups.ai/mcp' --transport streamable-http
mcp_servers:
ai-agentlookups-groundtruth:
url: "https://env.agentlookups.ai/mcp" {
"McpServers": {
"ai-agentlookups-groundtruth": {
"Transport": "http",
"Url": "https://env.agentlookups.ai/mcp"
}
}
} assistant mcp add ai-agentlookups-groundtruth -t streamable-http -u 'https://env.agentlookups.ai/mcp'
{
"mcpServers": {
"ai-agentlookups-groundtruth": {
"type": "http",
"url": "https://env.agentlookups.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Sept 26 +1
- Stability: 0.97 → pass security
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Aug 26 +1
- Tool “due_diligence” rewrote its description, which is the text the model reads security
- 27 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +1
- First check of Injection markers: pass security
- First check of Judged manipulation: pass security
- Tool “due_diligence” rewrote its description, which is the text the model reads security
- First check of Destructive annotations: pass functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Aug 26 0
- Schema quality: pass → fail ▼ functional
- New tool “due_diligence” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://env.agentlookups.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=env.agentlookups.ai | CN=YR1,O=Let's Encrypt,C=US | 5 Sept 2026 | 4 Dec 2026 | RSA 2048 | SHA256-RSA | 5305eef6fb18ce88bf11e7495a9ec6d2ff3 |
| SANs: env.agentlookups.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of env.agentlookups.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| agentlookups.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://env.agentlookups.ai/mcp | Verified | 200 | |
| http (plaintext) | http://env.agentlookups.ai/mcp | HTTPS enforced | 301 | https://env.agentlookups.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
drinking_water ~86
Public water systems serving a US state + county and/or city, with health-based SDWA violation summaries. Matching is approximate (service boundaries are not public); the user's water bill names their actual utility.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City served (optional) |
| county | string | – | County name (optional) |
| state | string | yes | Two-letter state code, e.g. MD |
No output schema declared.
No examples provided.
due_diligence ~208
Address due-diligence 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. no_coverage flags placeholder values machine-readably; relay caveats verbatim. Coverage: Superfund/toxic-release proximity national; other environmental layers CA/Bay Area; schools all 50 states and DC (2023-2025 results); climate CONUS (no AK/HI); crime SF/Oakland/Chicago. Pass EITHER a street address (geocoded via the US Census geocoder) OR lat/lon coordinates.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | US street address incl. city/state (alternative to lat/lon) |
| lat | number | – | Latitude (US) |
| lon | number | – | Longitude (US, negative) |
No output schema declared.
No examples provided.
environment_near ~127
Federal environmental records within a radius of a US location: Superfund/NPL sites, TRI toxic-release facilities, and facilities currently flagged for significant noncompliance. Pass EITHER a street address (geocoded via the US Census geocoder) OR lat/lon coordinates.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | US street address incl. city/state (alternative to lat/lon) |
| lat | number | – | Latitude (US) |
| lon | number | – | Longitude (US, negative) |
| radius_km | number | – | Search radius in km (default 10, max 50) |
No output schema declared.
No examples provided.
What is the GroundTruth - Environmental Records MCP server?
GroundTruth - Environmental Records is an MCP server listed in the public MCP registry as ai.agentlookups/groundtruth. Federal environmental records near any US location, with dates and provenance; never a safety score. This page covers its hosted endpoint (https://env.agentlookups.ai/mcp).
Is the GroundTruth - Environmental Records MCP server safe to use?
GroundTruth - Environmental Records scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the GroundTruth - Environmental Records MCP server expose?
GroundTruth - Environmental Records exposes 3 tools: environment_near, drinking_water, due_diligence. Their descriptions and schemas cost roughly 421 tokens of context every time the server is loaded.
Does the GroundTruth - Environmental Records MCP server require authentication?
No. We connected to GroundTruth - Environmental Records without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the GroundTruth - Environmental Records MCP server still maintained?
GroundTruth - Environmental Records is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.