# UnRemind.me Submit (remote · unremind.me)

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

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-27

## Components

- remote · `unremind.me`: 72/100 (this document), [markdown](https://verifymcp.io/servers/esfih-unremind-me-submit/mcp-submit.md), [page](https://verifymcp.io/servers/esfih-unremind-me-submit/mcp-submit)

## Channel facts

- Endpoint: `https://unremind.me/mcp/submit?src=mcp-registry-submit`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-09-27.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement.
  - 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**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 705 tokens (~235/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 97/100
  - Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the UnRemind.me Submit MCP server?

UnRemind.me Submit is a hosted endpoint at https://unremind.me/mcp/submit?src=mcp-registry-submit, 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 esfih-unremind-me-submit 'https://unremind.me/mcp/submit?src=mcp-registry-submit'
```

### Cursor

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

### VS Code

```json
{
  "servers": {
    "esfih-unremind-me-submit": {
      "type": "http",
      "url": "https://unremind.me/mcp/submit?src=mcp-registry-submit"
    }
  }
}
```

### Codex

```toml
[mcp_servers.esfih-unremind-me-submit]
url = "https://unremind.me/mcp/submit?src=mcp-registry-submit"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "esfih-unremind-me-submit": {
      "type": "remote",
      "url": "https://unremind.me/mcp/submit?src=mcp-registry-submit",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add esfih-unremind-me-submit --url 'https://unremind.me/mcp/submit?src=mcp-registry-submit' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  esfih-unremind-me-submit:
    url: "https://unremind.me/mcp/submit?src=mcp-registry-submit"
```

### Netclaw

```json
{
  "McpServers": {
    "esfih-unremind-me-submit": {
      "Transport": "http",
      "Url": "https://unremind.me/mcp/submit?src=mcp-registry-submit"
    }
  }
}
```

### Vellum

```bash
assistant mcp add esfih-unremind-me-submit -t streamable-http -u 'https://unremind.me/mcp/submit?src=mcp-registry-submit'
```

### Other

```json
{
  "mcpServers": {
    "esfih-unremind-me-submit": {
      "type": "http",
      "url": "https://unremind.me/mcp/submit?src=mcp-registry-submit"
    }
  }
}
```

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-09-26 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 71, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (2)

### `submit_unreminder` (~463 tokens)

Send someone an Unreminder

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 parameters:

- `due_at` (string): 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.
- `notes` (string): Detail the recipient needs to act on it: context, links, what done looks like. Optional but strongly preferred — a bare title often gets declined.
- `page_key` (string): Only needed if the recipient has made their page private. It is part of the link they shared. Omit otherwise.
- `submitter_email` (string): 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 serv…
- `submitter_name` (string): 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.
- `title` (string, required): Short and action-oriented, e.g. 'Send the signed lease back'. This is what the recipient sees first.
- `username` (string, required): The recipient's UnRemind.me username — the last part of their page URL, e.g. 'johndoe' for unremind.me/johndoe.
- `via_channel` (string): How you are reaching us, e.g. 'Claude Code'. Shown to the recipient as the CHANNEL the person used, never as the sender. Optional.

### `get_submission_guidance` (~54 tokens)

How submission works

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.

## Diagnostics

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

## Score history

- 2026-09-27: 72
- 2026-09-26: 72
- 2026-09-25: 71
- 2026-09-24: 71
- 2026-09-23: 70
- 2026-09-22: 70
- 2026-09-21: 69
- 2026-09-20: 69
- 2026-09-19: 68
- 2026-09-18: 68
- 2026-09-17: 67
- 2026-09-16: 67
- 2026-09-15: 67
- 2026-09-14: 66
- 2026-09-13: 66
- 2026-09-12: 65
- 2026-09-11: 65
- 2026-09-10: 64
- 2026-09-09: 64
- 2026-09-08: 63
- 2026-09-07: 63
- 2026-09-06: 62
- 2026-09-05: 62
- 2026-09-04: 61
- 2026-09-03: 61
- 2026-09-02: 60
- 2026-09-01: 60
- 2026-08-31: 60
- 2026-08-30: 59
- 2026-08-29: 59

## Common questions

### What is the UnRemind.me Submit MCP server?

UnRemind.me Submit is an MCP server listed in the public MCP registry as io.github.esfih/unremind-me-submit. Send a reminder to anyone with a public UnRemind.me page. No account or token. This page covers its hosted endpoint (https://unremind.me/mcp/submit?src=mcp-registry-submit).

### Is the UnRemind.me Submit MCP server safe to use?

UnRemind.me Submit scores 72 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 UnRemind.me Submit MCP server expose?

UnRemind.me Submit exposes 2 tools: submit_unreminder, get_submission_guidance. Their descriptions and schemas cost roughly 517 tokens of context every time the server is loaded.

### Does the UnRemind.me Submit MCP server require authentication?

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

### Is the UnRemind.me Submit MCP server still maintained?

UnRemind.me Submit is still listed as active in the MCP registry. We last reached this channel on 27 September 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://unremind.me/mcp/submit?src=mcp-registry-submit
- Repository: https://github.com/esfih/unremind-me-mcp
- Website: https://unremind.me/
- Changelog RSS feed: https://verifymcp.io/servers/esfih-unremind-me-submit/mcp-submit.xml
- Changelog JSON feed: https://verifymcp.io/servers/esfih-unremind-me-submit/mcp-submit.json
- HTML version of this page: https://verifymcp.io/servers/esfih-unremind-me-submit/mcp-submit