Skip to content

VolunteerReminder MCP server

com.volunteerreminder/mcpvolunteerreminder.comstreamable-httpv0.3.0Scanned

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

23 tools: 8 can delete or cancel things, 5 change things and 10 only read.

Tools: 8 delete, 0 irreversible, 5 write, 10 read.
  • Reads private data · 5
  • Reads text others write · 12
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

8 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the VolunteerReminder MCP server can do

The VolunteerReminder MCP server is published by volunteerreminder.com, a domain the MCP Registry verified. It has 23 tools. It can delete or cancel things (8 tools: update_schedule, archive_schedule, update_contact, remove_contact and 4 more) and create or change data (5 tools: create_schedule, add_contacts, import_volunteer_schedule, create_account and 1 more). 10 tools only read.

5 tools read private data (get_schedule, list_contacts, get_open_days and 2 more); 12 tools bring in text other people can write (create_schedule, update_schedule, archive_schedule and 9 more); 1 tool can send data out of your system (send_test_reminder). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 11, 2026, version 0.3.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

23 tools

Deletes or cancels 8Claude Code: deny
  • archive_scheduleArchive (soft-delete) a schedule.Reads text others writeNo findings

    Why it is in this group

    • The name "archive_schedule" says "archive": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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. If calendar invites are on for the account, assigned volunteers may get a new, updated or cancelled calendar invite by email (in test mode it goes to the owner instead).

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • assign_contacts_to_scheduleAssign volunteers to a schedule.Reads text others writeNo findings

    Why it is in this group

    • The name "assign_contacts_to_schedule" says "assign": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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. If calendar invites are on for the account, assigned volunteers may get a new, updated or cancelled calendar invite by email (in test mode it goes to the owner instead).

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • remove_contactRemove (soft-delete) a volunteer from the roster.Reads text others writeNo findings

    Why it is in this group

    • The name "remove_contact" says "remove": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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. If calendar invites are on for the account, assigned volunteers may get a new, updated or cancelled calendar invite by email (in test mode it goes to the owner instead).

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • remove_reminder_ruleRemove a reminder lead-time rule.No findings

    Why it is in this group

    • The name "remove_reminder_rule" says "remove": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • send_test_reminderSend a single TEST reminder to the account owner's own email so they can preview what a reminder looks like.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "send_test_reminder" says "send": a word for sending, and what is sent cannot be taken back.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "send_test_reminder" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Send a single TEST reminder to the account owner's own email 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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • set_reminder_ruleSet the reminder lead time: the account-wide default and/or a per-job override.No findings

    Why it is in this group

    • The name "set_reminder_rule" says "set": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • update_contactUpdate a volunteer's details.Reads text others writeNo findings

    Why it is in this group

    • The name "update_contact" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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. If calendar invites are on for the account, assigned volunteers may get a new, updated or cancelled calendar invite by email (in test mode it goes to the owner instead).

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • update_schedulePartially update a schedule — send only the fields you want to change; unset fields keep their current value.Reads text others writeNo findings

    Why it is in this group

    • The name "update_schedule" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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. If calendar invites are on for the account, assigned volunteers may get a new, updated or cancelled calendar invite by email (in test mode it goes to the owner instead).

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
Changes things 5Claude Code: ask
  • add_contactsAdd one or more volunteers to the roster in a single call.No findings

    Why it is in this group

    • The name "add_contacts" says "add": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • create_accountStart a new VolunteerReminder account for a human, using their email address.Reads text others writeNo findings

    Why it is in this group

    • The name "create_account" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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. Calling it again with the same email sends another verification email and creates no second account. 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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • create_scheduleCreate a recurring (or custom-date) schedule and materialize its upcoming occurrences.Reads text others writeNo findings

    Why it is in this group

    • The name "create_schedule" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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. If calendar invites are on for the account, assigned volunteers may get a new, updated or cancelled calendar invite by email (in test mode it goes to the owner instead).

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • import_volunteer_scheduleParse 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, s…Reads text others writeNo findings

    Why it is in this group

    • The name "import_volunteer_schedule" says "import": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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). If calendar invites are on for the account, assigned volunteers may get a new, updated or cancelled calendar invite by email (in test mode it goes to the owner instead).

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • start_checkoutGet 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.Reads text others writeNo findings

    Why it is in this group

    • The name "start_checkout" says "start": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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`).

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 10Show 10 read-only tools
  • get_account_overviewRead the current VolunteerReminder account: organization name, plan and entitlements, current reminder send mode, and volunteer usage vs the plan limit.No findings

    Why it is in this group

    • The name "get_account_overview" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_open_daysList 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.Reads private dataNo findings

    Why it is in this group

    • The name "get_open_days" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "calendar": it reads calendars.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_pricingRead 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 cre…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_pricing" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "message": it reads messages.
    • untrusted-inputThe description's first sentence says "read" and "message": it reads messages, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_reminder_settingsRead 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.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_reminder_settings" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "read" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_scheduleGet one schedule's full configuration: recurrence settings, job/role, group, roster (contact ids), start/end dates, and notes.Reads private dataNo findings

    Why it is in this group

    • The name "get_schedule" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "get" and "contact": it reads contacts.
    Description, as the server wrote it
    Get one schedule's full configuration: recurrence settings, job/role, group, roster (contact ids), start/end dates, and notes. Requires the `read` scope.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_send_historyRead recent reminder outcomes — which reminders were sent and which failed — newest first, paginated.No findings

    Why it is in this group

    • The name "get_send_history" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_upcoming_shiftsWho is volunteering when.No findings

    Why it is in this group

    • The name "get_upcoming_shifts" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_contactsList all volunteers on the account's roster, each with contact details and group.Reads private dataNo findings

    Why it is in this group

    • The name "list_contacts" says "list": a word for reading.

    What it can reach

    • private-dataThe name "list_contacts" says "list" and "contact": it reads contacts.
    • private-dataThe description's first sentence says "list" and "contact": it reads contacts.
    Description, as the server wrote it
    List all volunteers on the account's roster, each with contact details and group. Requires the `read` scope.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_schedulesList 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.No findings

    Why it is in this group

    • The name "list_schedules" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • preview_schedule_occurrencesPURE and side-effect-free: computes the next occurrence dates a recurrence configuration WOULD produce, without creating anything.No findings

    Why it is in this group

    • The name "preview_schedule_occurrences" says "preview": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

60 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data5
Reads files, mail, messages, databases, secrets, calendars or repositories.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__volunteerreminder__send_test_reminder"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:50 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
13
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.volunteerreminder.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://volunteerreminder.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 13 tools that change things (8 destructive, 5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.volunteerreminder.com/mcp: tools/list returned 23 tools to an anonymous client, including update_schedule (destructive), archive_schedule (destructive), update_contact (destructive), remove_contact (destructive), assign_contacts_to_schedule (destructive) and 8 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools9 changed.~9 changedView diff

Install

Pinned to version 0.3.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__volunteerreminder__get_account_overview",
      "mcp__volunteerreminder__list_schedules",
      "mcp__volunteerreminder__get_schedule",
      "mcp__volunteerreminder__preview_schedule_occurrences",
      "mcp__volunteerreminder__get_upcoming_shifts",
      "mcp__volunteerreminder__list_contacts",
      "mcp__volunteerreminder__get_open_days",
      "mcp__volunteerreminder__get_reminder_settings",
      "mcp__volunteerreminder__get_send_history",
      "mcp__volunteerreminder__get_pricing"
    ],
    "ask": [
      "mcp__volunteerreminder__create_schedule",
      "mcp__volunteerreminder__add_contacts",
      "mcp__volunteerreminder__import_volunteer_schedule",
      "mcp__volunteerreminder__create_account",
      "mcp__volunteerreminder__start_checkout"
    ],
    "deny": [
      "mcp__volunteerreminder__update_schedule",
      "mcp__volunteerreminder__archive_schedule",
      "mcp__volunteerreminder__update_contact",
      "mcp__volunteerreminder__remove_contact",
      "mcp__volunteerreminder__assign_contacts_to_schedule",
      "mcp__volunteerreminder__set_reminder_rule",
      "mcp__volunteerreminder__remove_reminder_rule",
      "mcp__volunteerreminder__send_test_reminder"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as volunteerreminder. Review it before you use it.

Capability tags behind 15 rules
  • mcp__volunteerreminder__get_schedule private-data
  • mcp__volunteerreminder__create_schedule untrusted-input
  • mcp__volunteerreminder__update_schedule untrusted-input
  • mcp__volunteerreminder__archive_schedule untrusted-input
  • mcp__volunteerreminder__list_contacts private-data
  • mcp__volunteerreminder__update_contact untrusted-input
  • mcp__volunteerreminder__remove_contact untrusted-input
  • mcp__volunteerreminder__assign_contacts_to_schedule untrusted-input
  • mcp__volunteerreminder__import_volunteer_schedule untrusted-input
  • mcp__volunteerreminder__get_open_days private-data
  • mcp__volunteerreminder__get_reminder_settings private-data, untrusted-input
  • mcp__volunteerreminder__send_test_reminder untrusted-input, outbound
  • mcp__volunteerreminder__get_pricing private-data, untrusted-input
  • mcp__volunteerreminder__create_account untrusted-input
  • mcp__volunteerreminder__start_checkout untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.volunteerreminder/mcp/verify?hash=1e5dfc991dbc868d836b07770fb5aa00042649e386433617e946bb3e82674e0a" | jq -e '.changed == false'

Pinned hash 1e5dfc991dbc, from Nov 11, 2026, 05:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.volunteerreminder/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.volunteerreminder/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/com.volunteerreminder/mcp.svg)](https://radar.anlyon.com/servers/com.volunteerreminder/mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:10 UTC.

VolunteerReminder MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the VolunteerReminder MCP server safe?

No scan can promise that. What its definitions show: 23 tools, 13 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the VolunteerReminder MCP server delete data?

Yes. 8 tools can delete, cancel or revoke something: update_schedule, archive_schedule, update_contact, remove_contact, assign_contacts_to_schedule, set_reminder_rule and 2 more.

Can the VolunteerReminder MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the VolunteerReminder MCP server have?

23 tools: 8 destructive, 5 write, 10 read. update_schedule, archive_schedule, update_contact, remove_contact, assign_contacts_to_schedule, set_reminder_rule, remove_reminder_rule, send_test_reminder and 15 more.

Does the VolunteerReminder MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the VolunteerReminder MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_test_reminder.

Has the VolunteerReminder MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.