Home / MCP registry index / com.volunteerreminder/mcp
VolunteerReminder
com.volunteerreminder/mcp in the official MCP registry.
Endpoint https://mcp.volunteerreminder.com/mcp. Source: github.com/talltimbersgroup/VolunteerReminder.
The registry describes it as: Import a volunteer roster and preview shifts. Test-mode until a human enables live SMS.
We read its 23 tools on 2026-10-22. 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
get_account_overview list_schedules get_schedule preview_schedule_occurrences get_upcoming_shifts create_schedule update_schedule archive_schedule list_contacts add_contacts update_contact remove_contact assign_contacts_to_schedule import_volunteer_schedule get_open_days get_reminder_settings get_send_history set_reminder_rule remove_reminder_rule send_test_reminder get_pricing create_account start_checkout
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-volunteerreminder-mcp)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.