Remote MCP · Endpoint

Emission Factors MCP server

No. Emission Factors answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://emission-factors.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.rozetyp/emission-factors
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.16 s
Tools exposed
11 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Keyless US grid carbon + power cost by ZIP: eGRID Scope 2, Scope 1 fuels, site ranking, clean hours
Listing
From the official MCP registry (active).
Recent checks of Emission Factors
CheckedResultHandshake
1 hour agoHandshake completed1.16 s
4 days agoHandshake completed425 ms
7 days agoHandshake completed84 ms
16 days agoHandshake completed129 ms
16 days agoHandshake completed88 ms
18 days agoHandshake completed66 ms
19 days agoHandshake completed92 ms
20 days agoHandshake completed87 ms
21 days agoHandshake completed103 ms
22 days agoHandshake completed125 ms
23 days agoHandshake completed285 ms
26 days agoHandshake completed229 ms
29 days agoHandshake completed408 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 22 responding of 22.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Emission Factors and makes no claim about it beyond what these checks measured.