# VolunteerReminder

> Import a volunteer roster and preview shifts. Test-mode until a human enables live SMS.

- name: com.volunteerreminder/mcp
- version: 0.3.0
- connection class: R0 (autonomous)
- trust: 92/100
- quality: 72/100 (needs work)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.volunteerreminder%2Fmcp
- tools: https://api.protogrid.dev/v1/servers/com.volunteerreminder%2Fmcp/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "volunteerreminder": {
      "type": "http",
      "url": "https://mcp.volunteerreminder.com/mcp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 99
- freshness: 85
- provenance: 85
- drivers: +repository +dns-namespace +website +reachable +uptime-98% ~updated-43d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 72/100 (needs work)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 93 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 23 of 23 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- warn `tools.token_cost`: about 8,138 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 25 (weight 15)

- warn `stability.changes`: 12 tool changes in 30 days
- fail `stability.rug_pull`: 1 tools kept their name but changed most of their description in 30 days; review before trusting them

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 23, about 8,138 tokens to load them all
- tool set hash: d0befa84658f2f72529ef077bfce177c
- tools last changed: 2026-10-10T23:41:24.207Z
- badge: [![protogrid quality](https://protogrid.dev/badge/com.volunteerreminder/mcp.svg)](https://protogrid.dev/servers/com.volunteerreminder/mcp)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-10 `send_test_reminder` changed (description, annotations)
  - before: Send a single TEST reminder to the account owner's own email/phone so they can preview what a reminder looks like. This never reaches volunteers — it always reroutes to the owner. Optionally pass a schedule_id to preview that schedule's reminder; otherwise a generic sample is sent. Requires the `reminders:write` scope.
  - after: Send a single TEST reminder to the account owner's own email/phone so they can preview what a reminder looks like. This never reaches volunteers — it always reroutes to the owner. Optionally pass a schedule_id to preview that schedule's reminder; otherwise a generic sample is sent. It is a real message that cannot be unsent, so confirm with the user first. Requires the `reminders:write` scope.
- 2026-10-10 `set_reminder_rule` changed (description, inputSchema)
  - before: Set the reminder lead time: the account-wide default and/or a per-job override. Provide at least one of `global_default` or `job_override`, and set at least one of days/hours/minutes greater than zero. Overrides are per JOB (a job may back several schedules). Requires the `reminders:write` scope.
  - after: Set the reminder lead time: the account-wide default and/or a per-job override. Provide at least one of `global_default` or `job_override`, and set at least one of days/hours/minutes greater than zero. Overrides are per JOB (a job may back several schedules); get the job_id from list_schedules. Replaces any earlier override for that job. Requires the `reminders:write` scope.
- 2026-10-10 `update_contact` changed (inputSchema)
- 2026-10-10 `add_contacts` changed (description, inputSchema)
  - before: Add 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.
  - after: Add 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. Adding a mobile number needs consent_attested=true (ask the user to confirm the volunteers agreed to texts). To put new volunteers on a shift, follow with assign_contacts_to_schedule. Requires the `contacts:write` scope.
- 2026-10-10 `get_upcoming_shifts` changed (title, description, inputSchema) **meaning changed**
  - before: List 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.
  - after: Who is volunteering when. Lists upcoming shifts with date/time, schedule, whether that date is still on, and the rostered volunteers' names. Omit `schedule_id` to cover EVERY active schedule in one call (best for questions like "who is on this Sunday?": pass from and to as that same date). A bare "yyyy-MM-dd" `to` includes that whole day. Requires the `read` scope.
- 2026-10-10 `list_schedules` changed (description)
  - before: List 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.
  - after: List all active (non-archived) schedules on the account, each with its description, job/role (name and job_id), next upcoming occurrence, and how many volunteers are rostered. Requires the `read` scope.
- 2026-10-10 `set_reminder_rule` changed (inputSchema, annotations)
- 2026-10-10 `assign_contacts_to_schedule` changed (annotations)
- 2026-10-10 `update_contact` changed (annotations)
- 2026-10-01 `update_schedule` changed (description, inputSchema, annotations)
  - before: Partially 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.
  - after: Partially 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. If the change would remove upcoming shifts, nothing is saved and the tool returns confirm_remove_required with the `removed` dates and a `confirm_token`. Show the user those dates; only if they agree, call again with the same changes plus confirm_remove: true and that confirm_token. This tool does NOT change the roster; use assign_contacts_to_schedule for that. Requires the `schedules:write` scope.

Full history: https://api.protogrid.dev/v1/servers/com.volunteerreminder%2Fmcp/changes

## Remotes

- https://mcp.volunteerreminder.com/mcp (streamable-http, auth none, reachable true, uptime30d 0.982906)

## Packages

_none_

## Tools (23)

- `add_contacts`: Add 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. Adding a mobile number needs consent_attested=true (ask the user to confirm the volunteers agreed to texts). To put new volunteers on a shift, follow with assign_contacts_to_schedule. Requires the `contacts:write` scope.
- `archive_schedule`: Archive (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.
- `assign_contacts_to_schedule`: Assign volunteers to a schedule. This REPLACES the schedule's entire roster — send the COMPLETE desired set of contact ids, not a delta (pass an empty array to clear it). Every id must belong to this account or the whole request is rejected with the offending ids named. Does not change occurrences. Requires the `contacts:write` scope.
- `create_account`: Start a new VolunteerReminder account for a human, using their email address. This does NOT finish signup and does NOT return an API key: it emails the person a verification link they must click to activate the account. Nothing can be built on the account and no reminders can ever send until they verify — and even then a new account starts in safe `test` mode (reminders reach only the owner, never volunteers) until a human turns on live sending from the dashboard. Idempotent: calling it again with the same email re-sends the link and creates no duplicate. After the user tells you they've verified, they mint an API key from the dashboard and reconnect this connector with it. Tell the user to check their email.
- `create_schedule`: Create 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.
- `get_account_overview`: Read 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.
- `get_open_days`: List calendar days in the look-ahead window that have no attendable shift yet, plus recurring monthly slots not yet claimed by a schedule — i.e. where the account still needs volunteers. Requires the `read` scope.
- `get_pricing`: Read VolunteerReminder's public plan catalog: each plan's monthly and annual price (USD), volunteer limit, and included features (SMS reminders are included with no per-message credits or metering). No API key required — use this to help a user comparison-shop or decide which plan fits before they sign up.
- `get_reminder_settings`: Read the account's reminder lead times (the account-wide default plus any per-job overrides) and which channels (email / SMS) are available on the current plan. Reminder overrides are per JOB, not per individual schedule. Requires the `read` scope.
- `get_schedule`: Get one schedule's full configuration: recurrence settings, job/role, group, roster (contact ids), start/end dates, and notes. Requires the `read` scope.
- `get_send_history`: Read recent reminder outcomes — which reminders were sent and which failed — newest first, paginated. Use this to confirm reminders actually went out. Requires the `read` scope.
- `get_upcoming_shifts`: Who is volunteering when. Lists upcoming shifts with date/time, schedule, whether that date is still on, and the rostered volunteers' names. Omit `schedule_id` to cover EVERY active schedule in one call (best for questions like "who is on this Sunday?": pass from and to as that same date). A bare "yyyy-MM-dd" `to` includes that whole day. Requires the `read` scope.
- `import_volunteer_schedule`: Parse a pasted or uploaded volunteer roster + schedule (CSV or a table with columns like name, phone, email, job/role, day, start, end) and either PREVIEW or CREATE the contacts, schedules, and assignments. Always call first with confirm=false and show the user the upcoming shifts; only call again with confirm=true, passing back preview_token from that preview, after they approve. Import is test-mode only and is refused on some accounts. Use create_account first if they do not have an account — do not invent a second signup path. This tool never changes reminder mode, never enables the confirm loop or substitute finder, and never texts real volunteers. New accounts stay in test mode. Requires `read` for preview; `schedules:write` and `contacts:write` to commit. Set consent_attested=true on commit when any row has a phone number (the coordinator affirms the volunteers agreed to be texted).
- `list_contacts`: List all volunteers on the account's roster, each with contact details and group. Requires the `read` scope.
- `list_schedules`: List all active (non-archived) schedules on the account, each with its description, job/role (name and job_id), next upcoming occurrence, and how many volunteers are rostered. Requires the `read` scope.
- `preview_schedule_occurrences`: PURE 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.
- `remove_contact`: Remove (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.
- `remove_reminder_rule`: Remove a reminder lead-time rule. Provide `job_id` to remove that job's override; omit it to clear the account-wide default. Returns the updated reminder settings. Requires the `reminders:write` scope.
- `send_test_reminder`: Send a single TEST reminder to the account owner's own email/phone so they can preview what a reminder looks like. This never reaches volunteers — it always reroutes to the owner. Optionally pass a schedule_id to preview that schedule's reminder; otherwise a generic sample is sent. It is a real message that cannot be unsent, so confirm with the user first. Requires the `reminders:write` scope.
- `set_reminder_rule`: Set the reminder lead time: the account-wide default and/or a per-job override. Provide at least one of `global_default` or `job_override`, and set at least one of days/hours/minutes greater than zero. Overrides are per JOB (a job may back several schedules); get the job_id from list_schedules. Replaces any earlier override for that job. Requires the `reminders:write` scope.
- `start_checkout`: Get a Stripe-hosted Checkout URL for the account to subscribe to a paid plan, then HAND THE URL TO THE HUMAN to open and complete payment. You never take payment yourself and never see card details. Use get_pricing first to pick a plan. Fails if the account already has an active subscription (manage that from the billing dashboard). Requires a connected API key (any scope with `read`).
- `update_contact`: Update a volunteer's details. Send only the fields you want to change; a field set to null clears it. Requires the `contacts:write` scope.
- `update_schedule`: Partially 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. If the change would remove upcoming shifts, nothing is saved and the tool returns confirm_remove_required with the `removed` dates and a `confirm_token`. Show the user those dates; only if they agree, call again with the same changes plus confirm_remove: true and that confirm_token. This tool does NOT change the roster; use assign_contacts_to_schedule for that. Requires the `schedules:write` scope.