# VolunteerReminder (remote · mcp.volunteerreminder.com)

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

- Trust score: 68/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.volunteerreminder.com`: 68/100 (this document), [markdown](https://verifymcp.io/servers/com-volunteerreminder-mcp/mcp.md), [page](https://verifymcp.io/servers/com-volunteerreminder-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.volunteerreminder.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (archive_schedule).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4430 tokens (~192/item across 23 items; 23 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 94/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 3 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "get_send_history" implies "send" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the VolunteerReminder MCP server?

VolunteerReminder is a hosted endpoint at https://mcp.volunteerreminder.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-volunteerreminder-mcp 'https://mcp.volunteerreminder.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-volunteerreminder-mcp": {
      "url": "https://mcp.volunteerreminder.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-volunteerreminder-mcp]
url = "https://mcp.volunteerreminder.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-volunteerreminder-mcp": {
      "type": "remote",
      "url": "https://mcp.volunteerreminder.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-volunteerreminder-mcp --url 'https://mcp.volunteerreminder.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-volunteerreminder-mcp:
    url: "https://mcp.volunteerreminder.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-volunteerreminder-mcp": {
      "Transport": "http",
      "Url": "https://mcp.volunteerreminder.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-volunteerreminder-mcp -t streamable-http -u 'https://mcp.volunteerreminder.com/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 63, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-08 (score 63)

First indexed and scored.

## MCP tools (23)

### `get_account_overview` (~115 tokens)

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.

Output parameters:

- `account` (object)
- `effective_mode` (string)
- `plan` (object)
- `reminder_mode` (string)
- `usage` (object)

### `list_schedules` (~51 tokens)

List schedules

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.

Output parameters:

- `schedules` (array)

### `get_schedule` (~64 tokens)

Get a schedule

Get one schedule's full configuration: recurrence settings, job/role, group, roster (contact ids), start/end dates, and notes. Requires the `read` scope.

Input parameters:

- `schedule_id` (integer, required): The schedule's numeric id (from list_schedules or get_schedule).

Output parameters:

- `description` (string)
- `id` (number)
- `schedule_type` (string)

### `preview_schedule_occurrences` (~516 tokens)

Preview upcoming occurrence dates

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.

Input parameters:

- `count` (integer): How many upcoming occurrences to return (default 8, max 52).
- `custom_dates` (array): Explicit list of "yyyy-MM-dd" dates. Required (non-empty) when schedule_type is 'custom'; ignored otherwise.
- `day_of_month` (integer): Fixed day of the month for the 'fixed' types. Defaults to 1. Clamped to the last day of shorter months (e.g. 31 in February becomes the 28th/29th).
- `days_of_week` (array): Weekday names this recurs on, e.g. ["tuesday","thursday"]. Required (non-empty) when schedule_type is 'weekly'; ignored otherwise.
- `end_date`: "yyyy-MM-dd" (account timezone) after which occurrences stop, or null for no end date.
- `nth_weekday` (string): The weekday that recurs, for schedule_type 'monthly_nth'/'bimonthly_nth'. Defaults to sunday for those types.
- `schedule_type` (string, required): Recurrence shape. 'weekly' recurs on one or more days of the week; 'monthly_fixed'/'bimonthly_fixed' recur on a fixed day of the month; 'monthly_nth'/'bimonthly_nth' recur on the Nth weekday of the m…
- `start_date`: "yyyy-MM-dd" (account timezone) before which no occurrences materialize, or null for no lower bound.
- `start_month` (integer): Anchor month (1=January … 12=December) the every-other-month cadence steps from, for the 'bimonthly_*' types. Defaults to the account's current month.
- `time`: Wall-clock time of day "HH:mm" (24-hour) in the account timezone, or null for no specific time.
- `week_of_month` (integer): Which occurrence of the weekday in the month (1st–5th), for the Nth-weekday types. Defaults to 1.

Output parameters:

- `occurrences` (array)
- `time_zone` (string)

### `get_upcoming_shifts` (~150 tokens)

Get upcoming shifts for a schedule

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.

Input parameters:

- `from` (string): Start of the range: "yyyy-MM-dd" (account timezone) or a full ISO 8601 datetime. Defaults to now.
- `limit` (integer): Maximum shifts to return (default 20, max 100).
- `schedule_id` (integer, required): The schedule's numeric id (from list_schedules or get_schedule).
- `to` (string): End of the range, same formats as `from`. Defaults to 90 days from now.

Output parameters:

- `occurrences` (array)

### `create_schedule` (~648 tokens)

Create a 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.

Input parameters:

- `contact_ids` (array): Optional initial roster (volunteer contact ids) to assign at creation. Ids not owned by this account are silently dropped. To change a roster later, use assign_contacts_to_schedule.
- `custom_dates` (array): Explicit list of "yyyy-MM-dd" dates. Required (non-empty) when schedule_type is 'custom'; ignored otherwise.
- `day_of_month` (integer): Fixed day of the month for the 'fixed' types. Defaults to 1. Clamped to the last day of shorter months (e.g. 31 in February becomes the 28th/29th).
- `days_of_week` (array): Weekday names this recurs on, e.g. ["tuesday","thursday"]. Required (non-empty) when schedule_type is 'weekly'; ignored otherwise.
- `description` (string, required): Short label shown on the schedule list and in reminders, e.g. "Sunday greeters".
- `end_date`: "yyyy-MM-dd" (account timezone) after which occurrences stop, or null for no end date.
- `group_id`: Id of an existing volunteer group to attach, or null. Unknown ids are ignored.
- `job_name` (string, required): The role/task volunteers are reminded about. Matched case-insensitively against the account's existing jobs and created if new.
- `notes`: Free-text internal notes, or null.
- `nth_weekday` (string): The weekday that recurs, for schedule_type 'monthly_nth'/'bimonthly_nth'. Defaults to sunday for those types.
- `schedule_type` (string, required): Recurrence shape. 'weekly' recurs on one or more days of the week; 'monthly_fixed'/'bimonthly_fixed' recur on a fixed day of the month; 'monthly_nth'/'bimonthly_nth' recur on the Nth weekday of the m…
- `start_date`: "yyyy-MM-dd" (account timezone) before which no occurrences materialize, or null for no lower bound.
- `start_month` (integer): Anchor month (1=January … 12=December) the every-other-month cadence steps from, for the 'bimonthly_*' types. Defaults to the account's current month.
- `time`: Wall-clock time of day "HH:mm" (24-hour) in the account timezone, or null for no specific time.
- `week_of_month` (integer): Which occurrence of the weekday in the month (1st–5th), for the Nth-weekday types. Defaults to 1.

Output parameters:

- `schedule` (object)
- `upcoming_occurrences` (array)

### `update_schedule` (~565 tokens)

Update a 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. This tool does NOT change the roster; use assign_contacts_to_schedule for that. Requires the `schedules:write` scope.

Input parameters:

- `custom_dates` (array): Explicit list of "yyyy-MM-dd" dates. Required (non-empty) when schedule_type is 'custom'; ignored otherwise.
- `day_of_month` (integer): Fixed day of the month for the 'fixed' types. Defaults to 1. Clamped to the last day of shorter months (e.g. 31 in February becomes the 28th/29th).
- `days_of_week` (array): Weekday names this recurs on, e.g. ["tuesday","thursday"]. Required (non-empty) when schedule_type is 'weekly'; ignored otherwise.
- `description` (string): New schedule label.
- `end_date`: "yyyy-MM-dd" (account timezone) after which occurrences stop, or null for no end date.
- `group_id`: New group id, or null to detach. Unknown ids are ignored.
- `job_name` (string): New job/role name.
- `notes`: New notes, or null to clear.
- `nth_weekday` (string): The weekday that recurs, for schedule_type 'monthly_nth'/'bimonthly_nth'. Defaults to sunday for those types.
- `schedule_id` (integer, required): The schedule's numeric id (from list_schedules or get_schedule).
- `schedule_type` (string): Recurrence shape. 'weekly' recurs on one or more days of the week; 'monthly_fixed'/'bimonthly_fixed' recur on a fixed day of the month; 'monthly_nth'/'bimonthly_nth' recur on the Nth weekday of the m…
- `start_date`: "yyyy-MM-dd" (account timezone) before which no occurrences materialize, or null for no lower bound.
- `start_month` (integer): Anchor month (1=January … 12=December) the every-other-month cadence steps from, for the 'bimonthly_*' types. Defaults to the account's current month.
- `time`: Wall-clock time of day "HH:mm" (24-hour) in the account timezone, or null for no specific time.
- `week_of_month` (integer): Which occurrence of the weekday in the month (1st–5th), for the Nth-weekday types. Defaults to 1.

Output parameters:

- `description` (string)
- `id` (number)

### `archive_schedule` (~86 tokens)

Archive a 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.

Input parameters:

- `schedule_id` (integer, required): The schedule's numeric id (from list_schedules or get_schedule).

Output parameters:

- `archived` (boolean)
- `id` (number)

### `list_contacts` (~31 tokens)

List volunteers

List all volunteers on the account's roster, each with contact details and group. Requires the `read` scope.

Output parameters:

- `contacts` (array)

### `add_contacts` (~117 tokens)

Add volunteers

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.

Input parameters:

- `contacts` (array, required): The volunteers to add (1–200 per call). Each needs at least a full_name.

Output parameters:

- `created` (array)

### `update_contact` (~206 tokens)

Update a volunteer

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.

Input parameters:

- `contact_id` (integer, required): The contact's numeric id (from list_contacts).
- `email_address`: Email address reminders may be sent to, or null.
- `first_name`: First name, or null.
- `full_name` (string): New display name.
- `group_id`: Id of an existing group on this account to file the contact under, or null.
- `land_phone`: Landline number (informational only, never texted), or null.
- `last_name`: Last name, or null.
- `mobile_phone`: Mobile number for SMS reminders. Accepts E.164 (+15125550100) or a plain 10-digit US/Canada number; stored as E.164. Send null to clear.
- `notes`: Free-text notes about the contact, or null.

Output parameters:

- `full_name` (string)
- `id` (number)

### `remove_contact` (~70 tokens)

Remove a volunteer

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.

Input parameters:

- `contact_id` (integer, required): The contact's numeric id (from list_contacts).

Output parameters:

- `deleted` (boolean)
- `id` (number)

### `assign_contacts_to_schedule` (~125 tokens)

Set a schedule's roster

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.

Input parameters:

- `contact_ids` (array, required): The complete set of volunteer contact ids for this schedule (replaces any existing roster). Empty array clears the roster.
- `schedule_id` (integer, required): The schedule to assign the roster to.

Output parameters:

- `contact_ids` (array)
- `schedule_id` (number)

### `import_volunteer_schedule` (~361 tokens)

Import a volunteer roster and 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).

Input parameters:

- `confirm` (boolean): false (default) = parse and preview only, no writes. true = create the contacts, schedules, and assignments after the user approved the preview. confirm=true requires preview_token from the preceding…
- `consent_attested` (boolean): Required true on confirm=true when any contact has a phone number. Affirms the volunteers agreed to receive shift-reminder texts.
- `preview_token` (string): Required when confirm=true. Copy the preview_token returned by the preceding confirm=false call for this exact roster text.
- `text` (string, required): The roster as CSV, TSV, pipe-delimited text, or a headerless table in the order name, phone, email, job, day, start, end. Quoted CSV fields are fine. Do not log this text.

Output parameters:

- `assignments_created` (number)
- `contact_count` (number)
- `contacts_created` (number)
- `errors` (array)
- `ok` (boolean)
- `preview_token` (string)
- `reminder_mode` (string)
- `reminder_mode_note` (string)
- `row_count` (number)
- `schedule_count` (number)
- `schedules` (array)
- `schedules_created` (number)
- `skipped_row_count` (number)
- `warnings` (array)

### `get_open_days` (~107 tokens)

Get open days (who do we still need?)

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.

Input parameters:

- `current_year_only` (boolean): When true (the default), clamp the window to the end of the current calendar year instead of crossing into next year.
- `months` (integer): How many months to look ahead (1–24). Default 12.

Output parameters:

- `open_dates` (array)
- `open_schedules` (array)

### `get_reminder_settings` (~61 tokens)

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.

Output parameters:

- `channels` (object)
- `global_default`
- `job_overrides` (array)

### `get_send_history` (~80 tokens)

Get reminder 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.

Input parameters:

- `page` (integer): 1-indexed page number. Default 1.
- `per_page` (integer): Rows per page (max 100). Default 20.

Output parameters:

- `entries` (array)
- `has_more` (boolean)
- `total` (number)

### `set_reminder_rule` (~162 tokens)

Set a 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). Requires the `reminders:write` scope.

Input parameters:

- `global_default` (object): Set (or replace) the account-wide default lead time.
- `job_override` (object): Create or replace the lead-time override for one job.
- `require_sms` (boolean): Assert SMS should be used. If true and the plan does NOT include SMS, the whole request is rejected with an upgrade hint (nothing is saved). Omit or set false to make no assertion.

### `remove_reminder_rule` (~78 tokens)

Remove a 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.

Input parameters:

- `job_id` (integer): Remove this job's lead-time override. Omit to clear the account-wide default.

### `send_test_reminder` (~98 tokens)

Send a test reminder to the account owner

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.

Input parameters:

- `schedule_id` (integer): Preview the reminder for this schedule. Omit for a generic sample reminder.

Output parameters:

- `channel` (string)
- `delivered_to` (string)
- `note` (string)
- `schedule_id`
- `sent` (boolean)

### `get_pricing` (~70 tokens)

Get pricing and plans

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.

Output parameters:

- `plans` (array)
- `product` (string)
- `signup_url` (string)

### `create_account` (~236 tokens)

Create an account (pending email verification)

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.

Input parameters:

- `email` (string, required): The account owner's email address. The verification / sign-in link is sent here; only the person who controls this inbox can activate the account. Required.
- `organization_name` (string): Display name for the organization (becomes the account name). Optional — defaults to a placeholder the owner can rename after verifying. The account timezone defaults to America/Chicago and is editab…

Output parameters:

- `account_id` (number)
- `api_key` (null)
- `verification` (string)

### `start_checkout` (~121 tokens)

Get a Stripe Checkout link to subscribe

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`).

Input parameters:

- `interval` (string): Billing interval. Defaults to monthly.
- `plan` (string, required): The plan id to subscribe to (see get_pricing).

Output parameters:

- `checkout_url` (string)
- `interval` (string)
- `plan` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-volunteerreminder-mcp/mcp#diagnostics

## Score history

- 2026-09-20: 68
- 2026-09-19: 68
- 2026-09-18: 67
- 2026-09-17: 67
- 2026-09-16: 67
- 2026-09-15: 66
- 2026-09-14: 66
- 2026-09-13: 65
- 2026-09-12: 65
- 2026-09-11: 64
- 2026-09-10: 64
- 2026-09-09: 63
- 2026-09-08: 63

## Common questions

### What is the VolunteerReminder MCP server?

VolunteerReminder is an MCP server listed in the public MCP registry as com.volunteerreminder/mcp. Import a volunteer roster and preview shifts. Test-mode until a human enables live SMS. This page covers its hosted endpoint (https://mcp.volunteerreminder.com/mcp).

### Is the VolunteerReminder MCP server safe to use?

VolunteerReminder scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the VolunteerReminder MCP server expose?

VolunteerReminder exposes 23 tools: get_account_overview, list_schedules, get_schedule, preview_schedule_occurrences, get_upcoming_shifts, and 18 more. Their descriptions and schemas cost roughly 4,118 tokens of context every time the server is loaded.

### Does the VolunteerReminder MCP server require authentication?

No. We connected to VolunteerReminder without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the VolunteerReminder MCP server still maintained?

VolunteerReminder is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.volunteerreminder.com/mcp
- Repository: https://github.com/talltimbersgroup/VolunteerReminder
- Website: https://volunteerreminder.com/docs/agents
- Changelog RSS feed: https://verifymcp.io/servers/com-volunteerreminder-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-volunteerreminder-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-volunteerreminder-mcp/mcp