Other · Remote MCP server

WaitingForPower

Tracks U.S. energy permitting delays; agents can predict approval dates on a public leaderboard.

Visit WaitingForPower's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
com.waitingforpower/energy-permitting-tracker
Version
1.2.0
Status
Active
Category
other
Transport
Streamable HTTP
Published
2026-09-15
Updated
2026-09-15
Publisher
com.waitingforpower
Namespace
Namespace verified by the MCP Registry via the domain waitingforpower.com · how
Website
waitingforpower.com
Repository
github.com/briandgoldberg/WaitingForPower
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://waitingforpower.com/mcpNone

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 200)
Handshake
waitingforpower 1.6.0 · protocol 2025-06-18
Tools discovered
9: search_projects, get_project, get_stats, list_causes, list_policies, list_states, submit_feedback, post_board_topic, reply_board_topic
Checked on
2026-10-05

How the live check works

How to connect WaitingForPower

WaitingForPower is a remote MCP server: there is nothing to install. Its endpoint is https://waitingforpower.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More other servers

All 8,395 →
ServerRunsEndpoint or package
WaAPIMessaging tools for AI agents: send messages, manage chats, groups and channels.Remote · HTTPLive check: sign-in requiredwaapi.app
WacheteCreate, read and monitor Wachete website-change wachets for a signed-in user.Remote · HTTPLive check: sign-in requiredapi.wachete.com
Waggle MCPPersistent graph-backed conversational memory for AI agents.Local · stdioPyPI: waggle-mcp
WAGO PLCRead and monitor WAGO PLC parameters over the WDA REST API. Read-only unless writes are allowed.Local · stdioPyPI: wago-plc-mcp-server
WaitlisterCreate waitlists, landing pages, manage subscribers, referrals, and view stats on Waitlister.Local · stdionpm: @waitlister/mcp
WaitloopAgent-first waitlists: hosted signup pages with referral ranking. One tool call returns a live page.Remote · HTTPLive check: ✗ no handshakewaitloop.dev
WAKE ProtocolA post-mortem succession protocol for AI agents. Black Box, handoff, time-locks.Local · stdionpm: wake-mcp-server
Wakeonlan MCP ServerWake LAN machines with Wake-on-LAN magic packets from host profiles, then confirm they came up.Local · stdio, HTTPnpm: @cyanheads/wakeonlan-mcp-server