Remote MCP · Endpoint

Tempi MCP server

No. Tempi answered an MCP handshake 6 hours ago.

UpLast checked 6 hours 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
425 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 14 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
6 hours agoHandshake completed425 ms
10 days agoHandshake completed401 ms
11 days agoHandshake completed798 ms
11 days agoHandshake completed638 ms
13 days agoHandshake completed330 ms
15 days agoHandshake completed726 ms
15 days agoHandshake completed985 ms
16 days agoHandshake completed397 ms
17 days agoHandshake completed624 ms
19 days agoHandshake completed441 ms
22 days agoHandshake completed333 ms
24 days agoHandshake completed372 ms
26 days agoHandshake completed306 ms
29 days agoHandshake completed827 ms

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

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.