Home / MCP registry index / com.reminderit/reminderit
ReminderIt
com.reminderit/reminderit in the official MCP registry.
Endpoint https://mcp.reminderit.com/mcp.
The registry describes it as: Schedule real phone-call reminders with WhatsApp follow-up — medication, wake-ups, family check-ins.
We read its 25 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
list_reminders get_reminder list_upcoming get_recent_calls create_reminder update_reminder set_reminder_voice clear_reminder_voice set_reminder_channels set_skip_dates pause_reminder resume_reminder skip_next_occurrence test_call delete_reminder list_voices get_voice_settings set_voice_settings preview_voice whoami get_usage list_recipients add_recipient resend_recipient_verification remove_recipient
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-reminderit-reminderit)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.