# ReminderIt (remote · mcp.reminderit.com)

Schedule real phone-call reminders with WhatsApp follow-up — medication, wake-ups, family check-ins.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

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

## Channel facts

- Endpoint: `https://mcp.reminderit.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-10-04.

- **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 (update_reminder).
  - 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**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4314 tokens (~172/item across 25 items; 25 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 26 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 ReminderIt MCP server?

ReminderIt is a hosted endpoint at https://mcp.reminderit.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-reminderit-reminderit 'https://mcp.reminderit.com/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-reminderit-reminderit": {
      "type": "http",
      "url": "https://mcp.reminderit.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-10-02 (score 63, +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-10-01 (score 62, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_usage” rewrote its description, which is the text the model reads
- [security] Tool “resume_reminder” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 0.3.0 → 0.3.1

### 2026-09-30 (score 62)

First indexed and scored.

## MCP tools (25)

### `list_reminders` (~77 tokens)

List reminders

List every reminder on the account with its schedule, state and next call time.

    Start here for almost any request about existing reminders — it is the only way to
    discover reminder IDs, which every other reminder tool needs. Paused reminders show
    WHY they are paused (out_of_credit, destination_not_allowed, completed).

Output parameters:

- `result` (string)

### `get_reminder` (~95 tokens)

Get reminder details

Get the full configuration of one reminder as JSON.

    Use when you need detail that list_reminders omits — the exact spoken message,
    cron expression, skip dates, channel toggles, or voice override. Also use this to
    read current values before a partial update, so you don't overwrite settings.

    Args:
        reminder_id: Reminder ID from list_reminders.

Input parameters:

- `reminder_id` (string, required)

Output parameters:

- `result` (string)

### `list_upcoming` (~83 tokens)

List upcoming calls

Show the next scheduled calls across ALL reminders, in chronological order.

    Answers "what's coming up?" better than list_reminders, because it expands
    recurring rules into actual upcoming occurrences and merges them into one timeline.

    Args:
        limit: How many upcoming occurrences to return (1-50, default 10).

Input parameters:

- `limit` (integer)

Output parameters:

- `result` (string)

### `get_recent_calls` (~158 tokens)

Get call history

Show recent delivery history — what was actually called, sent, or missed.

    Use this to answer "did it call me?", "why didn't I get it?", or to confirm a
    reminder is really firing. Statuses: completed/answered = the person picked up;
    no-answer/busy = rang but nobody answered (a WhatsApp fallback usually follows);
    failed = the call could not be placed; blocked = suppressed before dialling (no
    credit, unsupported country, or a recipient who hasn't consented);
    sent/delivered/read = a WhatsApp or email fallback.

    Args:
        limit: Number of recent delivery records (1-50, default 10).

Input parameters:

- `limit` (integer)

Output parameters:

- `result` (string)

### `create_reminder` (~603 tokens)

Create reminder call

Schedule a new reminder phone call.

    This places REAL calls, so get the schedule right the first time: resolve the
    timezone via whoami, and read the result back to the user afterwards.

    Provide exactly one schedule: run_at (one-off), cron_expr, or interval_days.
    Leave the voice arguments empty to use the account's default voice.

    Args:
        title: Short label shown in the app, e.g. "Morning pills" (max 120 chars).
        message_text: Exactly what the voice says on the call, written as speech —
            "Time to take your blood pressure tablet." (max 600 chars). Avoid
            abbreviations and symbols that sound wrong when read aloud.
        type: "once" for a single call, "recurring" for a repeating schedule.
        timezone: IANA timezone the schedule is anchored to, e.g. "America/New_York".
        run_at: ISO 8601 local datetime for a one-off call. Required when type="once".
        cron_expr: Cron schedule for recurring calls, e.g. "0 8 * * 1-5" = weekdays 8am.
        interval_days: Repeat every N days (1-365). Simpler alternative to cron_expr.
        start_date: ISO date; the recurring series does not fire before this.
        end_date: ISO date; the series stops after this (e.g. end of a medication course).
        skip_dates: Local dates to skip, ["2026-08-12"] format — holidays, travel.
        recipient_id: Call a care-recipient (from list_recipients) instead of the
            account owner. The recipient must have consented.
        voice_id: Override the account voice for this reminder only (see list_voices).
        personality: Speaking style — "gentle", "cheerful", "professional", "energetic".
        language: BCP-47 language tag for the spoken message, e.g. "en-GB", "hi-IN".
        speaking_rate: Speech speed, 0.8 (slower) to 1.2 (faster). 1.0 is normal.
        whatsapp_fallback: Send the reminder on WhatsApp if the call isn't answered.
        email_fallback: Also email the reminder if the call isn't answered.…

Input parameters:

- `cron_expr`
- `email_fallback` (boolean)
- `end_date`
- `interval_days`
- `language`
- `message_text` (string, required)
- `personality`
- `recipient_id`
- `run_at`
- `skip_dates`
- `speaking_rate`
- `start_date`
- `timezone` (string, required)
- `title` (string, required)
- `type` (string, required)
- `voice_id`
- `whatsapp_fallback` (boolean)

Output parameters:

- `result` (string)

### `update_reminder` (~284 tokens)

Edit reminder

Edit a reminder's wording or schedule. Only the fields you pass are changed.

    Use for "move it to 7am", "say it differently", "stop after the 20th". To pause or
    resume, use pause_reminder / resume_reminder. To change the voice, use
    set_reminder_voice. To skip particular dates, use set_skip_dates.

    Args:
        reminder_id: Reminder to edit (from list_reminders).
        title: New short label.
        message_text: New spoken message (written as natural speech, max 600 chars).
        cron_expr: New cron schedule, e.g. "0 7 * * *" for daily 7am.
        interval_days: New "every N days" interval (1-365).
        run_at: New ISO 8601 datetime for a one-off reminder.
        timezone: New IANA timezone. Changing this moves every future call.
        start_date: New ISO start date for a recurring series.
        end_date: New ISO end date; the series stops after it.

Input parameters:

- `cron_expr`
- `end_date`
- `interval_days`
- `message_text`
- `reminder_id` (string, required)
- `run_at`
- `start_date`
- `timezone`
- `title`

Output parameters:

- `result` (string)

### `set_reminder_voice` (~224 tokens)

Set a reminder's voice

Give one reminder its own voice, overriding the account default.

    Use when a specific reminder should sound different — a calm, slower voice for
    medication; an energetic one for a workout; a different language for a relative.
    Call list_voices first to get valid voice IDs, and preview_voice if the user
    wants to hear it before committing. Other reminders are unaffected.

    Args:
        reminder_id: Reminder to restyle (from list_reminders).
        voice_id: Voice ID from list_voices.
        personality: "gentle", "cheerful", "professional", or "energetic".
        language: BCP-47 tag for the spoken message, e.g. "en-GB", "es-ES", "hi-IN".
        speaking_rate: 0.8 (slower, good for elderly listeners) to 1.2 (faster).

Input parameters:

- `language`
- `personality`
- `reminder_id` (string, required)
- `speaking_rate`
- `voice_id`

Output parameters:

- `result` (string)

### `clear_reminder_voice` (~48 tokens)

Reset a reminder's voice

Remove a reminder's custom voice so it uses the account default again.

    Args:
        reminder_id: Reminder whose voice override should be cleared.

Input parameters:

- `reminder_id` (string, required)

Output parameters:

- `result` (string)

### `set_reminder_channels` (~139 tokens)

Set missed-call fallbacks

Choose what happens when a reminder call isn't answered.

    The phone call itself is always attempted. These toggles control the follow-ups:
    WhatsApp is on by default, email is off. Note each delivered fallback also consumes
    one call from the account's quota.

    Args:
        reminder_id: Reminder to configure (from list_reminders).
        whatsapp_fallback: True to send a WhatsApp message when the call is missed.
        email_fallback: True to also email the reminder when the call is missed.

Input parameters:

- `email_fallback`
- `reminder_id` (string, required)
- `whatsapp_fallback`

Output parameters:

- `result` (string)

### `set_skip_dates` (~154 tokens)

Set skip dates

Set the specific dates a recurring reminder should NOT call.

    The right way to handle holidays, travel, or a pause of a few days — far better
    than deleting a reminder and rebuilding it. This REPLACES the existing skip list,
    so include dates the user still wants skipped (read them with get_reminder first).
    Pass an empty list to clear all skips.

    Args:
        reminder_id: Reminder to adjust (from list_reminders).
        skip_dates: Local dates in "YYYY-MM-DD" form, e.g. ["2026-08-12", "2026-08-13"].

Input parameters:

- `reminder_id` (string, required)
- `skip_dates` (array, required)

Output parameters:

- `result` (string)

### `pause_reminder` (~74 tokens)

Pause reminder

Pause a reminder so it stops calling, keeping all its settings intact.

    Prefer this over delete_reminder whenever the user might want it back — it is
    fully reversible with resume_reminder.

    Args:
        reminder_id: Reminder to pause (from list_reminders).

Input parameters:

- `reminder_id` (string, required)

Output parameters:

- `result` (string)

### `resume_reminder` (~85 tokens)

Resume reminder

Resume a paused reminder so it starts calling on its schedule again.

    If it was paused automatically for out_of_credit and the account still has no calls
    left, it will pause again at the next occurrence — check get_usage and tell the user.

    Args:
        reminder_id: Reminder to resume (from list_reminders).

Input parameters:

- `reminder_id` (string, required)

Output parameters:

- `result` (string)

### `skip_next_occurrence` (~77 tokens)

Skip next call

Skip only the next scheduled call, leaving the rest of the schedule untouched.

    Use for "not tomorrow, but keep it going after that". To skip particular calendar
    dates instead, use set_skip_dates.

    Args:
        reminder_id: Reminder whose next call should be skipped.

Input parameters:

- `reminder_id` (string, required)

Output parameters:

- `result` (string)

### `test_call` (~90 tokens)

Place a test call now

Place an immediate test call for a reminder so the user can hear it right now.

    The phone will ring within seconds — only do this when the user has asked to test,
    and never repeatedly. It consumes one call from their quota and does not change
    the schedule.

    Args:
        reminder_id: Reminder to test (from list_reminders).

Input parameters:

- `reminder_id` (string, required)

Output parameters:

- `result` (string)

### `delete_reminder` (~75 tokens)

Delete reminder

Permanently delete a reminder. This cannot be undone.

    Confirm with the user first, quoting the reminder's title and schedule. If they may
    want it later, use pause_reminder instead.

    Args:
        reminder_id: Reminder to delete (from list_reminders).

Input parameters:

- `reminder_id` (string, required)

Output parameters:

- `result` (string)

### `list_voices` (~77 tokens)

List voices

List the voices available on this account, with language, accent and tier.

    Call before set_voice_settings or set_reminder_voice to get valid voice IDs —
    never guess one. Voices marked premium may not be included in every plan; if the
    account's plan doesn't include one, calls fall back to a standard voice.

Output parameters:

- `result` (string)

### `get_voice_settings` (~47 tokens)

Get default voice

Show the account's default voice — the voice every reminder uses unless overridden.

    Read this before changing anything, so you can report what actually changed and
    leave unrelated settings alone.

Output parameters:

- `result` (string)

### `set_voice_settings` (~188 tokens)

Set default voice

Change the account's DEFAULT voice, affecting every reminder without an override.

    For a single reminder only, use set_reminder_voice instead. Get valid IDs from
    list_voices; preview_voice lets the user hear one first.

    Args:
        voice_id: Voice ID from list_voices.
        personality: "gentle", "cheerful", "professional", or "energetic".
        language: BCP-47 tag, e.g. "en-US", "en-GB", "hi-IN".
        speaking_rate: 0.8 (slower — often better for elderly listeners) to 1.2 (faster).
        greet_by_name: Whether calls open by greeting the user by name.

Input parameters:

- `greet_by_name`
- `language`
- `personality`
- `speaking_rate`
- `voice_id`

Output parameters:

- `result` (string)

### `preview_voice` (~187 tokens)

Preview a voice

Generate a short audio sample of a voice so the user can hear it before choosing.

    Returns a URL to the generated audio. Useful when a user is deciding between
    voices, or wants to check how their own reminder wording will sound.

    Args:
        voice_id: Voice ID from list_voices.
        text: Words to speak in the sample. Defaults to a standard demo line; pass the
            user's actual reminder message to preview exactly what they'll hear.
        personality: "gentle", "cheerful", "professional", or "energetic".
        language: BCP-47 tag, e.g. "en-GB".
        speaking_rate: 0.8 to 1.2.

Input parameters:

- `language`
- `personality` (string)
- `speaking_rate`
- `text`
- `voice_id` (string, required)

Output parameters:

- `result` (string)

### `whoami` (~149 tokens)

Get account details

Identify the connected ReminderIt account: who it is, their timezone, plan and quota.

    Two jobs. First, it is the connection check — call it when the user asks "am I
    connected?", "which account is this?", or when another tool returns an auth error,
    to confirm the API key is valid and see whose account it opens.

    Second, call it BEFORE creating or rescheduling a reminder: it returns the user's
    saved timezone, so you can schedule silently instead of asking. It also warns when
    the phone is unverified or the account is opted out — in either case no reminder can
    be delivered, so surface that before scheduling anything.

Output parameters:

- `result` (string)

### `get_usage` (~77 tokens)

Check call balance

Get remaining call quota, calls used, plan, and the current billing period.

    Check before creating several reminders or suggesting a test call, and whenever a
    delivery fails unexpectedly. One call OR one WhatsApp fallback each consume one
    unit from the same pool. When the balance is low or zero, tell the user plainly.

Output parameters:

- `result` (string)

### `list_recipients` (~74 tokens)

List people you remind

List care-recipients — other people this account can send reminders to.

    Needed to get the recipient_id for create_reminder. Consent status matters: only
    "confirmed" recipients receive calls; "pending" means they haven't accepted the
    verification call yet, so reminders to them will be blocked.

Output parameters:

- `result` (string)

### `add_recipient` (~155 tokens)

Add a person to remind

Add another person who can receive reminder calls, e.g. an elderly parent.

    ReminderIt immediately places a consent verification call to the number; reminders
    are only delivered after that person accepts. Only add someone the user genuinely
    has permission to call, and confirm the number digit by digit before submitting —
    a typo calls a stranger.

    Args:
        name: The person's name, used in the call greeting.
        phone: Their number in full E.164 format, e.g. "+447700900123".
        relationship: Optional label for the user's own reference, e.g. "Mother".

Input parameters:

- `name` (string, required)
- `phone` (string, required)
- `relationship` (string)

Output parameters:

- `result` (string)

### `resend_recipient_verification` (~87 tokens)

Resend consent call

Re-send the consent verification call to a recipient who hasn't confirmed yet.

    Use when list_recipients shows consent as pending and the person missed the first
    call. Don't repeat it more than necessary — each attempt rings their phone.

    Args:
        recipient_id: Recipient to re-verify (from list_recipients).

Input parameters:

- `recipient_id` (string, required)

Output parameters:

- `result` (string)

### `remove_recipient` (~60 tokens)

Remove a person

Remove a care-recipient from the account.

    Any reminders targeting them will stop being delivered. Confirm with the user first.

    Args:
        recipient_id: Recipient to remove (from list_recipients).

Input parameters:

- `recipient_id` (string, required)

Output parameters:

- `result` (string)

## Diagnostics

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

## Score history

- 2026-10-04: 63
- 2026-10-03: 63
- 2026-10-02: 63
- 2026-10-01: 62
- 2026-09-30: 62

## Common questions

### What is the ReminderIt MCP server?

ReminderIt is an MCP server listed in the public MCP registry as com.reminderit/reminderit. Schedule real phone-call reminders with WhatsApp follow-up, medication, wake-ups, family check-ins. This page covers its hosted endpoint (https://mcp.reminderit.com/mcp).

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

ReminderIt scores 63 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 ReminderIt MCP server expose?

ReminderIt exposes 25 tools: list_reminders, get_reminder, list_upcoming, get_recent_calls, create_reminder, and 20 more. Their descriptions and schemas cost roughly 3,367 tokens of context every time the server is loaded.

### Does the ReminderIt MCP server require authentication?

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

### Is the ReminderIt MCP server still maintained?

ReminderIt is still listed as active in the MCP registry. We last reached this channel on 4 October 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.reminderit.com/mcp
- Website: https://reminderit.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-reminderit-reminderit/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-reminderit-reminderit/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-reminderit-reminderit/mcp