Remote MCP · Endpoint

ReminderIt MCP server

No. ReminderIt answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.reminderit.com/mcp

The last check completed an MCP handshake.

Registry name
com.reminderit/reminderit
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
335 ms
Tools exposed
25 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Schedule real phone-call reminders with WhatsApp follow-up — medication, wake-ups, family check-ins.
Listing
From the official MCP registry (active).
Recent checks of ReminderIt
CheckedResultHandshake
1 hour agoHandshake completed335 ms
2 days agoHandshake completed351 ms
4 days agoHandshake completed324 ms
6 days agoHandshake completed316 ms
8 days agoHandshake completed360 ms
10 days agoHandshake completed325 ms
12 days agoHandshake completed312 ms
14 days agoHandshake completed309 ms
16 days agoHandshake completed176 ms
17 days agoHandshake completed359 ms
18 days agoHandshake completed343 ms
21 days agoHandshake completed502 ms
22 days agoHandshake completed310 ms
24 days agoHandshake completed387 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 ReminderIt and makes no claim about it beyond what these checks measured.