
Watt Street MCP server
Which MCP servers are Watt Street's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-26
- Registry namenet.wattstreet/gridverified in the MCP registry
The registry name sits under wattstreet.net. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-26
- Tools7
- Server calls itselfwatt-street
- Server version1.0.0
- Protocol version2026-07-28
On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 93 ms.
- Its tools do every use case we checked: check queued power projects and wait times by county; track data center requests to connect to the grid.
- Checked on 1 of the 7 days it takes to judge reliability.
Once connected
- For "check queued power projects and wait times by county", the likely first call is county_profile.
- For "track data center requests to connect to the grid", the likely first call is load_ledger.
- Parameters are untyped or undescribed in 5 of 7 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
- What an agent can do with it2 of 2 use cases
- Answeredmeasuring1 of the 7 daily checks it takes to print a share
- Median first answer90 ms
- Space in an agent's context≈ 715 tokensthe definitions of all its tools (7), which an agent carries on every turn
- Tool definitionsB · 88 of 100
- Typed results0 of 7 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 5 of 7
What an agent can do with it
- can do · check queued power projects and wait times by county
- can do · track data center requests to connect to the grid
- not sure · review rules and dockets that affect nearby projects
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
search_projectsSearch 39,173 US grid connection applications by region, status, fuel, state or size. Returns project rows with MW, county, wait time and outcome.
county_profileFull grid intelligence for one US county: queued MW, connected capacity, project count, median wait, lead technology.
load_ledgerLarge-load connection requests — requests to connect big new DEMAND to the US grid. 528 requests on file from BPA and NYISO only; 494 state no end use, so most cannot be attributed to data centers or any other industry. Does not yet…
map_dataGeoJSON FeatureCollection of grid activity for rendering a map: generation queue by county, data-center power requests, and AI campuses.
policy_eventsTracked policy events — data-center moratoria, large-load tariffs, FERC and state dockets — with direction (opening/closing) and citations.
interconnection_deadlinesCluster request windows, filing deadlines and compliance dates for US interconnection queues, with days remaining. Every date carries its source and how well it has been checked — a date marked unconfirmed came from a secondary source and…
account_statusCredits remaining on the calling key, and how to top up without a human.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"grid": {
"type": "http",
"url": "https://api.wattstreet.net/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http wattstreet https://api.wattstreet.net/mcpclaude.ai, ChatGPT and other clients: add https://api.wattstreet.net/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.