# FacilityProof (remote · facilityproof.davisvillelabs.com)

Source-reconciled U.S. environmental facility compliance evidence for AI agents.

- Trust score: 69/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `facilityproof.davisvillelabs.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-davisvillelabs-facilityproof/facilityproof.md), [page](https://verifymcp.io/servers/com-davisvillelabs-facilityproof/facilityproof)

## Channel facts

- Endpoint: `https://facilityproof.davisvillelabs.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 873 tokens (~436/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the FacilityProof MCP server?

FacilityProof is a hosted endpoint at https://facilityproof.davisvillelabs.com/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.

### Claude

```bash
claude mcp add --transport http com-davisvillelabs-facilityproof 'https://facilityproof.davisvillelabs.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-davisvillelabs-facilityproof": {
      "url": "https://facilityproof.davisvillelabs.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-davisvillelabs-facilityproof": {
      "type": "http",
      "url": "https://facilityproof.davisvillelabs.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-davisvillelabs-facilityproof]
url = "https://facilityproof.davisvillelabs.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-davisvillelabs-facilityproof": {
      "type": "remote",
      "url": "https://facilityproof.davisvillelabs.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-davisvillelabs-facilityproof --url 'https://facilityproof.davisvillelabs.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-davisvillelabs-facilityproof:
    url: "https://facilityproof.davisvillelabs.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-davisvillelabs-facilityproof": {
      "Transport": "http",
      "Url": "https://facilityproof.davisvillelabs.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-davisvillelabs-facilityproof -t streamable-http -u 'https://facilityproof.davisvillelabs.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-davisvillelabs-facilityproof": {
      "type": "http",
      "url": "https://facilityproof.davisvillelabs.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 69, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 67, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “facilityproof.check_facility_compliance_evidence” rewrote its description, which is the text the model reads
- [functional improvement] Schema quality: 510 → 436
- [functional] New tool “facilityproof.check_permit_identity”
- [cosmetic] “facilityproof.check_facility_compliance_evidence” reworded the description of “programId”
- [cosmetic] “facilityproof.check_facility_compliance_evidence” reworded the description of “state”

### 2026-09-25 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 64, +2)

- [security] Tool “facilityproof.check_facility_compliance_evidence” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 238 → 510
- [functional improvement] Tool coverage: 43% → 100%
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: fair → excellent
- [cosmetic] “facilityproof.check_facility_compliance_evidence” reworded the description of “address”
- [cosmetic] “facilityproof.check_facility_compliance_evidence” reworded the description of “city”
- [cosmetic] “facilityproof.check_facility_compliance_evidence” reworded the description of “frsId”
- [cosmetic] “facilityproof.check_facility_compliance_evidence” reworded the description of “name”
- [cosmetic] “facilityproof.check_facility_compliance_evidence” reworded the description of “programId”
- [cosmetic] “facilityproof.check_facility_compliance_evidence” reworded the description of “state”
- [cosmetic] “facilityproof.check_facility_compliance_evidence” reworded the description of “zip”

### 2026-09-21 (score 62)

First indexed and scored.

## MCP tools (2)

### `facilityproof.check_facility_compliance_evidence` (~454 tokens)

Check facility compliance evidence

Resolve one physical U.S. facility and return a bounded, source-reconciled environmental regulatory evidence report covering core air, water, hazardous-waste, and drinking-water programs plus inspections, reported violations, formal enforcement, penalties, freshness, source gaps, and conflicts. Use when an agent needs evidence about one specific facility and wrong-site matching or missing-source inference would be costly; do not use for company-wide research, raw EPA record retrieval, legal advice, or a clean/compliant verdict. Provide frsId or programId when known; otherwise provide name with enough location context to resolve exactly one site. This is a $1.00 USD MPP operation when commerce is active in a released state: identity and state eligibility are resolved before payment, ambiguous/unresolved/unreleased requests are not charged, and the call does not alter regulatory records. A fresh authorized invocation can charge again, while a settled delivery retry should reuse the identical request with the same payment credential to recover without a second settlement.

Input parameters:

- `address` (string): Street address for the physical facility when known. Used only for physical-site identity resolution; do not provide corporate headquarters unless that is the facility being checked.
- `city` (string): City for the physical facility. Used with name/address hints to distinguish facilities with similar names.
- `frsId` (string): Exact 12-digit EPA Facility Registry Service identifier when known. Prefer this over name matching because it anchors federal facility identity directly.
- `name` (string): Facility or site name, including a distinguishing plant/site descriptor when available. For name-based resolution, also provide city/state, address, or ZIP whenever possible.
- `programId` (string): Exact authoritative environmental program identifier when known, such as an NPDES permit ID or RCRA handler ID. FacilityProof uses it to resolve the physical facility before paid work.
- `state` (string): Two-letter U.S. postal abbreviation for the physical facility. Full compliance evidence and permit identity have separate production-readiness rules.
- `zip` (string): U.S. ZIP or ZIP+4 for the physical facility. Use as an identity hint, not as a substitute for a site name or authoritative identifier.

Output parameters:

- `asOf` (string): Evidence cutoff or as-of time represented by the report.
- `conflicts` (array): Unresolved disagreements across authoritative records that FacilityProof preserves rather than guessing through.
- `enforcementActions` (array): Formal enforcement-action evidence returned by authoritative sources.
- `evidence` (array): Source-linked evidence observations supporting the report.
- `facility` (object): Resolved physical-facility identity, including authoritative identifiers and normalized location context.
- `freshness` (array): Per-source freshness and observation metadata so agents can judge staleness.
- `generatedAt` (string): Timestamp when FacilityProof generated the report.
- `inspections` (array): Inspection evidence returned by authoritative sources in the bounded search.
- `limitations` (array): Important scope and interpretation limits, including that the report is evidence rather than legal advice or a compliance verdict.
- `operation`: Canonical FacilityProof operation that produced this report.
- `penalties` (array): Penalty/monetary enforcement evidence linked to the resolved facility when supported.
- `programs` (array): Bounded environmental program/permit coverage found for the resolved facility.
- `quality` (object): Quality and coverage signals for the report.
- `reportId` (string): Stable report identifier for this generated evidence package.
- `schemaVersion`: FacilityProof report schema version.
- `sourceGaps` (array): Expected or relevant source coverage that could not be established or retrieved.
- `violations` (array): Reported violation/noncompliance evidence returned by authoritative sources; absence is not a clean-compliance conclusion.

### `facilityproof.check_permit_identity` (~355 tokens)

Check facility permit identity

Resolve one physical U.S. facility and return authoritative FRS environmental program/permit identifiers plus qualified jurisdiction and source-system provenance before deeper compliance research. This is a $0.10 USD MPP operation when commerce is active. It is currently jurisdiction-ready in 40 states. Ambiguous identity, medium-confidence identity, linked-record conflicts, missing routed program identity, and states with unresolved Tribal/federal carve-outs are rejected before payment. The result does not determine compliance, permit status, violations, enforcement, or penalties.

Input parameters:

- `address` (string): Street address for the physical facility when known. Used only for physical-site identity resolution; do not provide corporate headquarters unless that is the facility being checked.
- `city` (string): City for the physical facility. Used with name/address hints to distinguish facilities with similar names.
- `frsId` (string): Exact 12-digit EPA Facility Registry Service identifier when known. Prefer this over name matching because it anchors federal facility identity directly.
- `name` (string): Facility or site name, including a distinguishing plant/site descriptor when available. For name-based resolution, also provide city/state, address, or ZIP whenever possible.
- `programId` (string): Exact authoritative environmental program identifier when known, such as an NPDES permit ID or RCRA handler ID. FacilityProof uses it to resolve the physical facility before paid work.
- `state` (string): Two-letter U.S. postal abbreviation for the physical facility. Full compliance evidence and permit identity have separate production-readiness rules.
- `zip` (string): U.S. ZIP or ZIP+4 for the physical facility. Use as an identity hint, not as a substitute for a site name or authoritative identifier.

Output parameters:

- `conflicts` (array)
- `facility` (object)
- `freshness` (array): FRS retrieval time plus source-system cadence/provenance. Source-route entries do not pretend a facility-specific source record was captured.
- `generatedAt` (string)
- `identity` (object)
- `jurisdiction` (object)
- `limitations` (array)
- `operation`
- `programs` (array)
- `schemaVersion`
- `sourceProvenance` (object)
- `unresolvedIdentifiers` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-davisvillelabs-facilityproof/facilityproof#diagnostics

## Score history

- 2026-09-28: 69
- 2026-09-27: 67
- 2026-09-26: 66
- 2026-09-25: 66
- 2026-09-24: 65
- 2026-09-23: 65
- 2026-09-22: 64
- 2026-09-21: 62

## Common questions

### What is the FacilityProof MCP server?

FacilityProof is an MCP server listed in the public MCP registry as com.davisvillelabs/facilityproof. Source-reconciled U.S. environmental facility compliance evidence for AI agents. This page covers its hosted endpoint (https://facilityproof.davisvillelabs.com/mcp).

### Is the FacilityProof MCP server safe to use?

FacilityProof scores 69 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 FacilityProof MCP server expose?

FacilityProof exposes 2 tools: facilityproof.check_facility_compliance_evidence, facilityproof.check_permit_identity. Their descriptions and schemas cost roughly 809 tokens of context every time the server is loaded.

### Does the FacilityProof MCP server require authentication?

No. We connected to FacilityProof without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the FacilityProof MCP server still maintained?

FacilityProof is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://facilityproof.davisvillelabs.com/mcp
- Website: https://facilityproof.davisvillelabs.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-davisvillelabs-facilityproof/facilityproof.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-davisvillelabs-facilityproof/facilityproof.json
- HTML version of this page: https://verifymcp.io/servers/com-davisvillelabs-facilityproof/facilityproof