Remote MCP · Endpoint

Mycelium Emissions Database MCP server

Yes, as of 1 hour ago: the check failed for an unclassified reason.

DownLast checked 1 hour ago

Server URL

https://mycelium.global/mcp/server

The last check failed: the check failed for an unclassified reason.

Registry name
global.mycelium/emissions-database
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
3 tools
Uptime, last 30 days
33.3% from 18 checks
Described by its publisher as
Search company carbon emissions: scope 1, 2 and 3 figures, Mycelium Scores and rankings.
Website
https://mycelium.global/mcp
Repository
https://github.com/MyceliumNetwork/mcp-server
Listing
From the official MCP registry (active).
Recent checks of Mycelium Emissions Database
CheckedResultHandshake
1 hour agoFailed - the check failed for an unclassified reason—
1 day agoFailed - the check failed for an unclassified reason—
2 days agoFailed - the check failed for an unclassified reason—
3 days agoFailed - the check failed for an unclassified reason—
4 days agoFailed - the check failed for an unclassified reason—
5 days agoFailed - the check failed for an unclassified reason—
6 days agoFailed - the check failed for an unclassified reason—
9 days agoFailed - the check failed for an unclassified reason—
12 days agoFailed - the check failed for an unclassified reason—
14 days agoFailed - the check failed for an unclassified reason—
16 days agoFailed - the check failed for an unclassified reason—
18 days agoFailed - the check failed for an unclassified reason—
20 days agoHandshake completed374 ms
22 days agoHandshake completed381 ms
24 days agoHandshake completed361 ms
26 days agoHandshake completed350 ms
27 days agoHandshake completed448 ms
29 days agoHandshake completed342 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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