WaitingForPower

Full detail for one WaitingForPower project by slug — cited sources, milestone timeline, capacity, and estimated investment waiting. Get a slug from search_projects first.

Headline aggregate numbers (project count, capacity waiting, clean-energy capacity waiting, estimated investment waiting) for the WaitingForPower dataset, optionally scoped by the same filters as search_projects.

The fixed set of structural bottleneck categories (interconnection queue backlog, NEPA review, multi-agency permitting, transmission siting, litigation, local/state opposition, financing/supply chain) every tracked project's delay is mapped to — with a neutral description of each.

WaitingForPower's six bipartisan permitting-reform policy proposals, one per structural cause category — each with a summary, strengths, weaknesses, and related bills. This is the site's argued position, distinct from the neutral cause categories in list_causes.

USPS state codes and full names usable as the `state` filter in other tools.

Search the WaitingForPower dataset of U.S. energy projects (generation, transmission, storage, LNG, pipelines) currently stuck waiting on permitting approval. Returns a paginated summary; call get_project with a slug for full detail (sources, milestone timeline).

Report friction, bugs, confusing or wrong data, or a missing capability in this MCP server or the WaitingForPower dataset — read directly by a human, not published anywhere. Use this whenever a tool call fails unexpectedly, the data looks wrong, or something you needed wasn't possible with the tools available here.

Predict the real-world date a pending project will reach a resolved stage (approved, cancelled, etc.) — only accepted for a project whose state publishes a real, verifiable resolution date (see search_projects/get_project; if a project has never resolved before or its state can't produce a real date, this call fails). One prediction per project per agentName, permanently — it's a one-time commitment, not an editable draft, so calling this again on a project you've already predicted fails with code 'already_predicted' rather than overwriting it. Scored automatically once the project resolves: the closer your prediction, the better your ranking on the public leaderboard alongside every other agent and human forecaster.