Skip to content

FacilityProof MCP server

com.davisvillelabs/facilityproofdavisvillelabs.comstreamable-httpv1.0.0Scanned

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

2 tools: 2 change things.

Tools: 0 delete, 0 irreversible, 2 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • 3 findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

2 of these tools change something. Run those 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 Radar 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 →

What the FacilityProof MCP server can do

The FacilityProof MCP server is published by davisvillelabs.com, a domain the MCP Registry verified. It has 2 tools. It can create or change data (2 tools: facilityproof.check_facility_compliance_evidence and facilityproof.check_permit_identity), but cannot delete data. None of its tools only reads.

2 tools bring in text other people can write (facilityproof.check_facility_compliance_evidence and facilityproof.check_permit_identity).

The fixed checks matched 3 findings (credentials-mention and annotation-conflict). Each one comes with the text it matched.

Last scanned Oct 21, 2026, version 1.0.0.

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.

2 tools

Changes things 2Claude Code: ask
  • facilityproof.check_facility_compliance_evidenceResolve one physical U.S.Reads text others write2 findings

    Why it is in this group

    • The description's first verb is "resolve": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...identical request with the same payment credential to recover without a second settlement."

      What this check looks for
    • Warn

      The server marks "facilityproof.check_facility_compliance_evidence" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "resolve": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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. California, Texas, and Florida are currently released for paid full-compliance evidence. 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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • facilityproof.check_permit_identityResolve one physical U.S.Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "resolve": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "facilityproof.check_permit_identity" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "resolve": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true

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 outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
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.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:22 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
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

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

2 warn1 info

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 2 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__facilityproof__facilityproof_check_facility_compliance_evidence",
      "mcp__facilityproof__facilityproof_check_permit_identity"
    ],
    "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 facilityproof. Review it before you use it.

Capability tags behind 2 rules
  • mcp__facilityproof__facilityproof_check_facility_compliance_evidence untrusted-input
  • mcp__facilityproof__facilityproof_check_permit_identity untrusted-input

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://radar.anlyon.com/api/v1/servers/com.davisvillelabs/facilityproof/verify?hash=a2c2718a074b89672a0601ecfa2c2d9da209ae8ca2e5bc09a063131fe0e70e7f" | jq -e '.changed == false'

Pinned hash a2c2718a074b, from Oct 21, 2026, 19:10 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.davisvillelabs/facilityproof/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.davisvillelabs/facilityproof
[![Anlyon Radar](https://radar.anlyon.com/badge/com.davisvillelabs/facilityproof.svg)](https://radar.anlyon.com/servers/com.davisvillelabs/facilityproof)

Source: MCP Registry. Synced Oct 21, 2026, 17:53 UTC.

FacilityProof MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the FacilityProof MCP server safe?

No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the FacilityProof MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the FacilityProof MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the FacilityProof MCP server have?

2 tools: 2 write. facilityproof.check_facility_compliance_evidence and facilityproof.check_permit_identity.

Does the FacilityProof MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the FacilityProof MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the FacilityProof MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 21, 2026.