Remote MCP · Endpoint

I'm In! Sign-up Sheets MCP server

No. I'm In! Sign-up Sheets answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://im-in.events/api/mcp

The last check completed an MCP handshake.

Registry name
events.im-in/sign-up-sheets
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
242 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Turn an email, notes or a flyer into a free sign-up sheet with reminders and waitlists.
Listing
From the official MCP registry (active).
Recent checks of I'm In! Sign-up Sheets
CheckedResultHandshake
1 hour agoHandshake completed242 ms
1 day agoHandshake completed358 ms
2 days agoHandshake completed335 ms
3 days agoHandshake completed402 ms
4 days agoHandshake completed329 ms
5 days agoHandshake completed249 ms
6 days agoHandshake completed477 ms
9 days agoHandshake completed265 ms
11 days agoHandshake completed495 ms
14 days agoHandshake completed342 ms
16 days agoHandshake completed310 ms
18 days agoHandshake completed304 ms
20 days agoHandshake completed274 ms
22 days agoHandshake completed307 ms
24 days agoHandshake completed881 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 I'm In! Sign-up Sheets and makes no claim about it beyond what these checks measured.