ai.radmail/radmail-mcp
REMOTE · RADMAIL.AI · 2 COMPONENTS · SCANNED AUG 3
Email OS for agents - real-inbox search, triage, commitments, and a verifiable BEC hard-stop.
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 →
Endpoint Security63
- 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 6 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 632 tokens (~105/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · radmail.ai
claude mcp add --transport http ai-radmail-radmail-mcp https://radmail.ai/api/mcp/sandbox
[mcp_servers.ai-radmail-radmail-mcp] url = "https://radmail.ai/api/mcp/sandbox"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-radmail-radmail-mcp": {
"type": "remote",
"url": "https://radmail.ai/api/mcp/sandbox",
"enabled": true
}
}
} openclaw mcp add ai-radmail-radmail-mcp --url https://radmail.ai/api/mcp/sandbox --transport streamable-http
mcp_servers:
ai-radmail-radmail-mcp:
url: "https://radmail.ai/api/mcp/sandbox" {
"mcpServers": {
"ai-radmail-radmail-mcp": {
"type": "http",
"url": "https://radmail.ai/api/mcp/sandbox"
}
}
} 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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +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.
- 27 Jul 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
- 26 Jul 26 64
First indexed and scored.
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 3 Aug 2026 · Probed https://radmail.ai/api/mcp/sandbox
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=radmail.ai | CN=YR2,O=Let's Encrypt,C=US | 29 Jun 2026 | 27 Sept 2026 | RSA 2048 | SHA256-RSA | 51aa1d743e01e82034d4b3eda04c932db19 |
| SANs: *.radmail.ai, radmail.ai | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of radmail.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| radmail.ai. | 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 |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), browsing-topics=() |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://radmail.ai/api/mcp/sandbox | Verified | 200 | |
| http (plaintext) | http://radmail.ai/api/mcp/sandbox | HTTPS enforced | 308 | https://radmail.ai/api/mcp/sandbox |
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.
draft_reply ~70
Draft a reply for a thread. It returns text for a human to review — it does not and cannot send it.
| Name | Type | Req | Description |
|---|---|---|---|
| guidance | string | — | Optional steer for the draft. Never sent — review-only. |
| message_id | string | yes | An id from triage_inbox to draft a reply for. |
No output schema declared.
No examples provided.
list_commitments ~33
Extract the open commitments in the correspondence, both owed by you and owed to you, with who and by-when.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_right_now ~31
Return only the 'Right Now' lane — the most recent and most important messages that genuinely can't be missed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search ~141
Find a specific message by sender, subject, or content. Results come back most-relevant + newest first, and every hit says where it matched (from / subject / body) and why. On this hosted sandbox it searches the built-in demo inbox; run the radmail-mcp package with RADMAIL_API_KEY set and the same tool searches your REAL ingested inbox read-only (with from / after / before filters) via the v1 search API.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Max hits to return (default 10). |
| query | string | yes | Words to find, matched against from / subject / body. Every word must appear somewhere in a message. |
No output schema declared.
No examples provided.
triage_inbox ~72
Rank a mailbox on two axes (importance x urgency) and return what needs a human now versus what can wait or is already handled — with each thread's open commitment (the promise you owe or are owed, and whether it's overdue) surfaced inline, so the follow-through is visible on the very first call.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
why_surfaced ~56
Explain in plain English why a given message was surfaced — the signals (sender, urgency, commitment) behind its rank.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | An id from triage_inbox, e.g. m_001. |
No output schema declared.
No examples provided.