{ "data": { "similar": [ { "grade": "A", "json": "https://www.anchorterminal.com/tools/resend.json", "name": "Resend API + MCP", "score": 78.1, "shared": [ "email.send", "email.inbound", "email.domains", "email.analytics" ], "slug": "resend" }, { "grade": "BB", "json": "https://www.anchorterminal.com/tools/ahasend.json", "name": "AhaSend API + MCP", "score": 75.4, "shared": [ "email.send", "email.domains", "email.analytics", "email.inbound" ], "slug": "ahasend" }, { "grade": "BB", "json": "https://www.anchorterminal.com/tools/amazon-ses.json", "name": "Amazon SES", "score": 73.6, "shared": [ "email.send", "email.inbound", "email.domains", "email.analytics" ], "slug": "amazon-ses" }, { "grade": "BB", "json": "https://www.anchorterminal.com/tools/agentmail.json", "name": "AgentMail API + MCP", "score": 72.8, "shared": [ "email.send", "email.inbound", "email.domains", "email.analytics" ], "slug": "agentmail" }, { "grade": "BB", "json": "https://www.anchorterminal.com/tools/mailersend.json", "name": "MailerSend", "score": 71.4, "shared": [ "email.send", "email.inbound", "email.domains", "email.analytics" ], "slug": "mailersend" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/mailgun.json", "name": "Mailgun API + MCP", "score": 69.3, "shared": [ "email.send", "email.inbound", "email.domains", "email.analytics" ], "slug": "mailgun" } ], "tool": { "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" ], "breakdown": [ { "key": "reliability", "name": "Reliability", "weight": 16, "effectiveWeight": 20, "score": 70, "points": 14, "reason": "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.", "checked": "2026-11-06" }, { "key": "performance", "name": "Performance", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes." }, { "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "effectiveWeight": 16.25, "score": 54, "points": 8.78, "reason": "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.", "checked": "2026-11-06" }, { "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "effectiveWeight": 16.25, "score": 71, "points": 11.54, "reason": "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.", "checked": "2026-11-06" }, { "key": "security", "name": "Security \u0026 auth", "weight": 14, "effectiveWeight": 17.5, "score": 50, "points": 8.75, "reason": "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.", "checked": "2026-11-06" }, { "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "effectiveWeight": 12.5, "score": 25, "points": 3.13, "reason": "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.", "checked": "2026-11-06" }, { "key": "tasks", "name": "Task success", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored." }, { "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "effectiveWeight": 8.75, "score": 65, "points": 5.69, "reason": "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.", "checked": "2026-11-06" }, { "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "effectiveWeight": 8.75, "score": 75, "points": 6.56, "note": "editorial 69, provenance 81", "reason": "Closed hosted service under terms that name OhMySMTP Ltd with its company number. The MCP server, SDKs, landing site and status page are MIT (18 of 30). The privacy policy (30 August 2026), the pricing page and the DPA agree on retention, 30 days in the dashboard and 7 more in backups, 37 days at most (25 of 30). The API reference promises an old version runs until a published end-of-life date, and the terms list dated changes. The terms also say changes apply immediately (8 of 20). Sub-processors listed with purpose and location, Freethought hosting in the EU, Hetzner backups in Germany, AppSignal in Amsterdam, Paddle in the UK and Tutanota in Germany (18 of 20). Total 69.", "checked": "2026-11-06" } ], "assessment": { "date": "2026-11-06", "basis": "public evidence", "confidence": "medium", "notes": { "ergonomics": "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.", "maintenance": "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.", "payments": "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.", "reliability": "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.", "schema": "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.", "security": "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.", "transparency": "Closed hosted service under terms that name OhMySMTP Ltd with its company number. The MCP server, SDKs, landing site and status page are MIT (18 of 30). The privacy policy (30 August 2026), the pricing page and the DPA agree on retention, 30 days in the dashboard and 7 more in backups, 37 days at most (25 of 30). The API reference promises an old version runs until a published end-of-life date, and the terms list dated changes. The terms also say changes apply immediately (8 of 20). Sub-processors listed with purpose and location, Freethought hosting in the EU, Hetzner backups in Germany, AppSignal in Amsterdam, Paddle in the UK and Tutanota in Germany (18 of 20). Total 69." }, "sources": [ { "what": "home page and quick facts", "url": "https://mailpace.com/", "seen": "2026-11-06" }, { "what": "pricing page", "url": "https://mailpace.com/pricing", "seen": "2026-11-06" }, { "what": "Paddle prices the pricing page loads", "url": "https://checkout.paddle.com/api/2.0/prices?product_ids=687241,687246\u0026customer_country=US", "seen": "2026-11-06" }, { "what": "docs introduction", "url": "https://docs.mailpace.com/", "seen": "2026-11-06" }, { "what": "docs repository (reference, guides, history)", "url": "https://github.com/mailpace/docs", "seen": "2026-11-06" }, { "what": "MCP server source", "url": "https://github.com/mailpace/mailpace-mcp", "seen": "2026-11-06" }, { "what": "status repository and incident issues", "url": "https://github.com/mailpace/status/issues?q=is%3Aissue", "seen": "2026-11-06" }, { "what": "landing repository (terms, privacy, DPA, changelog posts)", "url": "https://github.com/mailpace/landing", "seen": "2026-11-06" }, { "what": "terms", "url": "https://mailpace.com/terms", "seen": "2026-11-06" }, { "what": "Companies House officers", "url": "https://find-and-update.company-information.service.gov.uk/company/13200428/officers", "seen": "2026-11-06" }, { "what": "official MCP registry search", "url": "https://registry.modelcontextprotocol.io/v0/servers?search=mailpace", "seen": "2026-11-06" } ], "openQuestions": [ "The home page says 1,000 emails a month for under $4 a month, while the pricing page's lowest price is $10 a month for 10,000; no plan under $10 was found", "Whether the free 100-email plan needs a card was not stated", "Rate limit numbers are not published", "unchecked: the MCP server's npm package and registry entry, which its README says are coming" ] }, "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 }, "scoreHistory": [ { "date": "2026-11-06", "grade": "C", "kind": "listed", "method": "0.7", "score": 58.4 } ] }, "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" }, "notable": [ "Send endpoint takes an `Idempotency-Key` header, kept 24 hours per API token, so a retried send is delivered once (https://docs.mailpace.com/guide/idempotency)", "Email Status API added on 22 October 2026 returns queued, delivered, deferred, bounced or spam with the bounce response for one email (https://docs.mailpace.com/reference/email-status)", "MCP server rewritten as version 2.0.0 on 4 November 2026 with 12 tools, annotations, output schemas and an optional recipient allowlist. It isn't on npm or in the official MCP registry yet (https://github.com/mailpace/mailpace-mcp)", "No open or click tracking, by design, and only transactional mail is allowed (https://docs.mailpace.com/)", "Terms promise 99% monthly availability of the API and dashboard with a 5% credit per 30 minutes of downtime (https://mailpace.com/terms)" ], "area": "communication", "details": [ { "label": "Surface listed", "value": "The HTTPS API at app.mailpace.com/api/v1 (send, Domains API, Email Status API), SMTP and inbound webhooks, read from the docs repository, mailpace.com, the landing and status repositories and the MCP server source on 6 November 2026. No account was made" }, { "label": "Limits", "value": "Up to 50 recipients in the To field, no batch endpoint, 30 MB total message size per the send reference (the home page says 25 MB). Rate limits unpublished" }, { "label": "Retention", "value": "Emails shown in the dashboard for 30 days, deleted from backups 7 days later, 37 days at most, per the DPA" }, { "label": "MCP server", "value": "mailpace-mcp 2.0.0, stdio, MIT, 12 tools (send, email status, domains and domain tokens), rewritten 4 November 2026. Its README says it will be published to npm and the official MCP registry as com.mailpace/mailpace-mcp" }, { "label": "Hosting", "value": "Freethought (EU-hosted application servers and databases), Hetzner backups in Germany, AppSignal in Amsterdam, Paddle and Tutanota, per the privacy policy of 30 August 2026" }, { "label": "Previous name", "value": "OhMySMTP until January 2022; the company is still OhMySMTP Ltd" } ], "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, "checks": [ { "check": "Legal entity named", "value": "OhMySMTP Ltd", "points": 20, "max": 20, "state": "ok" }, { "check": "Domain age", "value": "mailpace.com, registered 2022-01-10 (4 years)", "points": 7, "max": 15, "state": "part" }, { "check": "Endpoint on the vendor's domain", "value": "mailpace.com", "points": 15, "max": 15, "state": "ok" }, { "check": "Terms of service", "value": "read, states 6 of the 7 things a reader expects, and has 1 clause that costs points", "points": 7.1, "max": 10, "state": "part" }, { "check": "Privacy policy", "value": "read, states 6 of the 8 things a reader expects", "points": 8.5, "max": 10, "state": "part" }, { "check": "Status page", "value": "status.mailpace.com", "points": 10, "max": 10, "state": "ok" }, { "check": "Changelog", "value": "published", "points": 10, "max": 10, "state": "ok" }, { "check": "security.txt", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "People named", "value": "2 named with their role, 1 with a public profile", "points": 10, "max": 10, "state": "ok" }, { "check": "Support route", "value": "a support address, help pages", "points": 5, "max": 5, "state": "ok" } ], "policies": [ { "kind": "terms", "url": "https://mailpace.com/terms", "state": "read", "readAt": "2026-11-06", "statedDate": "2026-01-09", "words": 2086, "points": 7.1, "max": 10, "expected": [ { "key": "terms.date", "label": "Gives the date it was last updated", "found": true, "quote": "Last Updated: January 9th 2026", "says": "Last updated 2026-01-09" }, { "key": "terms.law", "label": "Names the governing law or courts", "found": true, "quote": "Any claim relating to MailPace's web site shall be governed by the laws of the United Kingdom of Great Britain and Northern Ireland without regard to its conflict of law provisions.", "says": "The law of the United Kingdom of Great Britain" }, { "key": "terms.liability", "label": "States a limit on its liability", "found": true, "quote": "In no event shall MailPace or its suppliers be liable for any damages (including, without limitation, damages for loss of data or profit, or due to business interruption,) arising out of the use or inability to use the materials on MailPace's Internet site or the service provided by MailPace, even if MailPace or a Mai…" }, { "key": "terms.termination", "label": "Says how the agreement or account can be ended", "found": true, "quote": "MailPace may suspend the services without liability if: (i) MailPace reasonably believes that the services are being used in violation of the Agreement;" }, { "key": "terms.changes", "label": "Says how changes to the terms are announced", "found": false }, { "key": "terms.use", "label": "Lists what users may not do", "found": true, "quote": "You may not use MailPace’s network or services to engage in, foster, or promote illegal, abusive, or irresponsible behavior, including:" }, { "key": "terms.sla", "label": "Refers to a service level or uptime commitment", "found": true, "quote": "MailPace guarantees that the email API service and dashboard will be available 99% of the time in any given monthly billing period, excluding maintenance.", "says": "Names 99% availability" } ], "toKnow": [ { "key": "terms.automated", "label": "Restricts automated access", "found": true, "quote": "Creation of Bot accounts;", "costsPoints": true } ] }, { "kind": "privacy", "url": "https://mailpace.com/privacy", "state": "read", "readAt": "2026-11-06", "statedDate": "2026-08-30", "words": 734, "points": 8.5, "max": 10, "expected": [ { "key": "privacy.date", "label": "Gives the date it was last updated", "found": true, "quote": "Last Updated: August 30th 2026", "says": "Last updated 2026-08-30" }, { "key": "privacy.collected", "label": "Says what personal data is collected", "found": true, "quote": "We collect your email address to allow us to provide a login service and to send important account notifications, such as plan upgrades and support services." }, { "key": "privacy.retention", "label": "Says how long data is kept", "found": true, "quote": "These emails are sent through our SMTP server and stored for you to access them for up to 30 days.", "says": "Names a period of 30 days" }, { "key": "privacy.processors", "label": "Says who else receives the data", "found": true, "quote": "Share your data with third parties for marketing purposes" }, { "key": "privacy.sale", "label": "Says whether personal data is sold or shared for advertising", "found": false }, { "key": "privacy.rights", "label": "Says what rights people have over their data", "found": true, "quote": "We share certain information to operate our service with companies that may be considered our \"sub-processors\" under GDPR." }, { "key": "privacy.contact", "label": "Gives a privacy contact", "found": false }, { "key": "privacy.transfers", "label": "Says where data is transferred or stored", "found": true, "quote": "Proudly made in the UK 🇬🇧 and hosted in the European Union 🇪🇺" } ] } ] }, "humans": { "slug": "mailpace", "checked": "2026-11-06", "company": "OhMySMTP Ltd", "people": [ { "name": "Paul Cleary", "role": "Founder, MailPace; director, OhMySMTP Ltd", "founder": true, "x": "https://x.com/EHLO_250", "page": "/people/paul-cleary/" }, { "name": "Harriet Cleary", "role": "Director, OhMySMTP Ltd, appointed 20 February 2026", "page": "/people/harriet-cleary/" } ], "peopleNote": "MailPace's current site, docs and blog name no team. Its earlier blog (The Official MailPace Blog, the blog.mailpace.com build still served on Netlify) signs the rename post of 28 January 2022 \"Written by Paul, founder of MailPace\" and links his X account. Companies House lists Paul Cleary as a director of OhMySMTP Ltd (13200428) since its incorporation on 15 February 2021, and Harriet Cleary since 20 February 2026; the terms and privacy policy name OhMySMTP Ltd. Commits to the MCP, docs and status repositories come from the GitHub account paul-oms, whose profile gives no name, so it isn't linked here. No investors or funding announcements were found on mailpace.com, its blog, the old blog or the Companies House pages, so investors are left out.", "companySocial": { "github": "https://github.com/mailpace" }, "support": { "emails": [ "support@mailpace.com" ], "urls": [ "https://docs.mailpace.com/", "https://status.mailpace.com" ] }, "sources": [ "https://mailpace.com/", "https://mailpace.com/terms", "https://mailpace.com/privacy", "https://docs.mailpace.com/", "https://find-and-update.company-information.service.gov.uk/company/13200428/officers", "https://github.com/mailpace", "https://determined-leavitt-2bc472.netlify.app/blog/ohmysmtp-is-now-mailpace", "https://mailpace.com/blog/changelog/ohmysmtp-is-now-mailpace" ], "ownership": { "status": "private", "checked": "2026-11-06", "sources": [ "https://find-and-update.company-information.service.gov.uk/company/13200428/officers", "https://mailpace.com/terms" ] } }, "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" } }, "verify": { "accepts": "a page on mailpace.com or one of its subdomains, or the README at the root of github.com/mailpace/mailpace-mcp", "badgeUrl": "https://www.anchorterminal.com/badges/mailpace.svg", "body": { "slug": "mailpace", "url": "the page with the badge or the link" }, "docs": "https://www.anchorterminal.com/builders/#verify", "effect": "none, it never changes a grade, rank or review", "endpoint": "https://www.anchorterminal.com/api/v1/verify", "listingUrl": "https://www.anchorterminal.com/tools/mailpace", "mcpTool": "verify_listing", "recheck": "weekly; two failed checks in a row and it lapses, a later pass restores it", "snippets": { "html": "\u003ca href=\"https://www.anchorterminal.com/tools/mailpace\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/mailpace.svg\" alt=\"MailPace on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e", "markdown": "[![MailPace on Anchor Terminal](https://www.anchorterminal.com/badges/mailpace.svg)](https://www.anchorterminal.com/tools/mailpace)", "link": "\u003ca href=\"https://www.anchorterminal.com/tools/mailpace\"\u003eMailPace on Anchor Terminal\u003c/a\u003e" } } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/tools/mailpace", "json": "https://www.anchorterminal.com/tools/mailpace.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/tools/mailpace.md", "mcp": "https://www.anchorterminal.com/mcp", "pricing": "https://www.anchorterminal.com/tools/mailpace#pricing", "reviews": "https://www.anchorterminal.com/tools/mailpace#reviews", "slim": "https://www.anchorterminal.com/tools/mailpace.min.md" }, "markdown": "## Overview\n\n**Grade C · 58.4/100 · rank #750 of 1486 · #17 in Email delivery APIs · not agent-ready · confidence medium**\n\n\n## Assessment\n\nA 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## Facts\n\n| Field | Value |\n| --- | --- |\n| Vendor | OhMySMTP Ltd (https://mailpace.com) |\n| Kind | HTTP API |\n| Category | Email delivery APIs (https://www.anchorterminal.com/categories/email) |\n| Transport | HTTP |\n| Auth | API key · 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. |\n| Pricing | Paid ($10 / mo) · $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. |\n| x402 | No · 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. |\n| Licence | unknown |\n| Tools exposed | 12 |\n| Packages | npm: `@mailpace/mailpace.js` |\n| Source | https://github.com/mailpace/mailpace-mcp |\n| Docs | https://docs.mailpace.com/ |\n| llms.txt | not found |\n| Last release | 2026-10-22 |\n| GitHub stars | 1 (as of 2026-11-06) |\n| npm downloads / week | 207 |\n| Surface listed | The HTTPS API at app.mailpace.com/api/v1 (send, Domains API, Email Status API), SMTP and inbound webhooks, read from the docs repository, mailpace.com, the landing and status repositories and the MCP server source on 6 November 2026. No account was made |\n| Limits | Up to 50 recipients in the To field, no batch endpoint, 30 MB total message size per the send reference (the home page says 25 MB). Rate limits unpublished |\n| Retention | Emails shown in the dashboard for 30 days, deleted from backups 7 days later, 37 days at most, per the DPA |\n| MCP server | mailpace-mcp 2.0.0, stdio, MIT, 12 tools (send, email status, domains and domain tokens), rewritten 4 November 2026. Its README says it will be published to npm and the official MCP registry as com.mailpace/mailpace-mcp |\n| Hosting | Freethought (EU-hosted application servers and databases), Hetzner backups in Germany, AppSignal in Amsterdam, Paddle and Tutanota, per the privacy policy of 30 August 2026 |\n| Previous name | OhMySMTP until January 2022; the company is still OhMySMTP Ltd |\n| Capabilities | email.send, email.inbound, email.domains, email.analytics |\n| Tags | hosted, closed-source, smtp, webhooks, idempotency, status-page, sla, eu, mcp, typescript, ruby, go, php |\n| JSON | https://www.anchorterminal.com/api/v1/tools/mailpace.json |\n\n## Score breakdown (methodology v0.7, October 2026 research run)\n\nAssessed 2026-11-06 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. \"This run\" is each category's share of the 100 points.\n\n| Category | Weight | This run | Score (0–100) | Points |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 20 | 70 | 14.0 |\n| Performance | 10% | pending | pending | n/a |\n| Schema \u0026 documentation | 13% | 16.2 | 54 | 8.8 |\n| Agent ergonomics | 13% | 16.2 | 71 | 11.5 |\n| Security \u0026 auth | 14% | 17.5 | 50 | 8.8 |\n| Payments \u0026 pricing | 10% | 12.5 | 25 | 3.1 |\n| Task success | 10% | pending | pending | n/a |\n| Maintenance \u0026 community | 7% | 8.8 | 65 | 5.7 |\n| Transparency \u0026 trust (editorial 69, provenance 81) | 7% | 8.8 | 75 | 6.6 |\n| Negative events | up to −15 | up to −15 | none recorded | 0 |\n| **Total** | | | | **58.4 → C** |\n\n### Why each score\n\n- Reliability 70 (checked 2026-11-06): 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- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.\n- Schema \u0026 documentation 54 (checked 2026-11-06): 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- Agent ergonomics 71 (checked 2026-11-06): 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- Security \u0026 auth 50 (checked 2026-11-06): 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- Payments \u0026 pricing 25 (checked 2026-11-06): 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- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.\n- Maintenance \u0026 community 65 (checked 2026-11-06): 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- Transparency \u0026 trust 75 (checked 2026-11-06): Closed hosted service under terms that name OhMySMTP Ltd with its company number. The MCP server, SDKs, landing site and status page are MIT (18 of 30). The privacy policy (30 August 2026), the pricing page and the DPA agree on retention, 30 days in the dashboard and 7 more in backups, 37 days at most (25 of 30). The API reference promises an old version runs until a published end-of-life date, and the terms list dated changes. The terms also say changes apply immediately (8 of 20). Sub-processors listed with purpose and location, Freethought hosting in the EU, Hetzner backups in Germany, AppSignal in Amsterdam, Paddle in the UK and Tutanota in Germany (18 of 20). Total 69.\n\nFix list, everything this grade says the listing lacks, the biggest gain first (15 items). What it covers is at https://www.anchorterminal.com/fixes/mailpace.md (JSON https://www.anchorterminal.com/fixes/mailpace.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{\"listing\": \"mailpace\", \"plan\": \"read\"}`, free while the beta runs\n\n### What we couldn't check\n\n- The home page says 1,000 emails a month for under $4 a month, while the pricing page's lowest price is $10 a month for 10,000; no plan under $10 was found\n- Whether the free 100-email plan needs a card was not stated\n- Rate limit numbers are not published\n- unchecked: the MCP server's npm package and registry entry, which its README says are coming\n\n### Sources\n\n- home page and quick facts: \u003chttps://mailpace.com/\u003e (seen 2026-11-06)\n- pricing page: \u003chttps://mailpace.com/pricing\u003e (seen 2026-11-06)\n- Paddle prices the pricing page loads: \u003chttps://checkout.paddle.com/api/2.0/prices?product_ids=687241,687246\u0026customer_country=US\u003e (seen 2026-11-06)\n- docs introduction: \u003chttps://docs.mailpace.com/\u003e (seen 2026-11-06)\n- docs repository (reference, guides, history): \u003chttps://github.com/mailpace/docs\u003e (seen 2026-11-06)\n- MCP server source: \u003chttps://github.com/mailpace/mailpace-mcp\u003e (seen 2026-11-06)\n- status repository and incident issues: \u003chttps://github.com/mailpace/status/issues?q=is%3Aissue\u003e (seen 2026-11-06)\n- landing repository (terms, privacy, DPA, changelog posts): \u003chttps://github.com/mailpace/landing\u003e (seen 2026-11-06)\n- terms: \u003chttps://mailpace.com/terms\u003e (seen 2026-11-06)\n- Companies House officers: \u003chttps://find-and-update.company-information.service.gov.uk/company/13200428/officers\u003e (seen 2026-11-06)\n- official MCP registry search: \u003chttps://registry.modelcontextprotocol.io/v0/servers?search=mailpace\u003e (seen 2026-11-06)\n\n## Score history\n\nEvery move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/mailpace/history.json\n\n- 2026-11-06: graded 58.4 C (methodology 0.7)\n\n## Who's behind it (provenance 81/100, checked 2026-11-06)\n\n| Check | Finding | Points |\n| --- | --- | --- |\n| Legal entity named | OhMySMTP Ltd | 20/20 |\n| Domain age | mailpace.com, registered 2022-01-10 (4 years) | 7/15 |\n| Endpoint on the vendor's domain | mailpace.com | 15/15 |\n| Terms of service | read, states 6 of the 7 things a reader expects, and has 1 clause that costs points | 7.1/10 |\n| Privacy policy | read, states 6 of the 8 things a reader expects | 8.5/10 |\n| Status page | status.mailpace.com | 10/10 |\n| Changelog | published | 10/10 |\n| security.txt | not found | 0/10 |\n| People named | 2 named with their role, 1 with a public profile | 10/10 |\n| Support route | a support address, help pages | 5/5 |\n\nThe terms and privacy policy name OhMySMTP Ltd, incorporated in England and Wales, company number 13200428. Companies House lists two active directors.\n\nTerms last updated 9 January 2026, privacy policy 30 August 2026, DPA updated in October 2026 per the landing repository.\n\nmailpace.com/robots.txt allows all paths. The terms contain no clause on automated access to the website beyond the usual licence limits.\n\nRDAP gives mailpace.com a registration date of 10 January 2022; the service ran as OhMySMTP before that.\n\n/.well-known/security.txt returns 404 on mailpace.com and app.mailpace.com.\n\n### Terms and privacy, as read\n\nA reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.\n\n**Terms of service** (https://mailpace.com/terms), read 2026-11-06, dated 2026-01-09, states 6 of the 7 things a reader expects.\n\n- To know. Restricts automated access (costs points). \"Creation of Bot accounts;\"\n- Gives the date it was last updated. Last updated 2026-01-09.\n- Names the governing law or courts. The law of the United Kingdom of Great Britain.\n- Not found in the text. Says how changes to the terms are announced.\n- Refers to a service level or uptime commitment. Names 99% availability.\n\n**Privacy policy** (https://mailpace.com/privacy), read 2026-11-06, dated 2026-08-30, states 6 of the 8 things a reader expects.\n\n- Gives the date it was last updated. Last updated 2026-08-30.\n- Says how long data is kept. Names a period of 30 days.\n- Not found in the text. Says whether personal data is sold or shared for advertising.\n- Not found in the text. Gives a privacy contact.\n\n## Humans behind the project (researched 2026-11-06 from public pages, not part of the grade)\n\n### Key people\n\n- Paul Cleary, Founder, MailPace; director, OhMySMTP Ltd. X: https://x.com/EHLO_250\n- Harriet Cleary, Director, OhMySMTP Ltd, appointed 20 February 2026\n- Note: MailPace's current site, docs and blog name no team. Its earlier blog (The Official MailPace Blog, the blog.mailpace.com build still served on Netlify) signs the rename post of 28 January 2022 \"Written by Paul, founder of MailPace\" and links his X account. Companies House lists Paul Cleary as a director of OhMySMTP Ltd (13200428) since its incorporation on 15 February 2021, and Harriet Cleary since 20 February 2026; the terms and privacy policy name OhMySMTP Ltd. Commits to the MCP, docs and status repositories come from the GitHub account paul-oms, whose profile gives no name, so it isn't linked here. No investors or funding announcements were found on mailpace.com, its blog, the old blog or the Companies House pages, so investors are left out.\n- OhMySMTP Ltd: GitHub https://github.com/mailpace\n\n### Getting support\n\n- Support email: support@mailpace.com\n- Help: https://docs.mailpace.com/\n- Help: https://status.mailpace.com\n- Sources: https://mailpace.com/, https://mailpace.com/terms, https://mailpace.com/privacy, https://docs.mailpace.com/, https://find-and-update.company-information.service.gov.uk/company/13200428/officers, https://github.com/mailpace, https://determined-leavitt-2bc472.netlify.app/blog/ohmysmtp-is-now-mailpace, https://mailpace.com/blog/changelog/ohmysmtp-is-now-mailpace\n\n## Live (updated 2026-11-07 16:01 UTC)\n\n- Vendor status page: not read, no machine-readable status found\n- npm `@mailpace/mailpace.js` 0.1.3\n- security.txt: none\n- Watching changelog \u003chttps://mailpace.com/category/changelog\u003e\n- Watching privacy \u003chttps://mailpace.com/privacy\u003e\n- Watching terms \u003chttps://mailpace.com/terms\u003e\n- Always current: https://www.anchorterminal.com/api/v1/live/mailpace.json\n\n## Probe metrics\n\nNot measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.\n\n## Prices\n\n| Item | Price | Unit | Note |\n| --- | --- | --- | --- |\n| Scaling plan | $10 | per month (plan) | includes 10,000 emails sent or received |\n| Emails beyond 10,000 | $1 | per 1,000 emails | |\n\nAcross all listings: https://www.anchorterminal.com/prices/index.md\n\n## Strengths\n\n- Sends accept an `Idempotency-Key` header kept for 24 hours, so a retry after a timeout doesn't send twice\n- Per-domain server tokens limit a leaked key to one domain, and organisation tokens can create and revoke them by API\n- Webhooks are signed with Ed25519 and inbound mail is retried five times before it fails\n- Status page on Upptime with GitHub issues as incident reports, and a 99% monthly availability promise with credits in the terms\n- Sub-processors and their locations are listed, and mail is kept 30 days plus 7 in backups per the DPA\n\n## Weaknesses\n\n- No OpenAPI spec, llms.txt or Markdown docs for agents; the reference is Docusaurus pages\n- Rate limits aren't published; the docs say they vary by organisation age, plan and history\n- No free plan without emailing support, and the paid plan starts at $10 a month\n- MCP server 2.0.0 exists only in the repository; npm and the MCP registry had nothing for it on 6 November 2026\n- No security.txt, disclosure policy or certification found\n\n\n\n## Before you call it (notes for agents)\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## Connect\n\nFirst request:\n\n```bash\ncurl 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\"}'\n```\n\nThrough letme: https://letme.dev/mailpace. letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md\n\n## Similar tools\n\nRanked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.\n\n| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |\n| --- | --- | --- | --- | --- | --- | --- |\n| Resend API + MCP | A | 78.1 | 26 | email.send, email.inbound, email.domains, email.analytics | no | https://www.anchorterminal.com/tools/resend.md |\n| AhaSend API + MCP | BB | 75.4 | 62 | email.send, email.domains, email.analytics, email.inbound | no | https://www.anchorterminal.com/tools/ahasend.md |\n| Amazon SES | BB | 73.6 | 99 | email.send, email.inbound, email.domains, email.analytics | no | https://www.anchorterminal.com/tools/amazon-ses.md |\n| AgentMail API + MCP | BB | 72.8 | 116 | email.send, email.inbound, email.domains, email.analytics | yes | https://www.anchorterminal.com/tools/agentmail.md |\n| MailerSend | BB | 71.4 | 160 | email.send, email.inbound, email.domains, email.analytics | no | https://www.anchorterminal.com/tools/mailersend.md |\n| Mailgun API + MCP | B | 69.3 | 253 | email.send, email.inbound, email.domains, email.analytics | no | https://www.anchorterminal.com/tools/mailgun.md |\n\n## Panel reviews (0)\n\nReviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .\n\nDesk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md\n\n## Notable\n\n- Send endpoint takes an `Idempotency-Key` header, kept 24 hours per API token, so a retried send is delivered once (source: \u003chttps://docs.mailpace.com/guide/idempotency\u003e)\n- Email Status API added on 22 October 2026 returns queued, delivered, deferred, bounced or spam with the bounce response for one email (source: \u003chttps://docs.mailpace.com/reference/email-status\u003e)\n- MCP server rewritten as version 2.0.0 on 4 November 2026 with 12 tools, annotations, output schemas and an optional recipient allowlist. It isn't on npm or in the official MCP registry yet (source: \u003chttps://github.com/mailpace/mailpace-mcp\u003e)\n- No open or click tracking, by design, and only transactional mail is allowed (source: \u003chttps://docs.mailpace.com/\u003e)\n- Terms promise 99% monthly availability of the API and dashboard with a 5% credit per 30 minutes of downtime (source: \u003chttps://mailpace.com/terms\u003e)\n\n- #17 of 20 in 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## Compare\n\n- [AhaSend API + MCP vs MailPace](https://www.anchorterminal.com/compare/ahasend-vs-mailpace.md): BB 75.4 vs C 58.4\n- [Amazon SES vs MailPace](https://www.anchorterminal.com/compare/amazon-ses-vs-mailpace.md): BB 73.6 vs C 58.4\n- [Brevo API + MCP vs MailPace](https://www.anchorterminal.com/compare/brevo-vs-mailpace.md): E 42.5 vs C 58.4\n- [Cloudflare Email Service vs MailPace](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailpace.md): B 65.2 vs C 58.4\n- [Groundmail API + MCP vs MailPace](https://www.anchorterminal.com/compare/groundmail-vs-mailpace.md): B 64.5 vs C 58.4\n- [Loops API + MCP vs MailPace](https://www.anchorterminal.com/compare/loops-vs-mailpace.md): B 64.5 vs C 58.4\n- [MailerSend vs MailPace](https://www.anchorterminal.com/compare/mailersend-vs-mailpace.md): BB 71.4 vs C 58.4\n- [Mailgun API + MCP vs MailPace](https://www.anchorterminal.com/compare/mailgun-vs-mailpace.md): B 69.3 vs C 58.4\n- [Mailjet API + MCP vs MailPace](https://www.anchorterminal.com/compare/mailjet-vs-mailpace.md): C 59.6 vs C 58.4\n- [MailPace vs Mailtrap Email API + MCP](https://www.anchorterminal.com/compare/mailpace-vs-mailtrap.md): C 58.4 vs B 66.8\n- [MailPace vs Mailchimp Transactional (Mandrill)](https://www.anchorterminal.com/compare/mailpace-vs-mandrill.md): C 58.4 vs C 61.5\n- [MailPace vs Postmark API + MCP](https://www.anchorterminal.com/compare/mailpace-vs-postmark.md): C 58.4 vs B 64.9\n- [MailPace vs Resend API + MCP](https://www.anchorterminal.com/compare/mailpace-vs-resend.md): C 58.4 vs A 78.1\n- [MailPace vs Twilio SendGrid](https://www.anchorterminal.com/compare/mailpace-vs-sendgrid.md): C 58.4 vs B 68.8\n- [MailPace vs SendLayer](https://www.anchorterminal.com/compare/mailpace-vs-sendlayer.md): C 58.4 vs D 47.7\n- [MailPace vs SMTP2GO API + MCP](https://www.anchorterminal.com/compare/mailpace-vs-smtp2go.md): C 58.4 vs B 62\n- [MailPace vs Zoho CPaaS (formerly ZeptoMail)](https://www.anchorterminal.com/compare/mailpace-vs-zoho-zeptomail.md): C 58.4 vs C 58.2\n\n## Verify this listing\n\nFor the vendor. The badge or a plain link to this page verifies the listing, from a page on mailpace.com or one of its subdomains, or the README at the root of github.com/mailpace/mailpace-mcp. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{\"slug\": \"mailpace\", \"url\": \"…\"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify\n\nHTML badge:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/mailpace\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/mailpace.svg\" alt=\"MailPace on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e\n```\n\nMarkdown badge, for a README:\n\n```markdown\n[![MailPace on Anchor Terminal](https://www.anchorterminal.com/badges/mailpace.svg)](https://www.anchorterminal.com/tools/mailpace)\n```\n\nPlain link:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/mailpace\"\u003eMailPace on Anchor Terminal\u003c/a\u003e\n```\n\n## Share this listing\n\nFor the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say MailPace is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.\n\n- Dark: https://www.anchorterminal.com/assets/share/mailpace-dark.png\n- Light: https://www.anchorterminal.com/assets/share/mailpace-light.png\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": "Terminal", "url": "https://www.anchorterminal.com/tools/" }, { "name": "Email delivery APIs", "url": "https://www.anchorterminal.com/categories/email" }, { "name": "MailPace", "url": "" } ], "description": "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.", "facts": [ "rank #750 of 1486", "API key auth", "0 desk reviews" ], "h1": "MailPace", "image": "https://www.anchorterminal.com/assets/og/tools-mailpace.png", "path": "/tools/mailpace", "published": "2026-10-01", "section": "tools", "title": "MailPace review (2026): pricing, alternatives and grade C", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/tools/mailpace" }, "tokens": { "markdown": 6650, "slim": 1530 }, "version": 1 }