Servidor MCP de VolunteerReminder

• Nombre en el registrocom.volunteerreminder/mcpverificado en el registro MCP

El nombre en el registro está bajo volunteerreminder.com. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-19
• Herramientas23
• El servidor se llamavolunteerreminder
• Versión del servidor0.3.0
• Versión del protocolo2025-06-18

El 2026-10-19 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 342 ms.

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
• Comprobado 2 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 2 hasta ahora
• Respondiómidiendo2 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta482 ms
• Espacio en el contexto del agente≈ 7884 tokenslas definiciones de todas sus herramientas (23), que el agente lleva en cada turno
• Definiciones de herramientasA · 100 de 100

• Todas las herramientas pasan las seis comprobaciones.

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (30%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%) y uso (15%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• 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…

• 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.

• 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.

• 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…

• 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…

• 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…

• 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…

• 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…

• list_contacts

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

• 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…

• 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.

• 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.

• 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…

• 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…

• 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_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…

• 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.

• 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…

• 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…

• 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…

• 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…

• 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…