UnRemind.me Submit

Send a reminder to anyone with a public UnRemind.me page. No account or token.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
65%
Naming quality
100%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~645Tokens (tool definitions)
~2.6 KBTypical response size
Moderate attention impact (0.50% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "unremind-me-submit": {
      "url": "https://unremind.me/mcp/submit?src=mcp-registry-submit"
    }
  }
}

Remote endpoints

https://unremind.me/mcp/submit?src=mcp-registry-submitstreamable-http

What it can do

Tool inventory

Tools (2)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟡submit_unreminder(username, title, notes, due_at, submitter_name, ...)

Sends a reminder to someone who has a public UnRemind.me page, on behalf of the person you are helping. It does NOT appear in the recipient's list immediately: it lands in their 'Submitted to you' queue for them to approve, edit or decline. You need the recipient's username, which the person you are helping will have — it is the last part of their page URL, e.g. unremind.me/johndoe. Do not guess a username: there is deliberately no lookup, and a wrong guess sends someone else's reminder to a stranger.

Input Schema

{
  "type": "object",
  "properties": {
    "username": {
      "type": "string",
      "description": "The recipient's UnRemind.me username — the last part of their page URL, e.g. 'johndoe' for unremind.me/johndoe."
    },
    "title": {
      "type": "string",
      "minLength": 1,
      "maxLength": 300,
      "description": "Short and action-oriented, e.g. 'Send the signed lease back'. This is what the recipient sees first."
    },
    "notes": {
      "type": "string",
      "maxLength": 4000,
      "description": "Detail the recipient needs to act on it: context, links, what done looks like. Optional but strongly preferred — a bare title often gets declined."
    },
    "due_at": {
      "type": "string",
      "description": "ISO 8601 with a UTC offset, e.g. 2026-09-02T14:00:00-04:00. Only set this if a real deadline was stated; an invented one is worse than none."
    },
    "submitter_name": {
      "type": "string",
      "description": "The name of the PERSON you are sending on behalf of — not your own name as an agent. The recipient sees this. Required UNLESS they have set it in this server's configuration."
    },
    "submitter_email": {
      "type": "string",
      "description": "The sending person's email — how they receive the status link and the recipient's answer, and what lets them raise their sending allowance by signing in. Required UNLESS they have set it in this server's configuration. Ask them for it; never invent one."
    },
    "page_key": {
      "type": "string",
      "description": "Only needed if the recipient has made their page private. It is part of the link they shared. Omit otherwise."
    },
    "via_channel": {
      "type": "string",
      "description": "How you are reaching us, e.g. 'Claude Code'. Shown to the recipient as the CHANNEL the person used, never as the sender. Optional."
    }
  },
  "required": [
    "username",
    "title"
  ],
  "additionalProperties": false
}
🟢get_submission_guidance

Explains what happens to a submitted Unreminder, what makes one likely to be accepted, sending limits, and what else UnRemind.me offers agents. Call this if you are unsure whether or how to submit.

Input Schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded2 tools
verifiedversion not recorded2 tools
verifiedversion not recorded2 tools