Brevo API + MCP vs MailPace

Brevo API + MCP 83

The official Node SDK released 6.1.0 on 13 October and 6.2.0 on 16 October 2026, and the Python SDK 5.1.0 on 13 October, regenerated from the API with new OAuth and other endpoints, not dependency-only (30). API changelog entries on 13 and 14 August and 2 and 3 September per the 1 October check, plus the three SDK tags at half (20). Public changelog and support. We couldn't see reply times (10). Node 6.2.0 and Python 5.1.0, generated with Fern, released in October (15). The Node SDK runs CI, but its repository has no licence file while package.json lists one to publish (8).

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.

Brevo API + MCP 55

incident.io status page with 31 components (per the 1 October check, not re-read on 5 November because Brevo's terms bar robots and intelligent agents from navigating its site) (20). On 1 October the history showed 'Multiple services impacted' incidents marked as full outages on 17 and 25 September, inside the 90 days from 7 August, and eight since 4 July. The page doesn't show durations or which services each one hit, and the status page couldn't be re-read for October, so the recorded award is carried (0). Published limits per endpoint and plan, 1,000 requests a second for sends and 100 an hour for most other endpoints (15). 429 with rate-limit headers, and the official SDKs retry 408, 429 and 5xx twice and respect Retry-After. No idempotency key for sends found (10). Brevo's Terms of Service (version of 1 October 2025) include an appendix titled Service Level Agreement in which Brevo will endeavour to maintain an average monthly availability of 99.8 per cent of the Software, with no credit or other remedy, and section 5.5 says the service comes as is and as available. A target with no commitment or credit isn't an SLA, as for Manatal's stated uptime with discretionary refunds (0). GA (10).

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.

Brevo API + MCP 65

27 per-module MCP servers let a client load only contacts, templates or another module rather than the combined server, per the 1 October check, not re-read on 5 November because Brevo's terms bar robots and intelligent agents from navigating its site (18). limit, offset and sort on list endpoints (15). Errors map to typed classes in the SDKs. We didn't check for an error-code reference (12). No idempotency key on POST /v3/smtp/email, and we couldn't see tool annotations on the closed MCP (5). Node and Python SDKs among others, and a send needs sender, to, subject and content (15).

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.

Brevo API + MCP 30

No x402, MPP or L402 (0). Plan entry prices are public per the 30 September check, but the page loads them by script and the pay-as-you-go credit price needs the calculator, per the 1 October check, not re-read on 5 November because Brevo's terms bar robots and intelligent agents from navigating its site (10). Free plan of 300 emails a day with no card, once Brevo approves the account (20). Browser signup and approval, 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.