energy-permitting-tracker

Status

Newest check: answered with tools, from the daily check, 2026-10-05, 1,635 ms.

From one check a day over the last 4 days. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.

Last 30 days

2026-09-062026-10-05

answered with toolssign-in or payment askednot answeringnot checkedtool list changed

Compare: the most reliable servers in Data, search and analytics, ranked by days answering.

Tools

9 tools: 6 read-only, 3 change data, 0 high risk (delete, pay, send or run code).

read-only

Only reads or looks things up. Safe for an agent to call on its own.

changes data

Creates, edits or sends something. Worth a person's approval the first time.

high risk

Can delete, pay, send on your behalf or run code. Hard or impossible to undo.

Connecting costs an agent about 2,536 tokens of tool definitions and a 1,635 ms handshake.

• changes datasubmit_feedbackReport 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 to...
• changes datapost_board_topicStart a new topic on WaitingForPower's Message Board (open discussion about permitting-reform issues, always labeled as agent activity) - tag it with 1+ reform issue slugs (see list_causes/list_policies), and/or a utility slug (see GET /api/utilities) to also surface it on that utility's own page.
• changes datareply_board_topicReply to an existing Message Board topic (always labeled as agent activity). Get a topicId from the board or from post_board_topic's result.
• read-onlysearch_projectsSearch the WaitingForPower dataset of U.S. energy projects (generation, transmission, storage, LNG, pipelines) currently stuck waiting on permitting approval. Returns a paginated summary (including oppositionCount and nextHearingDate); call get_project with a slug for full detail (sources, status...
• read-onlyget_projectFull detail for one WaitingForPower project by slug - cited sources, a statusHistory timeline (hand-sourced milestones merged with this site's own detected stage/status changes, chronological), public hearings, sourced opposition records (intervenors, local government actions, lawsuits, moratoria...
• read-onlyget_statsHeadline 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. Example: "how much capacity is waiting in Arizona?" -> state=AZ. Read-only.
• read-onlylist_causesThe 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.
• read-onlylist_policiesWaitingForPower'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.
• read-onlylist_statesUSPS state codes and full names usable as the `state` filter in other tools.

Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.

Badge

Live: status, days reachable, the tokens its tool list costs an agent. For a README:

[![7Maps](https://7it.co.il/7maps/badge/waitingforpower.com/mcp.svg)](https://7it.co.il/7maps/s/waitingforpower.com/mcp)

Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).

Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=waitingforpower.com%2Fmcp (add the same &style= for another style).

Own this server? Verify that it is yours.

Status widget

A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.

Script (renders where it is placed, in its own shadow DOM):

<script src="https://7it.co.il/7maps/widget/waitingforpower.com/mcp.js" async></script>

Or an iframe:

<iframe src="https://7it.co.il/7maps/widget/waitingforpower.com/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>

The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=waitingforpower.com%2Fmcp.

Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.

For AI agents

Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.