# Mailjet API + MCP vs MailPace (slim)

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

- Full: https://www.anchorterminal.com/compare/mailjet-vs-mailpace.md (~4,600 tokens) · this version ~2,530 tokens · JSON https://www.anchorterminal.com/compare/mailjet-vs-mailpace.json · canonical https://www.anchorterminal.com/compare/mailjet-vs-mailpace
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Mailjet API + MCP scores 59.6 (C) on agent readiness against MailPace's 58.4 (C), and leads in 4 of 7 scored categories. MailPace leads on reliability and agent ergonomics. Both do sending email.

- Mailjet API + MCP: C 59.6, rank #694 of 1510 · https://www.anchorterminal.com/tools/mailjet.min.md
- MailPace: C 58.4, rank #754 of 1510 · https://www.anchorterminal.com/tools/mailpace.min.md
- Mailjet API + MCP, good for EU-based senders who want cheap transactional and marketing mail with data kept in the EU. Ahead on Schema & documentation, 76 against 54; Payments & pricing, 30 against 25; Maintenance & community, 79 against 65. Also A hosted endpoint, with nothing to install; Runs on your own machine; Free to start without a card.
- MailPace, good for Low-volume transactional mail from EU-hosted infrastructure with idempotent sends and no tracking. Ahead on Reliability, 70 against 62; Agent ergonomics, 71 against 53.

| Category | Mailjet API + MCP | MailPace |
| --- | --- | --- |
| Reliability (16%) | 62 | 70 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 76 | 54 |
| Agent ergonomics (13%) | 53 | 71 |
| Security & auth (14%) | 52 | 50 |
| Payments & pricing (10%) | 30 | 25 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 79 | 65 |
| Transparency & trust (7%) | 74 | 75 |

| Fact (where they differ) | Mailjet API + MCP | MailPace |
| --- | --- | --- |
| Vendor | Mailjet (Sinch) | OhMySMTP Ltd |
| Hosted endpoint | `https://api.mailjet.com/v3.1` | no (local only) |
| Transports | HTTP, stdio | HTTP |
| Pricing | Freemium | Paid |
| Licence | MIT | none |
| Tools exposed | 117 | 12 |
| llms.txt | yes | no |
| Last release | 2026-10-26 | 2026-10-22 |
| Terms last updated | no date given | 2026-01-09 |
| Privacy policy last updated | 2026-09-29 | 2026-08-30 |
| Terms restrict automated access | not found in the text | yes |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 255 stars, 177k npm/wk, 245k PyPI/wk | 1 stars, 207 npm/wk |
| Agent reviews | 2.5/5 (2) | none |

Why the edge:
- Schema & documentation, Mailjet API + MCP +22: Mailjet API + MCP 76 (Published OpenAPI files, and the MCP server bundles a 528 KB copy (25). llms.txt with about 120 links and Markdown pages (10). MCP tool descriptions are the operation summary only, and the reference describes each resource without saying when not to use it (8). Typed from OpenAPI, with Limit, Offset, Sort and countOnly parameters across GET resources (11). Status-code and error-code pages, and examples per endpoint (12). Send API v3 and v3.1 are versioned, and the releases page has dated entries, but they're product launches rather than an API changelog (10). Re-read on 4 November, llms.txt lists the API reference, guides and a Deprecated Endpoints page; release entries on the releases page stop at 3 September.); 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.)
- Agent ergonomics, MailPace +18: Mailjet API + MCP 53 (The released MCP server registers one tool for each of the 117 GET paths in its bundled spec, with no toolsets (5). Limit, Offset, Sort and countOnly on list resources, with a maximum of 1,000 results a page (15). Documented status codes and error codes with messages (14). Every MCP tool is a GET, so nothing it does can change the account. The repository's 1.2.0 (29 October 2026, no tag) adds `readOnlyHint` and `destructiveHint` annotations, but npm couldn't be read, so its release is unconfirmed and not credited. The Send API has no idempotency key (6). Official SDKs for Node, Python and other languages, one POST /v3.1/send call carries a Messages array, and the MCP needs the key and secret joined as `key:secret` (13). 5 + 15 + 14 + 6 + 13 = 53.); 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.)
- Maintenance & community, Mailjet API + MCP +14: Mailjet API + MCP 79 (node-mailjet v7.1.1 on 26 October 2026, a code fix enforcing HTTPS-only requests, 9 days before the check (30). In the 90 days from 6 August, the releases page's 3 September entry and five SDK tags at half each (node-mailjet v7.1.0 on 14 August and v7.1.1, mailjet-apiv3-python 1.8.0 on 17 August, 1.9.0 on 14 September and 1.9.1 on 8 October), 3.5 in all (20). The MCP repository merges pull requests, and its README asks users to file an issue if npm and GitHub diverge. We couldn't see issue reply times (8). Node and Python SDKs released in the last 10 and 27 days (15). CI runs the tests, but the MCP repository's package.json says 1.2.0 while its git tags stop at v1.1.0-beta.1, and npm couldn't be read (6). 30 + 20 + 8 + 15 + 6 = 79.); 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.)
- Reliability, MailPace +8: Mailjet API + MCP 62 (Statuspage at mailjet.statuspage.io with history back to 2023, read through its history.atom feed (20). In the 90 days from 6 August the feed has two entries. A planned hour of infrastructure maintenance on 23 September, during which logins and API and SMTP sends were unavailable and submitted mail waited in the queue, and a Microsoft incident on 4 September that deferred mail to M365 only, with other providers unaffected. Both read as minor (20). The rate-limit page, unchanged on 4 November, says transactional endpoints have a high limit and others a 'much lower' one, with no numbers (0). A 429 on excess and advice to wait and retry, but no Retry-After header and no idempotency key for sends. SandboxMode validates a send without delivering (7). Enterprise plans list a 'Service Level Agreement' with no published terms, per the 1 October check, not re-read on 4 November (5). GA (10). 20 + 20 + 0 + 7 + 5 + 10 = 62.); 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.)
- Payments & pricing, Mailjet API + MCP +5: Mailjet API + MCP 30 (No x402, MPP or L402 (0). Plan prices are public, but the price per extra 1,000 emails sits behind a help-centre link rather than on the pricing page (10). Free plan of 6,000 emails a month, 200 a day, with no card (20). Browser signup, no autonomous route (0).); 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.)