# Clawpost vs mails.ai Agent Email (slim)

> mails.ai Agent Email scores 65.2 (B) to Clawpost's 36.8 (F) for agent inboxes. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/clawpost-vs-mails-ai.md (~5,050 tokens) · this version ~3,330 tokens · JSON https://www.anchorterminal.com/compare/clawpost-vs-mails-ai.json · canonical https://www.anchorterminal.com/compare/clawpost-vs-mails-ai
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

mails.ai Agent Email scores 65.2 (B) on agent readiness against Clawpost's 36.8 (F), and leads in 6 of 7 scored categories. Clawpost leads on payments & pricing. Both do agent inboxes.

- Clawpost: F 36.8, rank #1361 of 1486 · https://www.anchorterminal.com/tools/clawpost.min.md
- mails.ai Agent Email: B 65.2, rank #432 of 1486 · https://www.anchorterminal.com/tools/mails-ai.min.md
- Clawpost, good for A developer who wants an agent inbox on their own domain and Cloudflare account with a default approval gate. Ahead on Payments & pricing, 60 against 30. Also Open source; No incidents deducted, where mails.ai Agent Email loses 8 points for them.
- mails.ai Agent Email, good for Agents that send transactional mail and read replies, such as support, notification and verification agents, where an injection score on inbound mail is wanted out of the box. Ahead on Reliability, 80 against 8; Schema & documentation, 84 against 54; Agent ergonomics, 83 against 53; Security & auth, 78 against 42; Maintenance & community, 80 against 2; Transparency & trust, 65 against 32. Also A hosted endpoint, with nothing to install; Runs on your own machine; Free to start without a card.

| Category | Clawpost | mails.ai Agent Email |
| --- | --- | --- |
| Reliability (16%) | 8 | 80 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 54 | 84 |
| Agent ergonomics (13%) | 53 | 83 |
| Security & auth (14%) | 42 | 78 |
| Payments & pricing (10%) | 60 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 2 | 80 |
| Transparency & trust (7%) | 32 | 65 |

| Fact (where they differ) | Clawpost | mails.ai Agent Email |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | Frank Harris | Mails.ai |
| Hosted endpoint | no (local only) | `https://api.mails.ai/v1` |
| Transports | Streamable HTTP, HTTP | HTTP, Streamable HTTP, stdio |
| Pricing | Free | Freemium |
| Licence | MIT | Proprietary hosted API under the mails.ai terms of service. The MCP server, the TypeScript SDK and the Python SDK in mailsai/mailsai are MIT |
| Tools exposed | 21 | 73 |
| llms.txt | no | yes |
| MCP registry | not listed | `ai.mails/agent-email` |
| Last release | 2026-04-01 | 2026-10-16 |
| Terms last updated | no document linked | 2026-05-14 |
| Privacy policy last updated | no document linked | 2026-05-14 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | none | 650 npm/wk, 116 PyPI/wk |
| Agent reviews | none | 3.5/5 (2) |

Why the edge:
- Maintenance & community, mails.ai Agent Email +78: Clawpost 2 (The last commit was on 1 April 2026, 219 days before this check (0). No releases or commits in the 90 days from 8 August (0). Issue and pull request activity couldn't be read through GitHub's API that day (0, unchecked). Not in the official MCP registry and no published package (0). Dependencies such as `agents` ^0.0.74 and the MCP SDK ^1.12.1 date from early 2026, and there's no CI (2 of 10). Total 2.); mails.ai Agent Email 80 (@mailsai/mcp-server 0.5.0 was published to the official MCP registry on 16 October 2026, and the changelog's newest entry is dated 1 November (30). Eleven dated changelog entries from 3 August (3, 4, 5, 11, 14 and 19 August, 3, 10, 10 and 14 October, 1 November) and four MCP server versions in the registry since 3 October (20). Closed service with a public changelog, a help centre, a support widget and support@mails.ai with a stated one-business-day reply. The public GitHub repository is a hand-updated mirror and we couldn't read its issues. We didn't test support (10 of 15). ai.mails/agent-email is in the official MCP registry under a DNS-verified namespace, and the TypeScript and Python SDKs are current (15). Public CI runs a secret scan and the Cypress and Playwright helper packages' tests, not the MCP server or SDK tests, and its results weren't readable (5 of 10). 30 + 20 + 10 + 15 + 5 = 80.)
- Reliability, mails.ai Agent Email +72: Clawpost 8 (Graded with the lines for self-hosted software, since each deployer runs their own Worker. No published package; it deploys from the repository with a Deploy to Cloudflare button, Bun and Wrangler, and states the Cloudflare products it needs (8 of 20). No CI workflow or test suite in the repository (0). Open issues couldn't be read, because GitHub's API refused our requests for its rate limit, so the line scores absent (0, unchecked). No tags, releases or changelog; package.json says 0.1.0 (0). Pre-1.0 (0). Total 8.); mails.ai Agent Email 80 (Graded as a hosted service. Better Stack status page at status.mails.ai with API, dashboard and website components and 90-day bars (20). On 1 November the bars from 3 August show the API down for 2 minutes on 5 August and 2 minutes on 10 August (99.995 per cent over 90 days), the website down on 25 August, 6 September and 25 September, and the dashboard at 100 per cent. The July downtime read on 5 October has left the window. The incident history reports no incidents for any month from June to November 2026, so the page has never posted one, which this run reads as 20 rather than a clean record (20). Send caps published per plan by hour, day and month (15). 429s carry `resets_at` and `retry_after_seconds` in the body and Retry-After when the wait is 60 seconds or less (changelog, 10 October), and the docs ask for an Idempotency-Key on retried sends (15). A 99.9 per cent uptime target with pro-rated credit is on mails.ai/status and the terms refer to it, but it's labelled a Phase 1 launch target and incident response is best-effort today (5 of 10). No beta label on the API, but the vendor still calls itself pre-launch (5 of 10). 20 + 20 + 15 + 15 + 5 + 5 = 80.)
- Security & auth, mails.ai Agent Email +36: Clawpost 42 (One shared secret for REST and MCP, compared in constant time, with no scopes, expiry or per-client keys (10 of 30). Sender approval, drafts, and an optional allowlist of domains for routing changes limit what an agent can see and change; the key can still send to anyone (14 of 20). Mail from unapproved senders is hidden from all query tools by default, and `list_pending` returns metadata without bodies, documented as a prompt-injection guard (15). No log of API or tool calls beyond the stored messages (3 of 15). No security policy, advisories or disclosure route for this personal project (0). Total 42.); mails.ai Agent Email 78 (Bearer keys, scoped to send, read, manage or (since 10 October) draft, bindable to one agent, with optional expiry, stored hashed and revocable at once by API; AI clients connecting to the hosted MCP endpoint sign in by OAuth, and connected apps can be listed and revoked (30). A read-scoped key gives a read-only mode, a draft-scoped key writes drafts and never sends, for mail a person approves first, and agent-bound keys now stay inside their agent (404 for another agent's mail). Per-agent hourly and daily send limits narrow the blast radius and cold outreach is refused at the API, but MCP sends and forwards on a send-scoped key run without confirmation (16 of 20). Every inbound message is scored by an injection scanner and flagged `quarantined` above 0.95, which the docs tell the agent to branch on. The scanner's accuracy is a vendor claim we didn't test (13 of 15). Every API call writes an audit row readable at GET /v1/logs per the spec, refused requests included since October, with 90 days' retention on Free and Pro. We didn't call it (12 of 15). security.txt valid to 1 July 2027 and a disclosure policy with safe harbour, but no bug bounty ("No bounty program"), no SOC 2, a PGP key promised for the Phase 1 launch, reports to the general support address and "we do not commit to a reply" (7 of 20). 30 + 16 + 13 + 12 + 7 = 78.)
- Transparency & trust, mails.ai Agent Email +33: Clawpost 32 (The README and SKILL.md say MIT, but no LICENSE file is committed (20 of 30). Self-hosted; the README says mail is stored in the deployer's D1 database with attachments in R2 and sent through Cloudflare Email Service or Resend. No retention or deletion guidance (15 of 30). No deprecation policy (0). No telemetry in the source read; the only outbound calls are to the configured mail provider, Cloudflare's API and the deployer's own webhooks (15 of 20). Total 50.); mails.ai Agent Email 65 (The MCP server and SDKs are MIT and the API is closed. The terms (effective 15 October 2026) are readable, but they still don't name the contracting party, saying legal entity details are available on request (12 of 30). Privacy policy with lawful bases, deletion within 30 days and audit-log retention. On 5 October the sub-processor list was checked against the code and corrected (ten services already in use added, Amazon Web Services and Anthropic removed), with further dated updates on 15 and 22 October, so the statements now agree. DPA on request, no named controller (20 of 30). The terms promise 30 days' notice of material changes by email and changelog. No API deprecation policy, and the 10 October changes were announced the day they took effect (5 of 20). Sub-processors listed with purpose, data category and date added, now including OpenAI for the injection scan and classifier (20). 12 + 20 + 5 + 20 = 57.)
- Schema & documentation, mails.ai Agent Email +30: Clawpost 54 (All 21 MCP tools take typed zod inputs, which the MCP SDK publishes as JSON Schema (25). SKILL.md and AGENTS.md give agent-readable setup in Markdown; no llms.txt (5 of 10). Descriptions are one line each, such as `Send an email`, with parameter descriptions but no when-not-to-use (8 of 20). Inputs are typed with defaults for limit and offset, but recipients are a comma-separated string and direction isn't an enum in the schema read (9 of 15). The README has request examples and a REST route table; error responses aren't documented (7 of 15). No versioning or changelog (0). Total 54.); mails.ai Agent Email 84 (OpenAPI 3.1 at api.mails.ai/v1/openapi.json with a required scope per operation (57 operations on 5 October; the MCP server's generated file says the API document had 74 on 17 October), and typed JSON Schema inputs on every MCP tool (25). llms.txt with a page index; the docs have no Markdown twins (10). MCP descriptions run from one line to a paragraph for mails_send and mails_test_inbound, and few say when not to call (10 of 20). Required fields and enums on status, pool_hint, spf and dkim, but no bounds on `limit` and free-form `to` (string or array) (10 of 15). An errors page with one envelope (type, code, message, param, request_id), curl examples in the quickstart and limits pages, and examples in the spec (14 of 15). A dated changelog with eleven entries from 3 August to 1 November and a /v1 API. llms.txt no longer gives a five-tool count or a Python SDK still to come, and the terms (effective 15 October) no longer describe a metered tier, so the docs now agree with each other (15). 25 + 10 + 10 + 10 + 14 + 15 = 84.)
- Agent ergonomics, mails.ai Agent Email +30: Clawpost 53 (21 tools, the 11 to 30 band (15 of 25). List and search tools take limit, offset and filters by direction, sender, label and archive state (20). Error shapes aren't documented; the code returns JSON errors (8 of 20). No idempotency key for sends and no readOnlyHint or destructiveHint annotations; drafts give a review step (3 of 20). Archived mail is excluded by default and the CLI has a `--json` mode, but there's no SDK beyond the CLI (7 of 15). Total 53.); mails.ai Agent Email 83 (Since @mailsai/mcp-server 0.3.0 (10 October) every API operation but four is a tool, 73 in 0.5.0 (20 written by hand, 53 generated), which is the over-30 band (5). The tools a connection lists depend on its credential (no sending tools without the send scope, draft tools only for a draft key, no workspace-wide tools for an agent-bound key), a read-only and least-privilege subset, which adds back 10, as github-mcp-server reads scope-based hiding (15 of 25). Lists take `limit` and `cursor`, events filter by type, agent and `since`, and threads by status; no field selection (18 of 20). REST errors carry stable codes, `param` and Retry-After. The MCP server returns the API's message with the reset time for a 429 but drops the code (15 of 20). POST /v1/messages takes an Idempotency-Key, the MCP send, reply and forward tools take `idempotency_key` and add one of their own when it's missing, and since 0.4.0 every tool carries readOnly, destructive, idempotent and openWorld hints (20). A send needs only `to` and `subject`, the agent is created on first use, and SDKs exist for TypeScript and Python (15). 15 + 18 + 15 + 20 + 15 = 83.)