Skip to content

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

by wattstreet.net · remote · no sign-in to list tools · v1.2.0 · published by net.wattstreet

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

Changes · 5
CompareRegistry entry

7 tools: 5 change things and 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

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 2Claude Code: allow
  • 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.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, 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. It assumes the server is installed as grid. Review it before you use it.