Remote MCP · Endpoint

Time of Meeting MCP server

No. Time of Meeting answered an MCP handshake 17 minutes ago.

UpLast checked 17 minutes ago

Server URL

https://timeofmeeting.com/mcp

The last check completed an MCP handshake.

Registry name
com.timeofmeeting/time-of-meeting
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
612 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Fair meeting times across time zones. Separate business-day and bank-day calculations.
Listing
From the official MCP registry (active).
Recent checks of Time of Meeting
CheckedResultHandshake
17 minutes agoHandshake completed612 ms
8 days agoHandshake completed212 ms
9 days agoHandshake completed161 ms
11 days agoHandshake completed198 ms
12 days agoHandshake completed347 ms
13 days agoHandshake completed160 ms
14 days agoHandshake completed143 ms
14 days agoHandshake completed238 ms
16 days agoHandshake completed164 ms
19 days agoHandshake completed222 ms
21 days agoHandshake completed191 ms
24 days agoHandshake completed152 ms
26 days agoHandshake completed148 ms
28 days agoHandshake completed143 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 Time of Meeting and makes no claim about it beyond what these checks measured.