Remote MCP · Endpoint

MeetZone MCP server

No. MeetZone answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://meetzone-api.mike-tusa.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.workers.mike-tusa.meetzone-api/meetzone-api
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
65 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Find meeting times that overlap working hours across IANA time zones, DST-aware. Free tier.
Listing
From the official MCP registry (active).
Recent checks of MeetZone
CheckedResultHandshake
2 days agoHandshake completed65 ms
3 days agoHandshake completed163 ms
3 days agoHandshake completed70 ms
5 days agoHandshake completed72 ms
6 days agoHandshake completed142 ms
7 days agoHandshake completed95 ms
8 days agoHandshake completed67 ms
9 days agoHandshake completed109 ms
11 days agoHandshake completed478 ms
13 days agoHandshake completed58 ms
16 days agoHandshake completed338 ms
18 days agoHandshake completed86 ms
20 days agoHandshake completed60 ms
22 days agoHandshake completed44 ms
24 days agoHandshake completed59 ms

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

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