{ "data": { "a": { "slug": "mailpace", "name": "MailPace", "vendor": "OhMySMTP Ltd", "vendorUrl": "https://mailpace.com", "kind": "http-api", "category": "email", "summary": "MailPace is a UK transactional email service, formerly OhMySMTP, hosted in the EU. It sends mail through an HTTPS API or SMTP, turns inbound mail into webhooks and has a Domains and Email Status API.", "url": "https://www.anchorterminal.com/tools/mailpace", "markdownUrl": "https://www.anchorterminal.com/tools/mailpace.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/mailpace.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/mailpace.json", "dns": "mailpace.grade.anchorterminal.com", "repo": "https://github.com/mailpace/mailpace-mcp", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "@mailpace/mailpace.js" } ], "auth": "api-key", "authNotes": "Each domain has its own server token, sent in the `MailPace-Server-Token` header, which can send from that domain and read its email status. An organisation token in `MailPace-Organization-Token` manages domains and domain tokens through the Domains API, including revoking them. Both are made in the dashboard after a browser signup.", "pricing": "paid", "pricingNotes": "$10 a month includes 10,000 emails sent or received, then $1 per 1,000, per the Paddle prices the pricing page loads and the comparison pages ($100 for 100,000, $1,000 for 1 million). A free plan of up to 100 emails a month is given on request by email. Paddle is the merchant of record; card, PayPal, Apple Pay or Google Pay.", "priceSummary": "$10 / mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs repository, the pricing page or the MCP server source (checked 2026-11-06). Payment is by Paddle subscription; the FAQ says crypto isn't accepted.", "endpoints": [] }, "toolCount": 12, "popularity": { "githubStars": 1, "npmWeekly": 207, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.mailpace.com/", "capabilities": [ "email.send", "email.inbound", "email.domains", "email.analytics" ], "tags": [ "hosted", "closed-source", "smtp", "webhooks", "idempotency", "status-page", "sla", "eu", "mcp", "typescript", "ruby", "go", "php" ], "lastRelease": "2026-10-22", "graded": true, "anchor": { "graded": true, "score": 58.4, "grade": "C", "agentReady": false, "rank": 750, "ranked": true, "rankOf": 1486, "categoryRank": 17, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 71, "maintenance": 65, "payments": 25, "reliability": 70, "schema": 54, "security": 50, "transparency": 75 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "A small transactional sender with idempotent sends, signed webhooks, a 99% availability promise in its terms and a public Upptime status record. There is no OpenAPI spec, no published rate limit, no llms.txt, and its MCP server was rewritten on 4 November 2026 but isn't on npm or in the MCP registry yet.", "bestFor": "Low-volume transactional mail from EU-hosted infrastructure with idempotent sends and no tracking.", "strengths": [ "Sends accept an `Idempotency-Key` header kept for 24 hours, so a retry after a timeout doesn't send twice", "Per-domain server tokens limit a leaked key to one domain, and organisation tokens can create and revoke them by API", "Webhooks are signed with Ed25519 and inbound mail is retried five times before it fails", "Status page on Upptime with GitHub issues as incident reports, and a 99% monthly availability promise with credits in the terms", "Sub-processors and their locations are listed, and mail is kept 30 days plus 7 in backups per the DPA" ], "weaknesses": [ "No OpenAPI spec, llms.txt or Markdown docs for agents; the reference is Docusaurus pages", "Rate limits aren't published; the docs say they vary by organisation age, plan and history", "No free plan without emailing support, and the paid plan starts at $10 a month", "MCP server 2.0.0 exists only in the repository; npm and the MCP registry had nothing for it on 6 November 2026", "No security.txt, disclosure policy or certification found" ], "agentNotes": [ "Send a UUID in `Idempotency-Key` on every `POST /api/v1/send`, and reuse it on a retry; keys last 24 hours and are tied to one token", "Use the server token of the sending domain, since the From domain must match the token's domain or the API returns 403", "On 429 `You are sending emails too quickly` back off; no Retry-After is documented", "Send only transactional mail; marketing and bulk newsletters are prohibited by the docs and terms", "Read delivery with `GET /api/v1/domains/:domain_id/emails/:id` using the id the send returned" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 58.4 } ], "editorialScores": { "ergonomics": 71, "maintenance": 65, "payments": 25, "reliability": 70, "schema": 54, "security": 50, "transparency": 69 }, "provenanceScore": 81, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl https://app.mailpace.com/api/v1/send -X POST -H \"Accept: application/json\" -H \"Content-Type: application/json\" -H \"MailPace-Server-Token: $MAILPACE_TOKEN\" -H \"Idempotency-Key: $(uuidgen)\" -d '{\"from\":\"you@yourdomain.com\",\"to\":\"person@example.com\",\"subject\":\"Hello\",\"textbody\":\"Hello\"}'" }, "letme": { "capability": "https://letme.dev/email.send", "tool": "https://letme.dev/mailpace" }, "area": "communication", "unitPrices": [ { "item": "Scaling plan", "unit": "month", "usd": 10, "note": "includes 10,000 emails sent or received" }, { "item": "Emails beyond 10,000", "unit": "1k-emails", "usd": 1 } ], "provenance": { "legalEntity": "OhMySMTP Ltd", "domain": "mailpace.com", "domainRegistered": "2022-01-10", "endpointOnVendorDomain": true, "terms": "https://mailpace.com/terms", "privacy": "https://mailpace.com/privacy", "statusPage": "https://status.mailpace.com", "changelog": "https://mailpace.com/category/changelog", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The terms and privacy policy name OhMySMTP Ltd, incorporated in England and Wales, company number 13200428. Companies House lists two active directors.", "Terms last updated 9 January 2026, privacy policy 30 August 2026, DPA updated in October 2026 per the landing repository.", "mailpace.com/robots.txt allows all paths. The terms contain no clause on automated access to the website beyond the usual licence limits.", "RDAP gives mailpace.com a registration date of 10 January 2022; the service ran as OhMySMTP before that.", "/.well-known/security.txt returns 404 on mailpace.com and app.mailpace.com." ], "score": 81 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/mailpace.json", "live": { "slug": "mailpace", "vendorStatus": { "page": "https://status.mailpace.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:01.553362214Z" }, "versions": [ { "registry": "npm", "name": "@mailpace/mailpace.js", "version": "0.1.3", "seenAt": "2026-11-06T23:42:02.752996422Z" } ], "githubStars": 1, "npmWeekly": 207, "securityTxt": { "url": "https://mailpace.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:07.630537329Z" }, "pages": [ { "url": "https://mailpace.com/category/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:13:40.841899008Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "38f92a159d1b" }, { "url": "https://mailpace.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:13:45.28058492Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e6b0fea49c1d" }, { "url": "https://mailpace.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:13:45.480605157Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "24f1eed01dad" } ], "updatedAt": "2026-11-07T16:01:07.630537329Z" } }, "answer": "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.", "b": { "slug": "mailtrap", "name": "Mailtrap Email API + MCP", "vendor": "Mailtrap (Railsware)", "vendorUrl": "https://mailtrap.io", "kind": "http-api", "category": "email", "summary": "Email platform from Railsware Products Studio LLC for transactional and bulk sending, inbound mail, templates, contacts and sandbox testing. Agents reach it through a REST API, SMTP, SDKs, a CLI and a local MCP server.", "url": "https://www.anchorterminal.com/tools/mailtrap", "markdownUrl": "https://www.anchorterminal.com/tools/mailtrap.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/mailtrap.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/mailtrap.json", "dns": "mailtrap.grade.anchorterminal.com", "repo": "https://github.com/mailtrap/mailtrap-mcp", "license": "Proprietary service under Mailtrap's terms of service. The MCP server, the Node.js SDK and the CLI are MIT", "transports": [ "http", "stdio" ], "remoteUrl": "https://send.api.mailtrap.io", "packages": [ { "registry": "npm", "name": "mailtrap" }, { "registry": "npm", "name": "mcp-mailtrap" }, { "registry": "pypi", "name": "mailtrap" } ], "auth": "api-key", "authNotes": "Self-serve API token, sent as `Authorization: Bearer` or in the `Api-Token` header. Tokens are created at mailtrap.io/settings/api-tokens with permissions per resource and an expiry of 1 to 365 days or a custom date (365 by default). A reset leaves the old token valid for 12 hours. The first token is made by hand in the UI, and later ones can be managed through the API. The MCP server reads `MAILTRAP_API_TOKEN`, and the sub-account tools need a separate organisation token.", "pricing": "freemium", "pricingNotes": "Free plan of 4,000 emails a month, capped at 150 a day, and the vendor says signup needs no credit card. Basic is $15 a month for 10,000 emails, Business starts at $85 for 100,000 and Enterprise at $750 for 1,500,000. Overage per 1,000 emails is $1.00, $0.88 and $0.55, and the free plan has none. Email Sandbox and Email Marketing are priced separately (https://mailtrap.io/pricing.md, checked 2026-10-08).", "priceSummary": "$15 / mo", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the pricing reference, the OpenAPI specs or the MCP README (checked 2026-10-08).", "endpoints": [] }, "toolCount": 130, "popularity": { "githubStars": 65, "npmWeekly": 65939, "pypiWeekly": 21317, "asOf": "2026-10-08" }, "docsUrl": "https://docs.mailtrap.io/", "llmsTxt": "https://docs.mailtrap.io/llms.txt", "openapi": "https://github.com/mailtrap/mailtrap-openapi", "registryName": "io.mailtrap/mcp", "capabilities": [ "email.send", "email.inbound", "email.templates", "email.domains", "email.analytics", "email.marketing", "email.inbox", "email.threads" ], "tags": [ "hosted", "freemium", "no-card", "mcp", "openapi", "llms-txt", "cli", "smtp", "typescript", "python", "webhooks", "sandbox", "status-page", "soc2", "iso27001" ], "lastRelease": "2026-10-30", "graded": true, "anchor": { "graded": true, "score": 66.8, "grade": "B", "agentReady": false, "rank": 352, "ranked": true, "rankOf": 1486, "categoryRank": 8, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 62, "maintenance": 93, "payments": 40, "reliability": 65, "schema": 82, "security": 60, "transparency": 77 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": 0, "verdict": "Public OpenAPI 3.1 specs, API tokens with per-resource permissions and expiry dates, and a free plan of 4,000 emails a month without a card support agent use. The MCP server loads 130 tools with no toolsets, and no idempotency key was found for sends, so a timed-out send needs a log check before any retry.", "bestFor": "Teams that want sending, a test sandbox and inbound mail under one token, with public OpenAPI specs and a free plan.", "strengths": [ "Ten public OpenAPI 3.1 specs in mailtrap/mailtrap-openapi, plus llms.txt, llms-full.txt and a Markdown copy of every docs page", "API tokens carry per-resource permissions and an expiry date (365 days by default), and a reset keeps the old token valid for 12 hours", "Free plan of 4,000 emails a month, with signup stated as needing no credit card, and overage rates published per 1,000 emails", "Every MCP tool is annotated, 55 with readOnlyHint and the other 75 with destructiveHint set true or false", "Email Sandbox captures test sends without delivering them, through the same API token and SDK switch" ], "weaknesses": [ "The MCP server registers 130 tools at once, with no toolsets, filtering or read-only mode", "No idempotency key for sends was found in the OpenAPI specs or the docs", "The status page recorded a sending outage of 1 hour 32 minutes on 1 August 2026 covering the Email Sending API, SMTP and Inbound Email", "Inbound and sandbox message bodies reach the model through the MCP server, and no prompt-injection guidance was found in its README or the docs", "User audit logs are limited to the Enterprise plan, and the free plan keeps email logs for 3 days" ], "agentNotes": [ "Ask the operator to create the first API token at mailtrap.io/settings/api-tokens. The first token can't be created through the API.", "Send transactional mail to send.api.mailtrap.io and bulk mail to bulk.api.mailtrap.io. Sandbox sending uses a different base URL and an inbox ID.", "Verify a sending domain before the first production send, and use Email Sandbox to test payloads without delivery.", "Stay under 150 requests per 10 seconds per token, and 10 per 60 seconds per account on the Stats and Suppressions APIs. On 429, back off until `x-ratelimit-reset`.", "Don't retry a timed-out send blindly, because no idempotency key was found. Check the email logs first." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3.3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 66.8 } ], "editorialScores": { "ergonomics": 62, "maintenance": 93, "payments": 40, "reliability": 65, "schema": 82, "security": 60, "transparency": 66 }, "provenanceScore": 88, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-10-28", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install mailtrap", "http": "curl -X POST https://send.api.mailtrap.io/api/send \\\n -H 'Authorization: Bearer YOUR_API_KEY' \\\n -H 'Content-Type: application/json' \\\n -d '{\n \"from\": {\"email\": \"sender@example.com\"},\n \"to\": [{\"email\": \"recipient@example.com\"}],\n \"subject\": \"Hello from Mailtrap\",\n \"text\": \"Welcome to Mailtrap!\"\n }'", "config": { "mcpServers": { "mailtrap": { "args": [ "-y", "mcp-mailtrap" ], "command": "npx", "env": { "DEFAULT_FROM_EMAIL": "your_sender@example.com", "MAILTRAP_ACCOUNT_ID": "your_account_id", "MAILTRAP_API_TOKEN": "your_mailtrap_api_token", "MAILTRAP_SANDBOX_ID": "your_sandbox_id" } } } } }, "letme": { "capability": "https://letme.dev/email.send", "tool": "https://letme.dev/mailtrap" }, "area": "communication", "unitPrices": [ { "item": "Basic 10k", "unit": "month", "usd": 15, "note": "10,000 emails" }, { "item": "Basic 100k", "unit": "month", "usd": 30, "note": "100,000 emails" }, { "item": "Business 100k", "unit": "month", "usd": 85, "note": "100,000 emails" }, { "item": "Enterprise 1.5M", "unit": "month", "usd": 750, "note": "1,500,000 emails" }, { "item": "Overage on Basic", "unit": "1k-emails", "usd": 1 }, { "item": "Overage on Business", "unit": "1k-emails", "usd": 0.88 }, { "item": "Overage on Enterprise", "unit": "1k-emails", "usd": 0.55 } ], "provenance": { "legalEntity": "Railsware Products Studio LLC", "domain": "mailtrap.io", "domainRegistered": "2011-10-06", "endpointOnVendorDomain": true, "terms": "https://mailtrap.io/terms/", "privacy": "https://mailtrap.io/privacy/", "statusPage": "https://status.mailtrap.info", "changelog": "https://feedback.mailtrap.io/changelog", "securityTxt": "none", "checked": "2026-11-01", "notes": [ "The terms of service (effective 24 September 2026) name Railsware Products Studio LLC, 117 E Colorado Blvd, Suite 600, Office 650, Pasadena, CA 91105, and are governed by Delaware law with AAA arbitration.", "The privacy policy and the data processing addendum at mailtrap.io/dpa are both dated 24 September 2026.", "The sending API answers at send.api.mailtrap.io and bulk.api.mailtrap.io. The status page is on a separate domain, status.mailtrap.info, hosted by Sorry.", "mailtrap.io/.well-known/security.txt returns 404.", "RDAP for mailtrap.io gives a registration date of 2011-10-06.", "On 1 November 2026 status.mailtrap.info answered robots.txt with 406 and an empty body, and trust.mailtrap.io with a Cloudflare bot check. mailtrap.io/.well-known/security.txt still returns 404." ], "score": 88 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/mailtrap.json", "live": { "slug": "mailtrap", "probe": { "target": "https://send.api.mailtrap.io", "method": "get", "lastAt": "2026-11-07T18:20:37.120197333Z", "lastOk": true, "lastStatus": 404, "lastMs": 487, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 406, "p95ms24h": 493, "samples24h": 239, "samples30d": 7440, "days": [ { "date": "2026-10-08", "probes": 70, "ok": 70 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://status.mailtrap.info", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:01.737894014Z" }, "versions": [ { "registry": "github", "name": "mailtrap/mailtrap-mcp", "version": "v0.12.0", "released": "2026-11-05", "seenAt": "2026-11-06T23:42:18.205427164Z" }, { "registry": "mcp-registry", "name": "io.mailtrap/mcp", "version": "0.11.0", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "npm", "name": "mailtrap", "version": "6.1.0", "seenAt": "2026-11-06T23:42:15.780828608Z" }, { "registry": "npm", "name": "mcp-mailtrap", "version": "0.12.0", "seenAt": "2026-11-06T23:42:16.004631231Z" }, { "registry": "pypi", "name": "mailtrap", "version": "3.0.0", "released": "2026-10-30", "seenAt": "2026-11-06T23:42:18.003167371Z" } ], "githubStars": 66, "npmWeekly": 76456, "pypiWeekly": 26483, "securityTxt": { "url": "https://mailtrap.io/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:47.576594095Z" }, "llmsTxt": { "url": "https://docs.mailtrap.io/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:56.635637934Z" }, "domain": { "domain": "mailtrap.io", "checkedAt": "2026-11-01T14:21:43.072025201Z" }, "pages": [ { "url": "https://feedback.mailtrap.io/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:09:46.232081333Z", "changedAt": "2026-11-05T12:33:18.740805976Z", "fingerprint": "51394c495f75" }, { "url": "https://mailtrap.io/pricing.md", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:13:41.990255988Z", "changedAt": "2026-10-24T02:20:55.561027454Z", "fingerprint": "6fdc9cd1ad56" }, { "url": "https://mailtrap.io/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:13:44.830335184Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "b3fc467f702d" }, { "url": "https://mailtrap.io/terms/", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:13:46.617154676Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "1c4fcbf64dac" } ], "github": { "repo": "mailtrap/mailtrap-mcp", "checkedAt": "2026-11-02T09:02:56.910762468Z", "stars": 66, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-30T07:48:19Z", "openIssues": 0, "openPRs": 2, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 30, "ci": { "branch": "main", "runs": 50, "success": 50, "failure": 0, "other": 0, "latest": "success", "latestAt": "2026-10-29T11:25:01Z" }, "replies": { "sampled": 12, "unanswered": 0, "medianDays": 70 } }, "updatedAt": "2026-11-07T18:20:37.120197333Z" } }, "edges": [ { "by": 28, "category": "schema", "leads": "mailtrap", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "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)." }, "scores": { "a": 54, "b": 82 } }, { "by": 28, "category": "maintenance", "leads": "mailtrap", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "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)." }, "scores": { "a": 65, "b": 93 } }, { "by": 15, "category": "payments", "leads": "mailtrap", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "b": "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)." }, "scores": { "a": 25, "b": 40 } }, { "by": 10, "category": "security", "leads": "mailtrap", "name": "Security \u0026 auth", "reasons": { "a": "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.", "b": "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)." }, "scores": { "a": 50, "b": 60 } }, { "by": 9, "category": "ergonomics", "leads": "mailpace", "name": "Agent ergonomics", "reasons": { "a": "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.", "b": "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)." }, "scores": { "a": 71, "b": 62 } }, { "by": 5, "category": "reliability", "leads": "mailpace", "name": "Reliability", "reasons": { "a": "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.", "b": "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)." }, "scores": { "a": 70, "b": 65 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "OhMySMTP Ltd", "b": "Mailtrap (Railsware)", "name": "Vendor" }, { "a": "no (local only)", "b": "https://send.api.mailtrap.io", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, stdio", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Paid", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "Proprietary service under Mailtrap's terms of service. The MCP server, the Node.js SDK and the CLI are MIT", "name": "Licence" }, { "a": "12", "b": "130", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "io.mailtrap/mcp", "name": "MCP registry" }, { "a": "2026-10-22", "b": "2026-10-30", "name": "Last release" }, { "a": "2026-01-09", "b": "2026-09-24", "name": "Terms last updated" }, { "a": "2026-08-30", "b": "2026-09-24", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "1 stars, 207 npm/wk", "b": "65 stars, 66k npm/wk, 21k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3.3/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "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.", "question": "Which is better for AI agents, MailPace or Mailtrap Email API + MCP?" }, { "answer": "Both need an API key.", "question": "Do MailPace and Mailtrap Email API + MCP need an API key?" }, { "answer": "No hosted endpoint is listed for MailPace. Mailtrap Email API + MCP has a hosted endpoint at https://send.api.mailtrap.io.", "question": "Can an agent call MailPace and Mailtrap Email API + MCP without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 70 against 65", "Agent ergonomics, 71 against 62" ], "also": null, "goodFor": "Low-volume transactional mail from EU-hosted infrastructure with idempotent sends and no tracking.", "slug": "mailpace", "watchFor": "No OpenAPI spec, llms.txt or Markdown docs for agents; the reference is Docusaurus pages" }, { "aheadOn": [ "Schema \u0026 documentation, 82 against 54", "Security \u0026 auth, 60 against 50", "Payments \u0026 pricing, 40 against 25", "Maintenance \u0026 community, 93 against 65" ], "also": [ "A hosted endpoint, with nothing to install", "Runs on your own machine", "Free to start without a card" ], "goodFor": "Teams that want sending, a test sandbox and inbound mail under one token, with public OpenAPI specs and a free plan.", "slug": "mailtrap", "watchFor": "The MCP server registers 130 tools at once, with no toolsets, filtering or read-only mode" } ], "history": { "mailpace": null, "mailtrap": [ { "causes": [ "correction" ], "date": "2026-10-28", "delta": -0.1, "from": 66.9, "fromGrade": "B", "to": 66.8, "toGrade": "B" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 66.8, "fromGrade": "B", "to": 66.9, "toGrade": "B" } ] }, "job": { "capability": "email.send", "name": "Sending email" }, "others": [ { "json": "https://www.anchorterminal.com/compare/ahasend-vs-mailpace.json", "title": "AhaSend API + MCP vs MailPace", "url": "https://www.anchorterminal.com/compare/ahasend-vs-mailpace" }, { "json": "https://www.anchorterminal.com/compare/ahasend-vs-mailtrap.json", "title": "AhaSend API + MCP vs Mailtrap Email API + MCP", "url": "https://www.anchorterminal.com/compare/ahasend-vs-mailtrap" }, { "json": "https://www.anchorterminal.com/compare/amazon-ses-vs-mailpace.json", "title": "Amazon SES vs MailPace", "url": "https://www.anchorterminal.com/compare/amazon-ses-vs-mailpace" }, { "json": "https://www.anchorterminal.com/compare/amazon-ses-vs-mailtrap.json", "title": "Amazon SES vs Mailtrap Email API + MCP", "url": "https://www.anchorterminal.com/compare/amazon-ses-vs-mailtrap" }, { "json": "https://www.anchorterminal.com/compare/brevo-vs-mailpace.json", "title": "Brevo API + MCP vs MailPace", "url": "https://www.anchorterminal.com/compare/brevo-vs-mailpace" }, { "json": "https://www.anchorterminal.com/compare/brevo-vs-mailtrap.json", "title": "Brevo API + MCP vs Mailtrap Email API + MCP", "url": "https://www.anchorterminal.com/compare/brevo-vs-mailtrap" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailpace.json", "title": "Cloudflare Email Service vs MailPace", "url": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailpace" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailtrap.json", "title": "Cloudflare Email Service vs Mailtrap Email API + MCP", "url": "https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailtrap" }, { "json": "https://www.anchorterminal.com/compare/groundmail-vs-mailpace.json", "title": "Groundmail API + MCP vs MailPace", "url": "https://www.anchorterminal.com/compare/groundmail-vs-mailpace" }, { "json": "https://www.anchorterminal.com/compare/groundmail-vs-mailtrap.json", "title": "Groundmail API + MCP vs Mailtrap Email API + MCP", "url": "https://www.anchorterminal.com/compare/groundmail-vs-mailtrap" }, { "json": "https://www.anchorterminal.com/compare/loops-vs-mailpace.json", "title": "Loops API + MCP vs MailPace", "url": "https://www.anchorterminal.com/compare/loops-vs-mailpace" }, { "json": "https://www.anchorterminal.com/compare/loops-vs-mailtrap.json", "title": "Loops API + MCP vs Mailtrap Email API + MCP", "url": "https://www.anchorterminal.com/compare/loops-vs-mailtrap" }, { "json": "https://www.anchorterminal.com/compare/mailersend-vs-mailpace.json", "title": "MailerSend vs MailPace", "url": "https://www.anchorterminal.com/compare/mailersend-vs-mailpace" }, { "json": "https://www.anchorterminal.com/compare/mailersend-vs-mailtrap.json", "title": "MailerSend vs Mailtrap Email API + MCP", "url": "https://www.anchorterminal.com/compare/mailersend-vs-mailtrap" }, { "json": "https://www.anchorterminal.com/compare/mailgun-vs-mailpace.json", "title": "Mailgun API + MCP vs MailPace", "url": "https://www.anchorterminal.com/compare/mailgun-vs-mailpace" }, { "json": "https://www.anchorterminal.com/compare/mailgun-vs-mailtrap.json", "title": "Mailgun API + MCP vs Mailtrap Email API + MCP", "url": "https://www.anchorterminal.com/compare/mailgun-vs-mailtrap" }, { "json": "https://www.anchorterminal.com/compare/mailjet-vs-mailpace.json", "title": "Mailjet API + MCP vs MailPace", "url": "https://www.anchorterminal.com/compare/mailjet-vs-mailpace" }, { "json": "https://www.anchorterminal.com/compare/mailjet-vs-mailtrap.json", "title": "Mailjet API + MCP vs Mailtrap Email API + MCP", "url": "https://www.anchorterminal.com/compare/mailjet-vs-mailtrap" }, { "json": "https://www.anchorterminal.com/compare/mailpace-vs-mandrill.json", "title": "MailPace vs Mailchimp Transactional (Mandrill)", "url": "https://www.anchorterminal.com/compare/mailpace-vs-mandrill" }, { "json": "https://www.anchorterminal.com/compare/mailpace-vs-postmark.json", "title": "MailPace vs Postmark API + MCP", "url": "https://www.anchorterminal.com/compare/mailpace-vs-postmark" }, { "json": "https://www.anchorterminal.com/compare/mailpace-vs-resend.json", "title": "MailPace vs Resend API + MCP", "url": "https://www.anchorterminal.com/compare/mailpace-vs-resend" }, { "json": "https://www.anchorterminal.com/compare/mailpace-vs-sendgrid.json", "title": "MailPace vs Twilio SendGrid", "url": "https://www.anchorterminal.com/compare/mailpace-vs-sendgrid" }, { "json": "https://www.anchorterminal.com/compare/mailpace-vs-sendlayer.json", "title": "MailPace vs SendLayer", "url": "https://www.anchorterminal.com/compare/mailpace-vs-sendlayer" }, { "json": "https://www.anchorterminal.com/compare/mailpace-vs-smtp2go.json", "title": "MailPace vs SMTP2GO API + MCP", "url": "https://www.anchorterminal.com/compare/mailpace-vs-smtp2go" }, { "json": "https://www.anchorterminal.com/compare/mailpace-vs-zoho-zeptomail.json", "title": "MailPace vs Zoho CPaaS (formerly ZeptoMail)", "url": "https://www.anchorterminal.com/compare/mailpace-vs-zoho-zeptomail" }, { "json": "https://www.anchorterminal.com/compare/mailtrap-vs-mandrill.json", "title": "Mailtrap Email API + MCP vs Mailchimp Transactional (Mandrill)", "url": "https://www.anchorterminal.com/compare/mailtrap-vs-mandrill" }, { "json": "https://www.anchorterminal.com/compare/mailtrap-vs-postmark.json", "title": "Mailtrap Email API + MCP vs Postmark API + MCP", "url": "https://www.anchorterminal.com/compare/mailtrap-vs-postmark" }, { "json": "https://www.anchorterminal.com/compare/mailtrap-vs-resend.json", "title": "Mailtrap Email API + MCP vs Resend API + MCP", "url": "https://www.anchorterminal.com/compare/mailtrap-vs-resend" }, { "json": "https://www.anchorterminal.com/compare/mailtrap-vs-sendgrid.json", "title": "Mailtrap Email API + MCP vs Twilio SendGrid", "url": "https://www.anchorterminal.com/compare/mailtrap-vs-sendgrid" }, { "json": "https://www.anchorterminal.com/compare/mailtrap-vs-sendlayer.json", "title": "Mailtrap Email API + MCP vs SendLayer", "url": "https://www.anchorterminal.com/compare/mailtrap-vs-sendlayer" }, { "json": "https://www.anchorterminal.com/compare/mailtrap-vs-smtp2go.json", "title": "Mailtrap Email API + MCP vs SMTP2GO API + MCP", "url": "https://www.anchorterminal.com/compare/mailtrap-vs-smtp2go" }, { "json": "https://www.anchorterminal.com/compare/mailtrap-vs-zoho-zeptomail.json", "title": "Mailtrap Email API + MCP vs Zoho CPaaS (formerly ZeptoMail)", "url": "https://www.anchorterminal.com/compare/mailtrap-vs-zoho-zeptomail" } ], "panel": null, "scores": [ { "by": 5, "edge": "mailpace", "key": "reliability", "mailpace": 70, "mailtrap": 65, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 28, "edge": "mailtrap", "key": "schema", "mailpace": 54, "mailtrap": 82, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 9, "edge": "mailpace", "key": "ergonomics", "mailpace": 71, "mailtrap": 62, "name": "Agent ergonomics", "weight": 13 }, { "by": 10, "edge": "mailtrap", "key": "security", "mailpace": 50, "mailtrap": 60, "name": "Security \u0026 auth", "weight": 14 }, { "by": 15, "edge": "mailtrap", "key": "payments", "mailpace": 25, "mailtrap": 40, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 28, "edge": "mailtrap", "key": "maintenance", "mailpace": 65, "mailtrap": 93, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 2, "edge": "mailtrap", "key": "transparency", "mailpace": 75, "mailtrap": 77, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "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.", "tasks": null, "tutorials": [], "verdicts": { "mailpace": "A small transactional sender with idempotent sends, signed webhooks, a 99% availability promise in its terms and a public Upptime status record. There is no OpenAPI spec, no published rate limit, no llms.txt, and its MCP server was rewritten on 4 November 2026 but isn't on npm or in the MCP registry yet.", "mailtrap": "Public OpenAPI 3.1 specs, API tokens with per-resource permissions and expiry dates, and a free plan of 4,000 emails a month without a card support agent use. The MCP server loads 130 tools with no toolsets, and no idempotency key was found for sends, so a timed-out send needs a log check before any retry." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/mailpace-vs-mailtrap", "json": "https://www.anchorterminal.com/compare/mailpace-vs-mailtrap.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/mailpace-vs-mailtrap.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/mailpace-vs-mailtrap.min.md" }, "markdown": "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.\n\n- MailPace: grade C, 58.4/100, rank #750 of 1486. Markdown https://www.anchorterminal.com/tools/mailpace.md · JSON https://www.anchorterminal.com/api/v1/tools/mailpace.json\n- Mailtrap Email API + MCP: grade B, 66.8/100, rank #352 of 1486. Markdown https://www.anchorterminal.com/tools/mailtrap.md · JSON https://www.anchorterminal.com/api/v1/tools/mailtrap.json\n- Best email delivery APIs for AI agents: https://www.anchorterminal.com/best/email/index.md\n- All 174 email comparisons: https://www.anchorterminal.com/compare/email/index.md\n\n## Which one, for what\n\n### MailPace (C)\n\nGood for: Low-volume transactional mail from EU-hosted infrastructure with idempotent sends and no tracking.\n\nAhead on:\n- Reliability, 70 against 65\n- Agent ergonomics, 71 against 62\n\nWatch for: No OpenAPI spec, llms.txt or Markdown docs for agents; the reference is Docusaurus pages\n\n### Mailtrap Email API + MCP (B)\n\nGood for: Teams that want sending, a test sandbox and inbound mail under one token, with public OpenAPI specs and a free plan.\n\nAhead on:\n- Schema \u0026 documentation, 82 against 54\n- Security \u0026 auth, 60 against 50\n- Payments \u0026 pricing, 40 against 25\n- Maintenance \u0026 community, 93 against 65\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: The MCP server registers 130 tools at once, with no toolsets, filtering or read-only mode\n\n\n## Why the edge\n\n### Schema \u0026 documentation: Mailtrap Email API + MCP +28\n\n- 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.\n- 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).\n\n### Maintenance \u0026 community: Mailtrap Email API + MCP +28\n\n- 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.\n- 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).\n\n### Payments \u0026 pricing: Mailtrap Email API + MCP +15\n\n- 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.\n- 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).\n\n### Security \u0026 auth: Mailtrap Email API + MCP +10\n\n- 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.\n- 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).\n\n### Agent ergonomics: MailPace +9\n\n- 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.\n- 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).\n\n### Reliability: MailPace +5\n\n- 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.\n- 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).\n\n## Score by category\n\n| Category | Weight | MailPace | Mailtrap Email API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 70 | 65 | MailPace +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 54 | 82 | Mailtrap Email API + MCP +28 |\n| Agent ergonomics | 13% (16.2 this run) | 71 | 62 | MailPace +9 |\n| Security \u0026 auth | 14% (17.5 this run) | 50 | 60 | Mailtrap Email API + MCP +10 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 25 | 40 | Mailtrap Email API + MCP +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 65 | 93 | Mailtrap Email API + MCP +28 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 75 | 77 | Mailtrap Email API + MCP +2 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **58.4 · C** | **66.8 · B** | |\n\n## Facts side by side\n\n| Fact | MailPace | Mailtrap Email API + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | OhMySMTP Ltd | Mailtrap (Railsware) |\n| Hosted endpoint | no (local only) | `https://send.api.mailtrap.io` |\n| Transports | HTTP | HTTP, stdio |\n| Auth | API key | API key |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| Licence | none | Proprietary service under Mailtrap's terms of service. The MCP server, the Node.js SDK and the CLI are MIT |\n| Tools exposed | 12 | 130 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| MCP registry | not listed | `io.mailtrap/mcp` |\n| Last release | 2026-10-22 | 2026-10-30 |\n| Terms last updated | 2026-01-09 | 2026-09-24 |\n| Privacy policy last updated | 2026-08-30 | 2026-09-24 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | 1 stars, 207 npm/wk | 65 stars, 66k npm/wk, 21k PyPI/wk |\n| Agent reviews | none | 3.3/5 (4) |\n\n## How the scores have moved\n\n### MailPace\n\nNo score change since it was listed.\n\n### Mailtrap Email API + MCP\n\n- -0.1 on 28 October 2026: correction\n- +0.1 on 27 October 2026: checklist\n\n## Verdicts\n\n**MailPace.** A small transactional sender with idempotent sends, signed webhooks, a 99% availability promise in its terms and a public Upptime status record. There is no OpenAPI spec, no published rate limit, no llms.txt, and its MCP server was rewritten on 4 November 2026 but isn't on npm or in the MCP registry yet.\n\n**Mailtrap Email API + MCP.** Public OpenAPI 3.1 specs, API tokens with per-resource permissions and expiry dates, and a free plan of 4,000 emails a month without a card support agent use. The MCP server loads 130 tools with no toolsets, and no idempotency key was found for sends, so a timed-out send needs a log check before any retry.\n\n## Before you call either\n\n### MailPace\n\n1. Send a UUID in `Idempotency-Key` on every `POST /api/v1/send`, and reuse it on a retry; keys last 24 hours and are tied to one token\n2. Use the server token of the sending domain, since the From domain must match the token's domain or the API returns 403\n3. On 429 `You are sending emails too quickly` back off; no Retry-After is documented\n4. Send only transactional mail; marketing and bulk newsletters are prohibited by the docs and terms\n5. Read delivery with `GET /api/v1/domains/:domain_id/emails/:id` using the id the send returned\n\n### Mailtrap Email API + MCP\n\n1. Ask the operator to create the first API token at mailtrap.io/settings/api-tokens. The first token can't be created through the API.\n2. Send transactional mail to send.api.mailtrap.io and bulk mail to bulk.api.mailtrap.io. Sandbox sending uses a different base URL and an inbox ID.\n3. Verify a sending domain before the first production send, and use Email Sandbox to test payloads without delivery.\n4. Stay under 150 requests per 10 seconds per token, and 10 per 60 seconds per account on the Stats and Suppressions APIs. On 429, back off until `x-ratelimit-reset`.\n5. Don't retry a timed-out send blindly, because no idempotency key was found. Check the email logs first.\n\n## Questions\n\n### Which is better for AI agents, MailPace or Mailtrap Email API + MCP?\n\nMailtrap 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.\n\n### Do MailPace and Mailtrap Email API + MCP need an API key?\n\nBoth need an API key.\n\n### Can an agent call MailPace and Mailtrap Email API + MCP without installing anything?\n\nNo hosted endpoint is listed for MailPace. Mailtrap Email API + MCP has a hosted endpoint at https://send.api.mailtrap.io.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/mailpace-vs-mailtrap.json, and with the fewest tokens: https://www.anchorterminal.com/compare/mailpace-vs-mailtrap.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"mailpace\", \"b\": \"mailtrap\"}`. From a terminal: `anchor compare mailpace mailtrap`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/mailpace.json and https://www.anchorterminal.com/api/v1/tools/mailtrap.json\n\n## Other comparisons with MailPace or Mailtrap Email API + MCP\n\n- [AhaSend API + MCP vs MailPace](https://www.anchorterminal.com/compare/ahasend-vs-mailpace.md)\n- [AhaSend API + MCP vs Mailtrap Email API + MCP](https://www.anchorterminal.com/compare/ahasend-vs-mailtrap.md)\n- [Amazon SES vs MailPace](https://www.anchorterminal.com/compare/amazon-ses-vs-mailpace.md)\n- [Amazon SES vs Mailtrap Email API + MCP](https://www.anchorterminal.com/compare/amazon-ses-vs-mailtrap.md)\n- [Brevo API + MCP vs MailPace](https://www.anchorterminal.com/compare/brevo-vs-mailpace.md)\n- [Brevo API + MCP vs Mailtrap Email API + MCP](https://www.anchorterminal.com/compare/brevo-vs-mailtrap.md)\n- [Cloudflare Email Service vs MailPace](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailpace.md)\n- [Cloudflare Email Service vs Mailtrap Email API + MCP](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailtrap.md)\n- [Groundmail API + MCP vs MailPace](https://www.anchorterminal.com/compare/groundmail-vs-mailpace.md)\n- [Groundmail API + MCP vs Mailtrap Email API + MCP](https://www.anchorterminal.com/compare/groundmail-vs-mailtrap.md)\n- [Loops API + MCP vs MailPace](https://www.anchorterminal.com/compare/loops-vs-mailpace.md)\n- [Loops API + MCP vs Mailtrap Email API + MCP](https://www.anchorterminal.com/compare/loops-vs-mailtrap.md)\n- [MailerSend vs MailPace](https://www.anchorterminal.com/compare/mailersend-vs-mailpace.md)\n- [MailerSend vs Mailtrap Email API + MCP](https://www.anchorterminal.com/compare/mailersend-vs-mailtrap.md)\n- [Mailgun API + MCP vs MailPace](https://www.anchorterminal.com/compare/mailgun-vs-mailpace.md)\n- [Mailgun API + MCP vs Mailtrap Email API + MCP](https://www.anchorterminal.com/compare/mailgun-vs-mailtrap.md)\n- [Mailjet API + MCP vs MailPace](https://www.anchorterminal.com/compare/mailjet-vs-mailpace.md)\n- [Mailjet API + MCP vs Mailtrap Email API + MCP](https://www.anchorterminal.com/compare/mailjet-vs-mailtrap.md)\n- [MailPace vs Mailchimp Transactional (Mandrill)](https://www.anchorterminal.com/compare/mailpace-vs-mandrill.md)\n- [MailPace vs Postmark API + MCP](https://www.anchorterminal.com/compare/mailpace-vs-postmark.md)\n- [MailPace vs Resend API + MCP](https://www.anchorterminal.com/compare/mailpace-vs-resend.md)\n- [MailPace vs Twilio SendGrid](https://www.anchorterminal.com/compare/mailpace-vs-sendgrid.md)\n- [MailPace vs SendLayer](https://www.anchorterminal.com/compare/mailpace-vs-sendlayer.md)\n- [MailPace vs SMTP2GO API + MCP](https://www.anchorterminal.com/compare/mailpace-vs-smtp2go.md)\n- [MailPace vs Zoho CPaaS (formerly ZeptoMail)](https://www.anchorterminal.com/compare/mailpace-vs-zoho-zeptomail.md)\n- [Mailtrap Email API + MCP vs Mailchimp Transactional (Mandrill)](https://www.anchorterminal.com/compare/mailtrap-vs-mandrill.md)\n- [Mailtrap Email API + MCP vs Postmark API + MCP](https://www.anchorterminal.com/compare/mailtrap-vs-postmark.md)\n- [Mailtrap Email API + MCP vs Resend API + MCP](https://www.anchorterminal.com/compare/mailtrap-vs-resend.md)\n- [Mailtrap Email API + MCP vs Twilio SendGrid](https://www.anchorterminal.com/compare/mailtrap-vs-sendgrid.md)\n- [Mailtrap Email API + MCP vs SendLayer](https://www.anchorterminal.com/compare/mailtrap-vs-sendlayer.md)\n- [Mailtrap Email API + MCP vs SMTP2GO API + MCP](https://www.anchorterminal.com/compare/mailtrap-vs-smtp2go.md)\n- [Mailtrap Email API + MCP vs Zoho CPaaS (formerly ZeptoMail)](https://www.anchorterminal.com/compare/mailtrap-vs-zoho-zeptomail.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "MailPace vs Mailtrap Email API + MCP", "url": "" } ], "description": "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.", "facts": [ "MailPace C 58.4", "Mailtrap Email API + MCP B 66.8", "scores" ], "h1": "MailPace vs Mailtrap Email API + MCP", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/mailpace-vs-mailtrap", "published": "2026-10-01", "section": "tools", "title": "MailPace vs Mailtrap Email for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/mailpace-vs-mailtrap" }, "tokens": { "markdown": 5300, "slim": 3180 }, "version": 1 }