Remote MCP · Endpoint

io.github.lazymac2x/api-schema-drift-detector MCP server

No. io.github.lazymac2x/api-schema-drift-detector answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.lazy-mac.com/api-schema-drift-detector/mcp

The last check completed an MCP handshake.

Registry name
io.github.lazymac2x/api-schema-drift-detector
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
134 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Cloudflare Workers MCP server: api-schema-drift-detector
Listing
From the official MCP registry (active).
Recent checks of io.github.lazymac2x/api-schema-drift-detector
CheckedResultHandshake
1 hour agoHandshake completed134 ms
1 day agoHandshake completed150 ms
2 days agoHandshake completed176 ms
3 days agoHandshake completed75 ms
4 days agoHandshake completed160 ms
5 days agoHandshake completed217 ms
6 days agoHandshake completed151 ms
9 days agoHandshake completed217 ms
11 days agoHandshake completed222 ms
14 days agoHandshake completed307 ms
16 days agoHandshake completed256 ms
18 days agoHandshake completed168 ms
20 days agoHandshake completed82 ms
22 days agoHandshake completed213 ms
24 days agoHandshake completed47 ms
26 days agoHandshake completed92 ms
27 days agoHandshake completed97 ms
29 days agoHandshake completed587 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 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.

Listing data comes from the official MCP registry. Glide is not affiliated with io.github.lazymac2x/api-schema-drift-detector and makes no claim about it beyond what these checks measured.