# MailPace vs Mailtrap Email API + MCP (slim)

> Mailtrap Email scores 66.8 (B) to MailPace's 58.4 (C) for sending email. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/mailpace-vs-mailtrap.md (~5,300 tokens) · this version ~3,180 tokens · JSON https://www.anchorterminal.com/compare/mailpace-vs-mailtrap.json · canonical https://www.anchorterminal.com/compare/mailpace-vs-mailtrap
- 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)

Mailtrap Email API + MCP scores 66.8 (B) on agent readiness against MailPace's 58.4 (C), and leads in 5 of 7 scored categories. MailPace leads on reliability and agent ergonomics. Both do sending email.

- MailPace: C 58.4, rank #750 of 1486 · https://www.anchorterminal.com/tools/mailpace.min.md
- Mailtrap Email API + MCP: B 66.8, rank #352 of 1486 · https://www.anchorterminal.com/tools/mailtrap.min.md
- MailPace, good for Low-volume transactional mail from EU-hosted infrastructure with idempotent sends and no tracking. Ahead on Reliability, 70 against 65; Agent ergonomics, 71 against 62.
- Mailtrap Email API + MCP, good for Teams that want sending, a test sandbox and inbound mail under one token, with public OpenAPI specs and a free plan. Ahead on Schema & documentation, 82 against 54; Security & auth, 60 against 50; Payments & pricing, 40 against 25; Maintenance & community, 93 against 65. Also A hosted endpoint, with nothing to install; Runs on your own machine; Free to start without a card.

| Category | MailPace | Mailtrap Email API + MCP |
| --- | --- | --- |
| Reliability (16%) | 70 | 65 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 54 | 82 |
| Agent ergonomics (13%) | 71 | 62 |
| Security & auth (14%) | 50 | 60 |
| Payments & pricing (10%) | 25 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 65 | 93 |
| Transparency & trust (7%) | 75 | 77 |

| Fact (where they differ) | MailPace | Mailtrap Email API + MCP |
| --- | --- | --- |
| Vendor | OhMySMTP Ltd | Mailtrap (Railsware) |
| Hosted endpoint | no (local only) | `https://send.api.mailtrap.io` |
| Transports | HTTP | HTTP, stdio |
| Pricing | Paid | Freemium |
| Licence | none | Proprietary service under Mailtrap's terms of service. The MCP server, the Node.js SDK and the CLI are MIT |
| Tools exposed | 12 | 130 |
| llms.txt | no | yes |
| MCP registry | not listed | `io.mailtrap/mcp` |
| Last release | 2026-10-22 | 2026-10-30 |
| Terms last updated | 2026-01-09 | 2026-09-24 |
| Privacy policy last updated | 2026-08-30 | 2026-09-24 |
| Terms restrict automated access | yes | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 1 stars, 207 npm/wk | 65 stars, 66k npm/wk, 21k PyPI/wk |
| Agent reviews | none | 3.3/5 (4) |

Why the edge:
- Schema & documentation, Mailtrap Email API + MCP +28: MailPace 54 (No OpenAPI or other machine-readable contract for the HTTPS API. The MCP server's 12 tools have typed zod inputs and output schemas, but that server isn't published yet, so partial credit (8 of 25). llms.txt answers 404 on mailpace.com and docs.mailpace.com, and no Markdown copies are served (0). The reference states what each endpoint does, and the introduction says when not to use it (transactional only, no batch, no static IPs) (12 of 20). Field tables give type, examples and required or optional, with enums for status, sort and direction and the 50-recipient cap in text (9 of 15). Examples in curl and six languages and a full table of error responses with messages, though several listed messages have a broken quote (`{"error:"...`) and the send reference says 30 MB where the home page says 25 MB (12 of 15). Version in the path with a promise that an old version runs until a published end-of-life date, and dated changelog posts (13 of 15). Total 54.); Mailtrap Email API + MCP 82 (Graded on the REST API and the MCP server. Ten public OpenAPI 3.1 specs in mailtrap/mailtrap-openapi, and JSON Schema inputs on every MCP tool (25). llms.txt, llms-full.txt and a Markdown copy of each docs page (10). MCP descriptions are mostly one line. A few say when to use the tool or note a quota, and few say when not to (12). Schemas set required fields, minItems and additionalProperties false, with `template_variables` left open (12). The specs carry curl and SDK samples and example error bodies, and errors are arrays of plain strings with no codes (11). Specs are versioned 2.0.0, the product changelog is dated and the MCP CHANGELOG follows semver, with no version in the send path (12).)
- Maintenance & community, Mailtrap Email API + MCP +28: MailPace 65 (Email Status API documented on 22 October 2026, and the MCP server rewritten as 2.0.0 on 4 November 2026, two days before this check (30). In the 90 days from 8 August, the Q3 changelog post of 31 August, the Email Status docs of 22 October, a mailpace-rails push on 17 October and the MCP rewrite, but only one changelog post (15 of 20). A closed service with email support. Three pull requests to the MCP repository from 2025 have no reply (8 of 15). Not in the official MCP registry (search for mailpace returned nothing on 6 November). The Node library was last pushed in October 2024 and Go in January 2024, while mailpace-rails is current (7 of 15). The MCP server gained CI with tests on 4 November; the older SDKs weren't checked for CI (5 of 10). Total 65.); Mailtrap Email API + MCP 93 (mailtrap-python v3.0.0 was tagged on 30 October 2026, mailtrap-nodejs v6.0.0 on 29 October, CLI v0.9.0 on 28 October and MCP 0.11.0 on 27 October (30). Since 3 August, MCP 0.7.0 to 0.11.0, Node SDK 4.9.0 to 6.0.0, Python SDK 2.7.0 to 3.0.0 and dated changelog entries up to 16 September (20). Pull requests on the MCP repository are merged within days and Dependabot updates land weekly. A community forum opened on 16 September. Issue reply times weren't visible (18). Listed in the official MCP registry as io.mailtrap/mcp at 0.11.0, published 27 October, and SDKs are current (15). CI runs lint, tests and build on the MCP repository and now on pull requests, with CodeQL on the Node SDK (10).)
- Payments & pricing, Mailtrap Email API + MCP +15: MailPace 25 (No x402, MPP or L402 (0). $10 a month for 10,000 emails and $1 per 1,000 after, loaded from Paddle on the pricing page and stated in the comparison pages' tables without login (20). A free plan of up to 100 emails a month is available only by emailing support, so it isn't self-serve (5 of 20). Signup, DKIM verification and payment happen in a browser (0). Total 25.); Mailtrap Email API + MCP 40 (No x402, MPP or L402 (0). Plan prices and overage per 1,000 emails ($1.00, $0.88, $0.55) published without login, including a Markdown pricing page (20). Free plan of 4,000 emails a month, and the vendor's page for agents says signup needs no credit card (20). A person signs up in a browser and creates the first API token by hand in the UI (0).)
- Security & auth, Mailtrap Email API + MCP +10: MailPace 50 (Per-domain server tokens that can only send from and read status for their domain, and an organisation token that creates, renames and revokes domain tokens through the Domains API. Tokens travel in headers only. The authentication page still tells users to contact support to regenerate a leaked token (25 of 30). No read-only token. A domain token can't touch other domains, and the unpublished MCP server has an optional recipient allowlist. No approval step on the hosted API (8 of 20). Inbound mail reaches the customer's webhook as untrusted content, and Email Status returns bounce text. The MCP README warns about prompt injection and suggests the allowlist (9 of 15). The dashboard keeps sent mail for 30 days; no log of API calls was found (6 of 15). No security.txt (404 on mailpace.com and app.mailpace.com), no disclosure policy, bug bounty, SOC 2 or ISO 27001. WebAuthn-only two-factor sign-in and Ed25519-signed webhooks are documented (2 of 20). Total 50.); Mailtrap Email API + MCP 60 (API tokens with permissions per resource, an expiry date (365 days by default), a reset with a 12-hour overlap and management through the API. The docs give header authentication only (28). Token permissions can limit an agent to chosen domains or sandboxes and the sandbox keeps test sends away from real recipients, but the MCP server has no read-only mode or confirmation step beyond its annotations (12). Inbound and sandbox message bodies are returned to the model, and no prompt-injection guidance was found in the MCP README or the docs (0). Email logs for 3 to 30 days by plan, the MCP server forwards the client identity in its User-Agent, and user audit logs are Enterprise only (8). ISO/IEC 27001:2022, a SOC 2 Type II report under NDA and regular penetration tests are stated. No security.txt, disclosure policy or bug bounty was found, and the trust centre refused our reader (12).)
- Agent ergonomics, MailPace +9: MailPace 71 (Responses are small, the send returns an id and status and Email Status returns one email (18 of 25). Only the domains list takes `limit`, `offset`, `sort` and `direction`; there is no endpoint to list or search sent mail (8 of 20). Errors are JSON with a human message and an HTTP status for each case in the documented table, with no stable error codes (14 of 20). `Idempotency-Key` on sends, kept 24 hours per token, and failed validations are not stored so they can be retried. The MCP server marks send as not idempotent and revoke as destructive (18 of 20). A send needs from, to, a subject and a body; official libraries for Node, Rails, Go and PHP transports and an SMTP route (13 of 15). Total 71.); Mailtrap Email API + MCP 62 (130 MCP tools registered at once in 0.11.0, with no toolsets, filtering or dynamic loading (5). List endpoints page by token and per_page or last_id, with search and filters on email logs, sandbox messages, campaigns and inbound threads (17). Errors are readable messages under documented status codes, without machine codes (13). No idempotency key found. All 130 tools are annotated, 55 with readOnlyHint, 45 with destructiveHint true and 30 with destructiveHint false, and none with idempotentHint (12). `DEFAULT_FROM_EMAIL` and `MAILTRAP_SANDBOX_ID` cut required fields, and there are official SDKs in eight languages plus a CLI (15).)
- Reliability, MailPace +5: MailPace 70 (Graded with the hosted lines. A public Upptime status page at status.mailpace.com, driven by the mailpace/status repository, with monitors for the application, SMTP, docs, blog and landing page and GitHub issues as incident reports (20). The 90 days from 8 August hold two incidents, an application outage on 22 September 2026 that the operator put down to an upstream provider returning 5xx (issue open for two minutes), and SMTP down on 2 November 2026 for about 35 minutes, which leaves SMTP at 99.65% for the week. Minor incidents only (20). No rate limit numbers are published; the docs say limits vary by organisation age, plan and history (0). A documented 429 with its message, no Retry-After or backoff guidance, and an `Idempotency-Key` on sends with written retry rules (10 of 15). The terms guarantee 99% monthly availability of the API and dashboard with a 5% credit per 30 minutes (10). The API is at v1 with no beta label (10). Total 70.); Mailtrap Email API + MCP 65 (Graded as a hosted service. Status page at status.mailtrap.info with monthly history by component, per the 8 October check (20). On 1 November its robots.txt answered 406 with an empty body, which this run treats as blocked, so the history wasn't re-read. Per the 8 October read, the sending outage of 1 hour 32 minutes on 1 August has left the 90-day window that starts on 3 August, leaving two incidents of about 6 minutes each on Email Testing (the sandbox) on 16 September. The window from 9 October to 1 November is unread and isn't credited, so the line stays at the 8 October award until the history can be read, as merge-accounting's and glean's incident lines were held when their status hosts refused us (10). Rate limits published with numbers, re-read on 1 November, 150 requests per 10 seconds per token and lower per-account limits on Contacts, Stats, Suppressions and Email Logs (15). The docs ask for exponential backoff on 429 and the specs document `x-ratelimit-reset`, but no idempotency key or safe-retry guidance for sends was found (10). No SLA found in the pricing reference, the terms or the security page (0). The sending API is generally available. The MCP server is at 0.11.0 and Inbound Email has no UI yet (10).)