Remote MCP · Endpoint

Tempi MCP server

No. Tempi answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://meettempi.com/mcp

The last check completed an MCP handshake.

Registry name
com.meettempi/tempi
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
827 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Find open times and book, reschedule or cancel meetings on anyone's Tempi link. No account needed.
Listing
From the official MCP registry (active).
Recent checks of Tempi
CheckedResultHandshake
1 hour agoHandshake completed827 ms
1 day agoHandshake completed417 ms
3 days agoHandshake completed630 ms
6 days agoHandshake completed356 ms
7 days agoHandshake completed590 ms
9 days agoHandshake completed468 ms
10 days agoHandshake completed296 ms
11 days agoHandshake completed351 ms
13 days agoHandshake completed411 ms
15 days agoHandshake completed418 ms
17 days agoHandshake completed293 ms
19 days agoHandshake completed571 ms
20 days agoHandshake completed300 ms
21 days agoHandshake completed265 ms
22 days agoHandshake completed336 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 Tempi and makes no claim about it beyond what these checks measured.