MCP.Market

Behind the Watt MCP server

online · 100% uptime
by ykorets·io.github.ykorets/behind-the-watt·v1.0.0

Verified behind-the-meter data center power, announcements, and provenance receipts.

A91/100grade A
What users say
No reviews yet
Be the first
Safety scan
A91/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Behind the Watt yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Behind the Watt tools (4)

write = sends, deletes, buys or posts
  • get_announcementsFree

    Get the separately classified third-party reported project pipeline. These records are not BTW-verified operating capacity.

  • get_dataset_summaryFree

    Get the canonical dataset date, verified fleet totals, methodology, license and citation.

  • get_facilityFree

    Get one verified facility dossier including units, permits, quotes, source URLs, SHA-256 checksums and archived evidence links.

  • search_facilitiesFree

    Search BTW-verified behind-the-meter power facilities. Returns published facts and capacity; announcements are not included.

Public scan report

scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 828ms20/20
  • Tool poisoning4 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 3 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 91/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Behind the Watt compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 85% of 48,255 servers
Tools
4
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
171 ms
faster than 69% of 30,031 servers

What its tools let an agent do: 4 read

Install Behind the Watt in Claude Code, Cursor or VS Code

claude mcp add --transport http behind-the-watt https://mcp.behindthewatt.com/mcp
Add to Cursor

What the publisher says

From the Behind the Watt repository's README, as published. We do not edit it. Read it on GitHub

behind│the watt

The open database of behind-the-meter data center power. Who's actually online, how fast they got there, and what their power really costs. Tracked daily. Sourced from air permits, not press releases.

  • Site: site/ — Astro static build → behindthewatt.com
  • Engine: engine/ — watchers → archive → LLM extraction → review → publish
  • Data mirror: generated read-only export, will live at behindthewatt/data (own repo)
  • Architecture: docs/architecture.md · decisions: docs/decisions.md

Licenses

  • Code: MIT (LICENSE)
  • Data: CC BY 4.0 (LICENSE-DATA.md) — cite as Behind the Watt, behindthewatt.com

Status

Pre-launch. Genesis dataset: 3 verified operating facilities, pilot of Jul 2026.

Nothing above is checked by us. What we check is on the safety report.

Behind the Watt: common questions

Is Behind the Watt MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the Behind the Watt safety report
How do I install Behind the Watt?
It runs remotely at mcp.behindthewatt.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Behind the Watt need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Behind the Watt maintained?
The last commit was 43 days ago (2026-09-22). The latest release is v1.0.0.
Is Behind the Watt up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Behind the Watt compare with other MCP servers?
safety score 91/100 (higher than 85% of 48,255 servers); tools 4 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.