Remote MCP · Endpoint

Meet.bot MCP MCP server

No. Meet.bot MCP answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://mcp.meet.bot/

The last check completed an MCP handshake.

Registry name
bot.meet/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
106 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
AI-native scheduling and booking: check availability, book meetings, share links.
Listing
From the official MCP registry (active).
Recent checks of Meet.bot MCP
CheckedResultHandshake
3 hours agoHandshake completed106 ms
2 days agoHandshake completed127 ms
4 days agoHandshake completed125 ms
5 days agoHandshake completed120 ms
7 days agoHandshake completed132 ms
8 days agoHandshake completed122 ms
9 days agoHandshake completed116 ms
12 days agoHandshake completed123 ms
13 days agoHandshake completed135 ms
15 days agoHandshake completed130 ms
16 days agoHandshake completed112 ms
17 days agoHandshake completed106 ms
18 days agoHandshake completed117 ms
19 days agoHandshake completed112 ms
20 days agoHandshake completed122 ms
21 days agoHandshake completed131 ms
22 days agoHandshake completed124 ms

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

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