_ registry / mcp streamable-http · checked 1h ago

volunteerreminder

https://mcp.volunteerreminder.com

Registry code: fb8d284fc11c8a8f

api record

VolunteerReminder sets up and sends automated shift reminders (email + SMS) to

an organization's volunteers.

endpoint
https://mcp.volunteerreminder.com/mcp
protocol
streamable-http ·2025-06-18
authentication
bearer
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
402ms

last good check

priced tools
0

of 23 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 23 tools
23 auth-required 23 of 23 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_account_overview auth-required 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_open_days auth-required 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "months": {
      "type": "integer",
      "maximum": 24,
      "minimum": 1,
      "description": "How many months to look ahead (1–24). Default 12."
    },
    "current_year_only": {
      "type": "boolean",
      "description": "When true (the default), clamp the window to the end of the current calendar year instead of crossing into next year."
    }
  }
}
    arguments 16 lines
  • update_schedule auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "schedule_id"
  ],
  "properties": {
    "time": {
      "anyOf": [
        {
          "type": "string",
          "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$"
        },
        {
          "type": "null"
        }
      ],
      "description": "Wall-clock time of day \"HH:mm\" (24-hour) in the account timezone, or null for no specific time."
    },
    "notes": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "description": "New notes, or null to clear."
    },
    "end_date": {
      "anyOf": [
        {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
        },
        {
          "type": "null"
        }
      ],
      "description": "\"yyyy-MM-dd\" (account timezone) after which occurrences stop, or null for no end date."
    },
    "group_id": {
      "anyOf": [
        {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": -9007199254740991
        },
        {
          "type": "null"
        }
      ],
      "description": "New group id, or null to detach. Unknown ids are ignored."
    },
    "job_name": {
      "type": "string",
      "minLength": 1,
      "description": "New job/role name."
    },
    "start_date": {
      "anyOf": [
        {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
        },
        {
          "type": "null"
        }
      ],
      "description": "\"yyyy-MM-dd\" (account timezone) before which no occurrences materialize, or null for no lower bound."
    },
    "description": {
      "type": "string",
      "minLength": 1,
      "description": "New schedule label."
    },
    "nth_weekday": {
      "enum": [
        "sunday",
        "monday",
        "tuesday",
        "wednesday",
        "thursday",
        "friday",
        "saturday"
      ],
      "type": "string",
      "description": "The weekday that recurs, for schedule_type 'monthly_nth'/'bimonthly_nth'. Defaults to sunday for those types."
    },
    "schedule_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "The schedule's numeric id (from list_schedules or get_schedule).",
      "exclusiveMinimum": 0
    },
    "start_month": {
      "type": "integer",
      "maximum": 12,
      "minimum": 1,
      "description": "Anchor month (1=January … 12=December) the every-other-month cadence steps from, for the 'bimonthly_*' types. Defaults to the account's current month."
    },
    "custom_dates": {
      "type": "array",
      "items": {
        "type": "string",
        "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
      },
      "description": "Explicit list of \"yyyy-MM-dd\" dates. Required (non-empty) when schedule_type is 'custom'; ignored otherwise."
    },
    "day_of_month": {
      "type": "integer",
      "maximum": 31,
      "minimum": 1,
      "description": "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": {
      "type": "array",
      "items": {
        "enum": [
          "sunday",
          "monday",
          "tuesday",
          "wednesday",
          "thursday",
          "friday",
          "saturday"
        ],
        "type": "string"
      },
      "description": "Weekday names this recurs on, e.g. [\"tuesday\",\"thursday\"]. Required (non-empty) when schedule_type is 'weekly'; ignored otherwise."
    },
    "schedule_type": {
      "enum": [
        "weekly",
        "monthly_fixed",
        "monthly_nth",
        "bimonthly_fixed",
        "bimonthly_nth",
        "custom"
      ],
      "type": "string",
      "description": "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 month; the 'bimonthly_*' variants also alternate months starting from start_month; 'custom' uses an explicit list of dates."
    },
    "week_of_month": {
      "type": "integer",
      "maximum": 5,
      "minimum": 1,
      "description": "Which occurrence of the weekday in the month (1st–5th), for the Nth-weekday types. Defaults to 1."
    }
  }
}
    arguments 152 lines
  • get_schedule auth-required never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "schedule_id"
  ],
  "properties": {
    "schedule_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "The schedule's numeric id (from list_schedules or get_schedule).",
      "exclusiveMinimum": 0
    }
  }
}
    arguments 15 lines
  • preview_schedule_occurrences auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "schedule_type"
  ],
  "properties": {
    "time": {
      "anyOf": [
        {
          "type": "string",
          "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$"
        },
        {
          "type": "null"
        }
      ],
      "description": "Wall-clock time of day \"HH:mm\" (24-hour) in the account timezone, or null for no specific time."
    },
    "count": {
      "type": "integer",
      "maximum": 52,
      "minimum": 1,
      "description": "How many upcoming occurrences to return (default 8, max 52)."
    },
    "end_date": {
      "anyOf": [
        {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
        },
        {
          "type": "null"
        }
      ],
      "description": "\"yyyy-MM-dd\" (account timezone) after which occurrences stop, or null for no end date."
    },
    "start_date": {
      "anyOf": [
        {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
        },
        {
          "type": "null"
        }
      ],
      "description": "\"yyyy-MM-dd\" (account timezone) before which no occurrences materialize, or null for no lower bound."
    },
    "nth_weekday": {
      "enum": [
        "sunday",
        "monday",
        "tuesday",
        "wednesday",
        "thursday",
        "friday",
        "saturday"
      ],
      "type": "string",
      "description": "The weekday that recurs, for schedule_type 'monthly_nth'/'bimonthly_nth'. Defaults to sunday for those types."
    },
    "start_month": {
      "type": "integer",
      "maximum": 12,
      "minimum": 1,
      "description": "Anchor month (1=January … 12=December) the every-other-month cadence steps from, for the 'bimonthly_*' types. Defaults to the account's current month."
    },
    "custom_dates": {
      "type": "array",
      "items": {
        "type": "string",
        "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
      },
      "description": "Explicit list of \"yyyy-MM-dd\" dates. Required (non-empty) when schedule_type is 'custom'; ignored otherwise."
    },
    "day_of_month": {
      "type": "integer",
      "maximum": 31,
      "minimum": 1,
      "description": "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": {
      "type": "array",
      "items": {
        "enum": [
          "sunday",
          "monday",
          "tuesday",
          "wednesday",
          "thursday",
          "friday",
          "saturday"
        ],
        "type": "string"
      },
      "description": "Weekday names this recurs on, e.g. [\"tuesday\",\"thursday\"]. Required (non-empty) when schedule_type is 'weekly'; ignored otherwise."
    },
    "schedule_type": {
      "enum": [
        "weekly",
        "monthly_fixed",
        "monthly_nth",
        "bimonthly_fixed",
        "bimonthly_nth",
        "custom"
      ],
      "type": "string",
      "description": "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 month; the 'bimonthly_*' variants also alternate months starting from start_month; 'custom' uses an explicit list of dates."
    },
    "week_of_month": {
      "type": "integer",
      "maximum": 5,
      "minimum": 1,
      "description": "Which occurrence of the weekday in the month (1st–5th), for the Nth-weekday types. Defaults to 1."
    }
  }
}
    arguments 118 lines
  • get_upcoming_shifts auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "schedule_id"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "End of the range, same formats as `from`. Defaults to 90 days from now."
    },
    "from": {
      "type": "string",
      "description": "Start of the range: \"yyyy-MM-dd\" (account timezone) or a full ISO 8601 datetime. Defaults to now."
    },
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Maximum shifts to return (default 20, max 100)."
    },
    "schedule_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "The schedule's numeric id (from list_schedules or get_schedule).",
      "exclusiveMinimum": 0
    }
  }
}
    arguments 29 lines
  • create_schedule auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "description",
    "job_name",
    "schedule_type"
  ],
  "properties": {
    "time": {
      "anyOf": [
        {
          "type": "string",
          "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$"
        },
        {
          "type": "null"
        }
      ],
      "description": "Wall-clock time of day \"HH:mm\" (24-hour) in the account timezone, or null for no specific time."
    },
    "notes": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "description": "Free-text internal notes, or null."
    },
    "end_date": {
      "anyOf": [
        {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
        },
        {
          "type": "null"
        }
      ],
      "description": "\"yyyy-MM-dd\" (account timezone) after which occurrences stop, or null for no end date."
    },
    "group_id": {
      "anyOf": [
        {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": -9007199254740991
        },
        {
          "type": "null"
        }
      ],
      "description": "Id of an existing volunteer group to attach, or null. Unknown ids are ignored."
    },
    "job_name": {
      "type": "string",
      "minLength": 1,
      "description": "The role/task volunteers are reminded about. Matched case-insensitively against the account's existing jobs and created if new."
    },
    "start_date": {
      "anyOf": [
        {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
        },
        {
          "type": "null"
        }
      ],
      "description": "\"yyyy-MM-dd\" (account timezone) before which no occurrences materialize, or null for no lower bound."
    },
    "contact_ids": {
      "type": "array",
      "items": {
        "type": "integer",
        "maximum": 9007199254740991,
        "minimum": -9007199254740991
      },
      "description": "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."
    },
    "description": {
      "type": "string",
      "minLength": 1,
      "description": "Short label shown on the schedule list and in reminders, e.g. \"Sunday greeters\"."
    },
    "nth_weekday": {
      "enum": [
        "sunday",
        "monday",
        "tuesday",
        "wednesday",
        "thursday",
        "friday",
        "saturday"
      ],
      "type": "string",
      "description": "The weekday that recurs, for schedule_type 'monthly_nth'/'bimonthly_nth'. Defaults to sunday for those types."
    },
    "start_month": {
      "type": "integer",
      "maximum": 12,
      "minimum": 1,
      "description": "Anchor month (1=January … 12=December) the every-other-month cadence steps from, for the 'bimonthly_*' types. Defaults to the account's current month."
    },
    "custom_dates": {
      "type": "array",
      "items": {
        "type": "string",
        "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
      },
      "description": "Explicit list of \"yyyy-MM-dd\" dates. Required (non-empty) when schedule_type is 'custom'; ignored otherwise."
    },
    "day_of_month": {
      "type": "integer",
      "maximum": 31,
      "minimum": 1,
      "description": "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": {
      "type": "array",
      "items": {
        "enum": [
          "sunday",
          "monday",
          "tuesday",
          "wednesday",
          "thursday",
          "friday",
          "saturday"
        ],
        "type": "string"
      },
      "description": "Weekday names this recurs on, e.g. [\"tuesday\",\"thursday\"]. Required (non-empty) when schedule_type is 'weekly'; ignored otherwise."
    },
    "schedule_type": {
      "enum": [
        "weekly",
        "monthly_fixed",
        "monthly_nth",
        "bimonthly_fixed",
        "bimonthly_nth",
        "custom"
      ],
      "type": "string",
      "description": "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 month; the 'bimonthly_*' variants also alternate months starting from start_month; 'custom' uses an explicit list of dates."
    },
    "week_of_month": {
      "type": "integer",
      "maximum": 5,
      "minimum": 1,
      "description": "Which occurrence of the weekday in the month (1st–5th), for the Nth-weekday types. Defaults to 1."
    }
  }
}
    arguments 157 lines
  • add_contacts auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "contacts"
  ],
  "properties": {
    "contacts": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "full_name"
        ],
        "properties": {
          "notes": {
            "anyOf": [
              {
                "type": "string",
                "maxLength": 2000
              },
              {
                "type": "null"
              }
            ],
            "description": "Free-text notes about the contact, or null."
          },
          "group_id": {
            "anyOf": [
              {
                "type": "integer",
                "maximum": 9007199254740991,
                "exclusiveMinimum": 0
              },
              {
                "type": "null"
              }
            ],
            "description": "Id of an existing group on this account to file the contact under, or null."
          },
          "full_name": {
            "type": "string",
            "maxLength": 200,
            "minLength": 1,
            "description": "Display name, shown on the roster and in reminder text. Required."
          },
          "last_name": {
            "anyOf": [
              {
                "type": "string",
                "maxLength": 120
              },
              {
                "type": "null"
              }
            ],
            "description": "Last name, or null."
          },
          "first_name": {
            "anyOf": [
              {
                "type": "string",
                "maxLength": 120
              },
              {
                "type": "null"
              }
            ],
            "description": "First name, or null."
          },
          "land_phone": {
            "anyOf": [
              {
                "type": "string",
                "maxLength": 32
              },
              {
                "type": "null"
              }
            ],
            "description": "Landline number (informational only, never texted), or null."
          },
          "mobile_phone": {
            "anyOf": [
              {
                "type": "string",
                "maxLength": 32
              },
              {
                "type": "null"
              }
            ],
            "description": "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."
          },
          "email_address": {
            "anyOf": [
              {
                "type": "string",
                "format": "email",
                "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
                "maxLength": 320
              },
              {
                "type": "null"
              }
            ],
            "description": "Email address reminders may be sent to, or null."
          }
        }
      },
      "maxItems": 200,
      "minItems": 1,
      "description": "The volunteers to add (1–200 per call). Each needs at least a full_name."
    }
  }
}
    arguments 116 lines
  • update_contact auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "contact_id"
  ],
  "properties": {
    "notes": {
      "anyOf": [
        {
          "type": "string",
          "maxLength": 2000
        },
        {
          "type": "null"
        }
      ],
      "description": "Free-text notes about the contact, or null."
    },
    "group_id": {
      "anyOf": [
        {
          "type": "integer",
          "maximum": 9007199254740991,
          "exclusiveMinimum": 0
        },
        {
          "type": "null"
        }
      ],
      "description": "Id of an existing group on this account to file the contact under, or null."
    },
    "full_name": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "New display name."
    },
    "last_name": {
      "anyOf": [
        {
          "type": "string",
          "maxLength": 120
        },
        {
          "type": "null"
        }
      ],
      "description": "Last name, or null."
    },
    "contact_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "The contact's numeric id (from list_contacts).",
      "exclusiveMinimum": 0
    },
    "first_name": {
      "anyOf": [
        {
          "type": "string",
          "maxLength": 120
        },
        {
          "type": "null"
        }
      ],
      "description": "First name, or null."
    },
    "land_phone": {
      "anyOf": [
        {
          "type": "string",
          "maxLength": 32
        },
        {
          "type": "null"
        }
      ],
      "description": "Landline number (informational only, never texted), or null."
    },
    "mobile_phone": {
      "anyOf": [
        {
          "type": "string",
          "maxLength": 32
        },
        {
          "type": "null"
        }
      ],
      "description": "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."
    },
    "email_address": {
      "anyOf": [
        {
          "type": "string",
          "format": "email",
          "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
          "maxLength": 320
        },
        {
          "type": "null"
        }
      ],
      "description": "Email address reminders may be sent to, or null."
    }
  }
}
    arguments 108 lines
  • remove_contact auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "contact_id"
  ],
  "properties": {
    "contact_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "The contact's numeric id (from list_contacts).",
      "exclusiveMinimum": 0
    }
  }
}
    arguments 15 lines
  • assign_contacts_to_schedule auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "schedule_id",
    "contact_ids"
  ],
  "properties": {
    "contact_ids": {
      "type": "array",
      "items": {
        "type": "integer",
        "maximum": 9007199254740991,
        "exclusiveMinimum": 0
      },
      "maxItems": 500,
      "description": "The complete set of volunteer contact ids for this schedule (replaces any existing roster). Empty array clears the roster."
    },
    "schedule_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "The schedule to assign the roster to.",
      "exclusiveMinimum": 0
    }
  }
}
    arguments 26 lines
  • get_reminder_settings auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_send_history auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "page": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": 1,
      "description": "1-indexed page number. Default 1."
    },
    "per_page": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Rows per page (max 100). Default 20."
    }
  }
}
    arguments 18 lines
  • get_pricing auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • create_account auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "email"
  ],
  "properties": {
    "email": {
      "type": "string",
      "format": "email",
      "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
      "maxLength": 254,
      "description": "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": {
      "type": "string",
      "maxLength": 200,
      "description": "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 editable later."
    }
  }
}
    arguments 21 lines
  • start_checkout auth-required never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "plan"
  ],
  "properties": {
    "plan": {
      "enum": [
        "basic",
        "deluxe",
        "pro"
      ],
      "type": "string",
      "description": "The plan id to subscribe to (see get_pricing)."
    },
    "interval": {
      "enum": [
        "monthly",
        "annual"
      ],
      "type": "string",
      "description": "Billing interval. Defaults to monthly."
    }
  }
}
    arguments 26 lines
  • send_test_reminder auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "schedule_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "Preview the reminder for this schedule. Omit for a generic sample reminder.",
      "exclusiveMinimum": 0
    }
  }
}
    arguments 12 lines
  • list_contacts auth-required 1h ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • archive_schedule auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "schedule_id"
  ],
  "properties": {
    "schedule_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "The schedule's numeric id (from list_schedules or get_schedule).",
      "exclusiveMinimum": 0
    }
  }
}
    arguments 15 lines
  • list_schedules auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • import_volunteer_schedule auth-required never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "text"
  ],
  "properties": {
    "text": {
      "type": "string",
      "maxLength": 200000,
      "minLength": 1,
      "description": "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."
    },
    "confirm": {
      "type": "boolean",
      "description": "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 preview."
    },
    "preview_token": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1,
      "description": "Required when confirm=true. Copy the preview_token returned by the preceding confirm=false call for this exact roster text."
    },
    "consent_attested": {
      "type": "boolean",
      "description": "Required true on confirm=true when any contact has a phone number. Affirms the volunteers agreed to receive shift-reminder texts."
    }
  }
}
    arguments 29 lines
  • set_reminder_rule auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "require_sms": {
      "type": "boolean",
      "description": "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."
    },
    "job_override": {
      "type": "object",
      "required": [
        "job_id",
        "days_before",
        "hours_before",
        "minutes_before"
      ],
      "properties": {
        "job_id": {
          "type": "integer",
          "maximum": 9007199254740991,
          "description": "The job this override applies to (must belong to this account).",
          "exclusiveMinimum": 0
        },
        "days_before": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": 0,
          "description": "Whole days before the shift to send the reminder."
        },
        "hours_before": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": 0,
          "description": "Additional whole hours before the shift."
        },
        "minutes_before": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": 0,
          "description": "Additional whole minutes before the shift."
        }
      },
      "description": "Create or replace the lead-time override for one job."
    },
    "global_default": {
      "type": "object",
      "required": [
        "days_before",
        "hours_before",
        "minutes_before"
      ],
      "properties": {
        "days_before": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": 0,
          "description": "Whole days before the shift to send the reminder."
        },
        "hours_before": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": 0,
          "description": "Additional whole hours before the shift."
        },
        "minutes_before": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": 0,
          "description": "Additional whole minutes before the shift."
        }
      },
      "description": "Set (or replace) the account-wide default lead time."
    }
  }
}
    arguments 75 lines
  • remove_reminder_rule auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "job_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "Remove this job's lead-time override. Omit to clear the account-wide default.",
      "exclusiveMinimum": 0
    }
  }
}
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/fb8d284fc11c8a8f/badge.svg)](https://brick.blue/agent/fb8d284fc11c8a8f)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.