Skip to content

Watt Street — US grid, interconnection queue and data center power MCP server

net.wattstreet/gridwattstreet.netstreamable-httpv1.2.0Scanned

How long to get grid power in any US county. 39,173 filings, 1,574 counties, dated sources.

7 tools: 5 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 5 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

Anlyon alternative

5 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Watt Street — US grid, interconnection queue and data center power MCP server can do

The Watt Street — US grid, interconnection queue and data center power MCP server is published by wattstreet.net, a domain the MCP Registry verified. It has 7 tools. It can create or change data (5 tools: county_profile, load_ledger, map_data, policy_events and 1 more), but cannot delete data. 2 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 1.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 5Claude Code: ask
  • county_profileFull grid intelligence for one US county: queued MW, connected capacity, project count, median wait, lead technology.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Full grid intelligence for one US county: queued MW, connected capacity, project count, median wait, lead technology.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • interconnection_deadlinesCluster request windows, filing deadlines and compliance dates for US interconnection queues, with days remaining.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Cluster 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 has not been verified against the authority's own tariff. Do not present an unconfirmed date as a commitment.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • load_ledgerLarge-load connection requests — requests to connect big new DEMAND to the US grid.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Large-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 include ERCOT, PJM, MISO, CAISO, SPP or ISO-NE. Filter by state or size.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • map_dataGeoJSON FeatureCollection of grid activity for rendering a map: generation queue by county, data-center power requests, and AI campuses.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    GeoJSON FeatureCollection of grid activity for rendering a map: generation queue by county, data-center power requests, and AI campuses.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • policy_eventsTracked policy events — data-center moratoria, large-load tariffs, FERC and state dockets — with direction (opening/closing) and citations.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Tracked policy events — data-center moratoria, large-load tariffs, FERC and state dockets — with direction (opening/closing) and citations.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • account_statusCredits remaining on the calling key, and how to top up without a human.No findings

    Why it is in this group

    • The name "account_status" says "status": a word for reading.
    Description, as the server wrote it
    Credits remaining on the calling key, and how to top up without a human.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_projectsSearch 39,173 US grid connection applications by region, status, fuel, state or size.No findings

    Why it is in this group

    • The name "search_projects" says "search": a word for reading.
    Description, as the server wrote it
    Search 39,173 US grid connection applications by region, status, fuel, state or size. Returns project rows with MW, county, wait time and outcome.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:16 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2026-07-28
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://api.wattstreet.net/.well-known/oauth-protected-resource
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.wattstreet.net/mcp: tools/list returned 7 tools to an anonymous client, including county_profile (write), load_ledger (write), map_data (write), policy_events (write), interconnection_deadlines (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http grid https://api.wattstreet.net/mcp
claude mcp add --transport http grid https://api.wattstreet.net/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__grid__search_projects",
      "mcp__grid__account_status"
    ],
    "ask": [
      "mcp__grid__county_profile",
      "mcp__grid__load_ledger",
      "mcp__grid__map_data",
      "mcp__grid__policy_events",
      "mcp__grid__interconnection_deadlines"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as grid. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/net.wattstreet/grid/verify?hash=68fd1c85353e944df86ff4ba00ca26ab044b37bcdae3974793d0bd30c592ea89" | jq -e '.changed == false'

Pinned hash 68fd1c85353e, from Nov 18, 2026, 21:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/net.wattstreet/grid/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for net.wattstreet/grid
[![Anlyon Radar](https://radar.anlyon.com/badge/net.wattstreet/grid.svg)](https://radar.anlyon.com/servers/net.wattstreet/grid)

Source: MCP Registry. Synced Oct 21, 2026, 18:53 UTC.

Watt Street — US grid, interconnection queue and data center power MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Watt Street — US grid, interconnection queue and data center power MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Watt Street — US grid, interconnection queue and data center power MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Watt Street — US grid, interconnection queue and data center power MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Watt Street — US grid, interconnection queue and data center power MCP server have?

7 tools: 5 write, 2 read. county_profile, load_ledger, map_data, policy_events, interconnection_deadlines, search_projects and account_status.

Does the Watt Street — US grid, interconnection queue and data center power MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Watt Street — US grid, interconnection queue and data center power MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Watt Street — US grid, interconnection queue and data center power MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.