mcpbeat Sign in

WattScope MCP Server

by com-wattscope Your server? Claim it
answering

WattScope is answering right now. Last checked 9 min ago.

Tracks the estimated carbon footprint of AI model usage, per org and project.

Uptime history 61 days of history · worst day 94%
61 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
363 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check WattScope every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add wattscope --transport http https://www.wattscope.com.au/mcp
Settings → Connectors → Add custom connector, then paste this address
https://www.wattscope.com.au/mcp
~/.codex/config.toml
[mcp_servers.wattscope]
url = "https://www.wattscope.com.au/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "wattscope": {
      "url": "https://www.wattscope.com.au/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "wattscope": {
      "type": "http",
      "url": "https://www.wattscope.com.au/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://www.wattscope.com.au/mcp streamable-http sign-in 327 ms 9 min ago

Alternatives to WattScope

same job, measured the same way
AI Footprint
by nickjlamb

Water and energy footprint of AI use: chat prompts, agent sessions, methodology and sources.

4 tools answering
Hubd
by bzdos

The project tracker for teams of humans and AI agents — in plain files. MCP server + CLI.

67 installs/wk local only
Greener Ahead
by greenerahead

Your carbon footprint, VSME and CSRD reports and climate plan, with the source of every figure.

answering
Trail
by usetrail

Issue tracker and durable project memory for your coding agent, scoped to the folder you open.

129 installs/wk local only
Agile Sprint
by evozim

Scrum sprint optimizer and automated project manager.

1 tools answering
Arez AI
by ai-arez

Jobs, estimates, tasks, team messages and money owed for small US contractors.

answering
Bloomy Earth
by bloomy

Estimate the CO2e of AI usage, then plant trees, offset CO₂ or share climate actions.

answering
Homesage.ai MCP
by homesage

Estimated values, comps, rent, rehab costs and returns for 160M+ US properties, as 30+ agent tools.

answering

WattScope — questions

Answers built from our own checks of this server.

Why is there no tool list for WattScope?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is WattScope working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 363 ms. The bar chart above shows every period we have measured.
How do I connect WattScope?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to WattScope?
No API key is involved. WattScope answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is WattScope?
It answers our handshake in 363 ms on average, which is faster than 36% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.