VolunteerReminder
https://mcp.volunteerreminder.com/mcp ↗
Description
Import a volunteer roster and preview shifts. Test-mode until a human enables live SMS.
What our measurements say
VolunteerReminder is a remote MCP server published at mcp.volunteerreminder.com. It has been probed 8 times since 9/12/2026. It answered in 8 of them (100.0%), a near-uninterrupted record. Median response time is 456 ms, placing it among the faster endpoints. It exposes a broad tool surface of 23 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Tool names clearly indicate their purpose (e.g., 'get_account_overview', 'list_schedules').
- Some descriptions provide context for when to use the tool (e.g., 'call this first to understand the account').
Weaknesses
- Multiple descriptions are cut off (e.g., 'preview_schedule_occurrences' ends with 'rea' instead of 'read').
- Parameters with type 'null' lack clarity (e.g., 'time' in 'create_schedule').
- Some tools have overlapping purposes (e.g., 'add_contacts' vs. 'assign_contacts_to_schedule').
preview_schedule_occurrences— Description is cut off, missing critical scope information ('read').create_schedule— Parameters like 'time' have type 'null', which is unclear.update_schedule— No mention of error handling for invalid recurrence parameters.
Verdict
Event narrative
Risk: low
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test failed · last run:
- Cold-start: cold 45ms → warm 54ms (penalty 0ms)
Tools
Tools the server advertised in the latest measurement — measured, not catalog-claimed.
get_account_overviewRead the current VolunteerReminder account: organization name, plan and entitlements, current reminder send mode, and volunteer usage vs the plan limit. Call this first to understand what the account can do before creating schedules or contacts. Note the `reminder_mode`: an account created through this connector (create_account) starts in `test` (reminders reroute to the owner, never to volunteers); only a human can switch it to `live` from the dashboard. `effective_mode` is what actually happens at send time.
list_schedulesList all active (non-archived) schedules on the account, each with its description, job/role, next upcoming occurrence, and how many volunteers are rostered. Requires the `read` scope.
get_scheduleGet one schedule's full configuration: recurrence settings, job/role, group, roster (contact ids), start/end dates, and notes. Requires the `read` scope.
schedule_idintegerrequired
preview_schedule_occurrencesPURE and side-effect-free: computes the next occurrence dates a recurrence configuration WOULD produce, without creating anything. Use this to show the user the concrete dates (e.g. 'the next 8 Tuesdays at 9:00 AM Central') and get their confirmation BEFORE calling create_schedule. Requires the `read` scope.
schedule_typestringrequireddays_of_weekarraynth_weekdaystringweek_of_monthintegerday_of_monthintegerstart_monthintegertimestart_dateend_datecustom_datesarraycountinteger
get_upcoming_shiftsList a schedule's upcoming occurrences (shifts) in a date range, each with its date/time, whether the roster is attending that date, and the assigned volunteers. Requires the `read` scope.
schedule_idintegerrequiredfromstringtostringlimitinteger
create_scheduleCreate a recurring (or custom-date) schedule and materialize its upcoming occurrences. Best practice: call preview_schedule_occurrences with the same recurrence settings first and confirm the dates with the user. This tool returns the created schedule AND an inline preview of its next occurrences so you can show what was set up. You can optionally seed the roster with contact_ids at creation. Requires the `schedules:write` scope.
descriptionstringrequiredjob_namestringrequiredgroup_idschedule_typestringrequireddays_of_weekarraynth_weekdaystringweek_of_monthintegerday_of_monthintegerstart_monthintegertimestart_dateend_datecustom_datesarraycontact_idsarraynotes
update_schedulePartially update a schedule — send only the fields you want to change; unset fields keep their current value. Changing recurrence fields recomputes and re-materializes future occurrences. This tool does NOT change the roster; use assign_contacts_to_schedule for that. Requires the `schedules:write` scope.
schedule_idintegerrequireddescriptionstringjob_namestringgroup_idschedule_typestringdays_of_weekarraynth_weekdaystringweek_of_monthintegerday_of_monthintegerstart_monthintegertimestart_dateend_datecustom_datesarraynotes
archive_scheduleArchive (soft-delete) a schedule. It stops appearing in the active list and no further reminders go out for it, but past reminder history is preserved. This is reversible only from the dashboard. Confirm with the user before archiving. Requires the `schedules:write` scope.
schedule_idintegerrequired
list_contactsList all volunteers on the account's roster, each with contact details and group. Requires the `read` scope.
add_contactsAdd one or more volunteers to the roster in a single call. ALL-OR-NOTHING: if the batch would push the account past its plan's volunteer limit, or any contact references a group_id not on this account, NOTHING is added and the error names the limit/count/bad id so you can adjust. Phone numbers are validated and normalized to E.164. Requires the `contacts:write` scope.
contactsarrayrequired
update_contactUpdate a volunteer's details. Send only the fields you want to change; a field set to null clears it. Requires the `contacts:write` scope.
contact_idintegerrequiredfull_namestringfirst_namelast_nameemail_addressmobile_phoneland_phonegroup_idnotes
remove_contactRemove (soft-delete) a volunteer from the roster. This frees a volunteer-cap slot and removes them from any schedule rosters they were on. Confirm with the user before removing. Requires the `contacts:write` scope.
contact_idintegerrequired
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Added to watch — era: Legacy
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/com-volunteerreminder-mcp)<a href="https://mcpmetrics.io/servers/com-volunteerreminder-mcp"><img src="https://mcpmetrics.io/badge/com.volunteerreminder/mcp/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to seeSimilar MCP servers
The catalog entries whose name and description are closest to this one, found with the same index the search box uses.
- Python Package Runtime Testapcs-public-mcp-gateway.itsnotevenbutter03.workers.dev
Test a Python package/version on a target runtime. Scoped Linux install and usable-import evidence.
- Human Design API (Human Design Hub)api.humandesignhub.app
JPL-referenced Human Design charts for AI agents: bodygraph, transit, composite, Penta, DreamRave.
- app.netlify.micropay-test-suite/micropay-test-suitemicropay-test-suite.netlify.app
Verify your agent's x402 payment flow for free on Base Sepolia testnet before real money moves.
- QA Test Serverqa-test-cli-b955e6a8.alpic.live
Testing publish command
- Link Preview Cache APIlink-preview-cache-api.onrender.com
Same link preview data as link-preview-api, ~1/3 the price via a shared cache.
- ME Human Capabilitymcp-production-ff29.up.railway.app
Human judgment for AI agents: discover capabilities, get quotes, and track paid human tasks.
Comments
Sign in to write a comment
No comments yet. Be the first.