A demonstration

About

Geothermal Permitting Coordination Platform

For a specified geothermal project it identifies applicable reviews, the responsible agency for each, the dependencies among them, and an estimated duration of the sequence.

What GPCP reads

GPCP reads each source through a Model Context Protocol server. The page is what those servers returned, plus the encoded rule set. Lease polygons are from the public Bureau of Land Management Mineral and Land Records System. Connector status is read from the published SEPI index at sepi.thermalunderground.org/connectors.json.

Each server wraps one source and exposes read-only tools. Each response carries its source name, endpoint, and retrieval timestamp.

ServerSource
ecfreCFR and Federal Register public APIs
ipacUSFWS IPaC Location API
sepiSEPI · BLM AFMSS well records
gpcp-timelineEncoded dependency rule set

The schedule is computed from the rule set by topological sort. Same input, same output, every time.

MCP servers are local processes. A static host cannot run them. This site publishes what they produced, with geospatial and reference records from public federal services.

Provenance

Every record carries a marker.

SEPI Captured Extracted Live API

SEPI

Connector status supplied through the Subsurface Energy Permitting Index. SEPI is a separate system. GPCP reads the published index. Records that arrive through SEPI are marked SEPI on that project’s identifier layer.

Captured

Returned by a public federal endpoint on 20–21 August 2026 and stored.

Extracted

Derived from a published dataset by a third party.

Live API

Returned by a public federal endpoint during a session.

Sources

USFWS IPaC · eCFR · Federal Register · USGS PAD-US · USFWS National Wetlands Inventory · USGS National Hydrography Dataset · USGS 3DEP · Census TIGERweb · BLM MLRS · SEPI · OpenEI RAPID Toolkit · INFRA-COMPASS · PNNL PermitAI

Rule set v0.3.0. Data captured 20–21 August 2026.