unremind-me-submit

endpoint

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

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is unremind-me-submit live?

Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is unremind-me-submit free to use?

Yes — the hub reached it with no key and no payment.

What tools does unremind-me-submit have?

2 tools: submit_unreminder, get_submission_guidance.

Is unremind-me-submit safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

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_submission_guidance reads open 1h ago

  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.

  mcp-tool

  12345

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

  arguments 5 lines copy
• submit_unreminder sends messages unknown never probed

  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.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445

  {
    "type": "object",
    "required": [
      "username",
      "title"
    ],
    "properties": {
      "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."
      },
      "title": {
        "type": "string",
        "maxLength": 300,
        "minLength": 1,
        "description": "Short and action-oriented, e.g. 'Send the signed lease back'. This is what the recipient sees first."
      },
      "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."
      },
      "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."
      },
      "username": {
        "type": "string",
        "description": "The recipient's UnRemind.me username — the last part of their page URL, e.g. 'johndoe' for unremind.me/johndoe."
      },
      "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."
      },
      "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."
      }
    },
    "additionalProperties": false
  }

  arguments 45 lines copy

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

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.