# ai.radmail/radmail-mcp (remote · radmail.ai)

Email OS for agents - real-inbox search, triage, commitments, and a verifiable BEC hard-stop.

- Trust score: 66/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `radmail.ai`: 66/100 (this document), [markdown](https://verifymcp.io/servers/ai-radmail-radmail-mcp/api-mcp-sandbox.md), [page](https://verifymcp.io/servers/ai-radmail-radmail-mcp/api-mcp-sandbox)
- npm · `radmail-mcp`: 65/100, [markdown](https://verifymcp.io/servers/ai-radmail-radmail-mcp/radmail-mcp.md), [page](https://verifymcp.io/servers/ai-radmail-radmail-mcp/radmail-mcp)

## Channel facts

- Endpoint: `https://radmail.ai/api/mcp/sandbox`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.2`

## 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-08-03.

- **Endpoint Security**: 63/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 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 632 tokens (~105/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ai-radmail-radmail-mcp https://radmail.ai/api/mcp/sandbox
```

### Codex

```toml
[mcp_servers.ai-radmail-radmail-mcp]
url = "https://radmail.ai/api/mcp/sandbox"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-radmail-radmail-mcp": {
      "type": "remote",
      "url": "https://radmail.ai/api/mcp/sandbox",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-radmail-radmail-mcp --url https://radmail.ai/api/mcp/sandbox --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-radmail-radmail-mcp:
    url: "https://radmail.ai/api/mcp/sandbox"
```

### Other

```json
{
  "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.

## 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-08-02 (score 66, +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.

### 2026-07-31 (score 65, +1)

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

### 2026-07-30 (score 64, −2)

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

### 2026-07-29 (score 66, +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.

### 2026-07-28 (score 65, +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.

### 2026-07-27 (score 64, 0)

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

### 2026-07-26 (score 64)

First indexed and scored.

## MCP tools (6)

### `triage_inbox` (~72 tokens)

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.

### `list_right_now` (~31 tokens)

Return only the 'Right Now' lane — the most recent and most important messages that genuinely can't be missed.

### `why_surfaced` (~56 tokens)

Explain in plain English why a given message was surfaced — the signals (sender, urgency, commitment) behind its rank.

Input parameters:

- `message_id` (string, required): An id from triage_inbox, e.g. m_001.

### `list_commitments` (~33 tokens)

Extract the open commitments in the correspondence, both owed by you and owed to you, with who and by-when.

### `draft_reply` (~70 tokens)

Draft a reply for a thread. It returns text for a human to review — it does not and cannot send it.

Input parameters:

- `guidance` (string): Optional steer for the draft. Never sent — review-only.
- `message_id` (string, required): An id from triage_inbox to draft a reply for.

### `search` (~141 tokens)

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.

Input parameters:

- `limit` (number): Max hits to return (default 10).
- `query` (string, required): Words to find, matched against from / subject / body. Every word must appear somewhere in a message.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-radmail-radmail-mcp/api-mcp-sandbox#diagnostics

## Score history

- 2026-08-03: 66
- 2026-08-02: 66
- 2026-08-01: 65
- 2026-07-31: 65
- 2026-07-30: 64
- 2026-07-29: 66
- 2026-07-28: 65
- 2026-07-27: 64
- 2026-07-26: 64

## Links

- Remote endpoint: https://radmail.ai/api/mcp/sandbox
- Repository: https://github.com/dougsureel-tech/radmail-mcp
- Website: https://radmail.ai/for-agents
- Changelog RSS feed: https://verifymcp.io/servers/ai-radmail-radmail-mcp/api-mcp-sandbox/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-radmail-radmail-mcp/api-mcp-sandbox/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-radmail-radmail-mcp/api-mcp-sandbox