Skip to content
External endpointresponds

radmail-mcp

Email OS for agents: triage, search, and a verifiable BEC hard-stop. Zero-auth sandbox.

Endpoint URL
https://radmail.ai/api/mcp/sandbox
Current status
responds
Last checked
Aug 17, 2026, 05:06 AM UTC
Check
MCP initialize · 8s limit
Latency
206 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
ai.radmail/radmail-mcp

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
radmail-sandbox
Version
0.1.0
Capability keys
tools
Tool names
triage_inbox, list_right_now, why_surfaced, list_commitments, draft_reply, search
Instructions excerpt

RadMail is pre-release. The engine is live in a test bed on two real businesses today; the commercial multi-tenant product is launch-gated. The MCP sandbox you connect to is real and runnable now (heuristic, in-memory, free, no credentials), but it is the sandbox engine — not the production multi-tenant engine. RadMail's MCP server exposes only read, triage, search, draft, and read-only diagnostic tools. There is no tool that auto-sends money, changes banking details, or makes first contact with a new party — those stay human-only, forever, as a defense against business-email-compromise (BEC) fraud. An agent literally cannot use RadMail to do the dangerous thing. Compliance is a shared responsibility. RadMail is a tool that supports your program, not a compliance guarantee, and it does not by itself make any organization compliant. For regulated tiers RadMail signs a BAA and processes on BAA-covered, audited infrastructure. RadMail is not HIPAA-certified, FedRAMP-authorized, or S

Reported Aug 17, 2026, 05:06 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 97ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 910ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 160ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 206ms