accueil / serveurs / IA & Mémoire / com.davisvillelabs/facilityproof
com.davisvillelabs/facilityproof
serveur MCP (Model Context Protocol) · FacilityProof 1.0.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que com.davisvillelabs/facilityproof est sûr ?
Au dernier audit MCP Hub, le serveur MCP « com.davisvillelabs/facilityproof » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 2 outils
- facilityproof.check_facility_compliance_evidence≈ 1594 tokens
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.
Paramètres, retour & exemple (7)
Paramètreszip· string · optionnel
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.city· string · optionnel
City for the physical facility. Used with name/address hints to distinguish facilities with similar names.name· string · optionnel
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.frsId· string · optionnel
Exact 12-digit EPA Facility Registry Service identifier when known. Prefer this over name matching because it anchors federal facility identity directly.state· string · optionnel
Two-letter U.S. postal abbreviation for the physical facility. For full compliance evidence, California, Texas, and Florida are currently released. Permit identity uses a separate readiness gate.address· string · optionnel
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.programId· string · optionnel
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.
Exemple d'appel{"name": "facilityproof.check_facility_compliance_evidence", "arguments": {"zip": "texte", "city": "texte", "name": "texte", "frsId": "texte", "state": "texte", "address": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"asOf": "texte", "quality": {}, "evidence": [], "facility": {}, "programs": [], "reportId": "texte", "conflicts": [], "freshness": [], "operation": "texte", "penalties": [], "sourceGaps": [], "violations": []}} - facilityproof.check_permit_identity≈ 1036 tokens
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.
Paramètres, retour & exemple (7)
Paramètreszip· string · optionnel
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.city· string · optionnel
City for the physical facility. Used with name/address hints to distinguish facilities with similar names.name· string · optionnel
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.frsId· string · optionnel
Exact 12-digit EPA Facility Registry Service identifier when known. Prefer this over name matching because it anchors federal facility identity directly.state· string · optionnel
Two-letter U.S. postal abbreviation for the physical facility. For full compliance evidence, California, Texas, and Florida are currently released. Permit identity uses a separate readiness gate.address· string · optionnel
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.programId· string · optionnel
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.
Exemple d'appel{"name": "facilityproof.check_permit_identity", "arguments": {"zip": "texte", "city": "texte", "name": "texte", "frsId": "texte", "state": "texte", "address": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"facility": {}, "identity": {}, "programs": [], "conflicts": [], "freshness": [], "operation": "texte", "generatedAt": "texte", "limitations": [], "jurisdiction": {}, "schemaVersion": "texte", "sourceProvenance": {}, "unresolvedIdentifiers": []}}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».