UnRemind.me Submit
REMOTE · UNREMIND.ME · SCANNED SEP 27
Send a reminder to anyone with a public UnRemind.me page. No account or token.
Available components
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · unremind.me
claude mcp add --transport http esfih-unremind-me-submit 'https://unremind.me/mcp/submit?src=mcp-registry-submit'
{
"mcpServers": {
"esfih-unremind-me-submit": {
"url": "https://unremind.me/mcp/submit?src=mcp-registry-submit"
}
}
} {
"servers": {
"esfih-unremind-me-submit": {
"type": "http",
"url": "https://unremind.me/mcp/submit?src=mcp-registry-submit"
}
}
} [mcp_servers.esfih-unremind-me-submit] url = "https://unremind.me/mcp/submit?src=mcp-registry-submit"
{
"$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 mcp add esfih-unremind-me-submit --url 'https://unremind.me/mcp/submit?src=mcp-registry-submit' --transport streamable-http
mcp_servers:
esfih-unremind-me-submit:
url: "https://unremind.me/mcp/submit?src=mcp-registry-submit" {
"McpServers": {
"esfih-unremind-me-submit": {
"Transport": "http",
"Url": "https://unremind.me/mcp/submit?src=mcp-registry-submit"
}
}
} assistant mcp add esfih-unremind-me-submit -t streamable-http -u 'https://unremind.me/mcp/submit?src=mcp-registry-submit'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Sept 26 +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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +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.
- 22 Sept 26 +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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://unremind.me/mcp/submit?src=mcp-registry-submit
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=unremind.me | CN=WE1,O=Google Trust Services,C=US | 15 Aug 2026 | 13 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | ec765d44fbf4eac13c97f5bd2f83dc7 |
| SANs: unremind.me, *.unremind.me | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of unremind.me. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| me. | present | 45352 | 8 | Verified |
| unremind.me. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://unremind.me/mcp/submit?src=mcp-registry-submit | Verified | 200 | |
| http (plaintext) | http://unremind.me/mcp/submit?src=mcp-registry-submit | Inconclusive | 404 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_submission_guidance How submission works ~54
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 present but exposes no named parameters.
No output schema declared.
No examples provided.
submit_unreminder Send someone an Unreminder ~463
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Short and action-oriented, e.g. 'Send the signed lease back'. This is what the recipient sees first. |
| username | string | yes | 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. |
No output schema declared.
No examples provided.
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.