
KS Department of Health and Environment
Kansas Department of Health and Environment spills, AST/UST registry, Identified Sites cleanup list, and Environmental Interest Finder via agency host 4 curated layers covering 32K reported spills, 17K tanks, 3.7K cleanup sites across 13 BER programs, and 40K KEIMS environmental-interest records. No credentials required.
What is KS Department of Health and Environment?
Kansas Department of Health and Environment Bureau of Environmental Remediation (BER) and Division of Environment (DOE) services on agency host Four curated layers: layer 0 Reported Spill Locations (~32,284 events — 5 SPILL_STATUS values: Closed 30,860, Transferred 699, Referred 499, Open 174, "not recorded" 52; 106 Title-Case counties led by Sedgwick 2,321, Wyandotte 1,799, Butler 1,709, Johnson 1,648, McPherson 1,413; SPILL_DATE / INCIDENT_DATE / CLOSED_DATE epoch-ms with `TIMESTAMP` filter support; LEAD_AGENCY=KDHE only); layer 0 Tank Site Locations (~17,506 AST+UST facilities — 5 FAC_STATUS values: ALL Out of Use 8,844, Currently In Use 5,534, No Status Recorded 2,599, Temp/Pending 512, Unknown 17; 6 FAC_DIST KDHE district codes NCDO/NEDO/NWDO/SCDO/SEDO/SWDO; permit/expire/unpermit AST+UST tank counts); layer 0 Identified Sites List (~3,736 cleanup sites across 13 PROGRAMNAME values: Federal Facilities 646, Voluntary Cleanup 604, Brownfields 596, State Cooperative 536, Site Assessment 427, Orphan Sites 253, Dry Cleaner Remediation 228, Environmental Use Controls 191, Superfund 102, Storage Tanks 60, Sector ID 43, BER 38, Risk Management 11; STATUSDESC: Resolved 1,942 / Active 1,439 / Resolved with Restrictions 253 / Transferred out of Bureau 96 / UNKNOWN 6); layer 1 KEIMS Programs Environmental Interest Finder (~39,754 records across 8 ENV_INT_TYPE_DESC values: Storage Tanks AST/UST 17,506, LUST 11,944, Identified Sites 3,716, Stormwater Runoff 2,959, WWTP 2,224, Air Title V 246, Air Synthetic Minor 726, Drycleaner 433). §0 surprises: legacy host agency host is DEAD — TLS cert mismatch (cert subject is agency host). BER/Spills_DASC data services publishes 0 layers (uninitialized) — handler uses Spills_viewer_public/0 instead. Spills MEDIUM_AFFECTED is FREE-TEXT (100+ distinct values with whitespace/parens) — handler exposes substring match only. Tanks_DASC county column is FAC_CNTY (not COUNTY); 105 distinct Title Case (no dups). ISL_DASC has BOTH COUNTYNAME (UPPERCASE) and COUNTYABBR (2-letter) — handler uses COUNTYNAME. KEIF4KEIMS L1 has no county column — only CITY. KEIF L0 Non-KEIMS (53K) is a duplicate visualization tier with no program type — not exposed. ; Last verified live 2026-05-08.
Available Tools
Requirements
- Toggle onToggle on and use — no setup needed.
Quick Setup Guide
Follow these steps to connect your AI agents to this connector
Open /mcp and enable KS Department of Health and Environment with the toggle — no credentials needed.
Call searchSpills with status: 'Open' and dateFrom: '2025-01-01' to find unresolved 2025 spills, or searchIdentifiedSites with program: 'BER - Brownfields' and status: 'Active' for live brownfield sites.
Connect to Your AI Assistant
Choose your AI assistant below for specific setup instructions
Follow these steps to connect KS Department of Health and Environment to Claude:
Step 1: Open Claude Settings
Launch Claude → Click the profile button (bottom left) → Navigate to Settings
Step 2: Access Connectors
Scroll down to the Connectors tab → Navigate to the bottom → Click “Add Custom Connector”
Step 3: Name Your Connector
Enter any name you'd like for this connector
Step 4: Get the Connector URL
Log in to PatchOps → Navigate to the /mcp page → Copy the connector URL you want to use
Step 5: Add the Connector
Paste the URL in the “Remote MCP Server URL” text box → Click Add
Step 6: Start Using
Your connector is now ready to use in Claude
Follow these steps to connect KS Department of Health and Environment to ChatGPT:
Step 1: Enable Developer Mode
Go to Settings → Connectors → Advanced → Enable Developer mode
Step 2: Create New Connector
Go back to Connectors page → Click “Create” (top right)
Step 3: Name Your Connector
Enter any name you'd like for this connector (descriptions are optional)
Step 4: Get the Connector URL
Log in to PatchOps → Navigate to the /mcp page → Copy the connector URL you want to use
Step 5: Add the URL
Paste the URL in the “MCP Server URL” text box
Step 6: Set Authentication
Click the authentication dropdown → Select “No authentication” (PatchOps handles authentication internally)
Step 7: Create the Connector
Click “I understand and want to continue” checkbox → Press Create
Step 8: Using the Connector
Start a new chat → Click the + button (left of text box) → Open dropdown → Hover over three dots labeled “More” → Select your connector
Instructions for connecting KS Department of Health and Environment to GitHub Copilot:
Coming Soon
Detailed setup instructions for GitHub Copilot will be added here.
For other MCP-compatible platforms:
Step 1: Get the Connector URL
Log in to PatchOps → Navigate to the /mcp page → Copy the connector URL you want to use
Step 2: Add to Configuration
Add this configuration to your MCP settings file. Replace the URL with your specific connector URL from the /mcp page:
"KS Department of Health and Environment-MCP": {
"url": "https://patchops.ai/api/mcp/...",
"type": "http"
}Example Configuration
Here’s an example using PatchOps MCP:
"PatchOps-MCP": {
"url": "https://patchops.ai/api/mcp/...",
"type": "http"
}