Remote MCP · Endpoint

GreenCycle Compound Atlas MCP server

No. GreenCycle Compound Atlas answered an MCP handshake 33 minutes ago.

UpLast checked 33 minutes ago

Server URL

https://greencyclepedia.com/mcp

The last check completed an MCP handshake.

Registry name
com.greencyclepedia/atlas
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
336 ms
Tools exposed
23 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Read-only cannabis compound, receptor, anatomy and evidence data, every value sourced.
Listing
From the official MCP registry (active).
Recent checks of GreenCycle Compound Atlas
CheckedResultHandshake
33 minutes agoHandshake completed336 ms
3 days agoHandshake completed359 ms
13 days agoHandshake completed326 ms
13 days agoHandshake completed330 ms
15 days agoHandshake completed328 ms
16 days agoHandshake completed323 ms
17 days agoHandshake completed353 ms
18 days agoHandshake completed364 ms
18 days agoHandshake completed334 ms
20 days agoHandshake completed337 ms
22 days agoHandshake completed335 ms
25 days agoHandshake completed332 ms
27 days agoHandshake completed346 ms

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

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 GreenCycle Compound Atlas and makes no claim about it beyond what these checks measured.