Remote MCP · Endpoint

AtlasClose Governance Demo MCP server

No. AtlasClose Governance Demo answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://demo.atlasclose.com/mcp

The last check completed an MCP handshake.

Registry name
com.atlasclose/demo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
722 ms
Tools exposed
53 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Experimental AtlasClose governance demo. Authority checks, labeled evidence, receipts, refusals.
Listing
From the official MCP registry (active).
Recent checks of AtlasClose Governance Demo
CheckedResultHandshake
1 hour agoHandshake completed722 ms
9 days agoHandshake completed592 ms
9 days agoHandshake completed456 ms
11 days agoHandshake completed486 ms
12 days agoHandshake completed474 ms
13 days agoHandshake completed442 ms
14 days agoHandshake completed448 ms
14 days agoHandshake completed624 ms
16 days agoHandshake completed445 ms
19 days agoHandshake completed428 ms
21 days agoHandshake completed665 ms
24 days agoHandshake completed381 ms
26 days agoHandshake completed362 ms
28 days agoHandshake completed352 ms

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

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 AtlasClose Governance Demo and makes no claim about it beyond what these checks measured.