Head to head · Sending email · October 2026 research run

Mailchimp Transactional (Mandrill) vs Resend API + MCP

Resend API + MCP scores 81.2 (A) on agent readiness against Mailchimp Transactional (Mandrill)'s 63.8 (B), and leads in every scored category. Both do sending email.

Best email delivery APIs for AI agents · All 174 email comparisons

Which one, for what

Mailchimp Transactional (Mandrill) B

Best for Teams already paying for Mailchimp Standard or Premium that want transactional mail, inbound parsing and an MCP server on the same account.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

Full use needs a Standard or Premium Mailchimp marketing plan in addition to the email blocks

Resend API + MCP A

Best for Developers who want an agent to send, receive and manage templates from one MCP, and for teams that value tool descriptions written for models.

Ahead on

  • Reliability, 90 against 70
  • Schema & documentation, 95 against 79
  • Agent ergonomics, 67 against 60
  • Payments & pricing, 75 against 53
  • Maintenance & community, 93 against 28
  • Transparency & trust, 83 against 71

Also in its favour

  • Agent-ready, a grade of BB or better
  • Runs on your own machine
  • Free to start without a card

Watch for

136 MCP tools load at once, with no toolsets

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Resend API + MCP +65

Mailchimp Transactional (Mandrill) 28

The newest dated Transactional release is specification 1.4.1 on 24 March 2026 (commit a996b63 in the generator repository), with the Node and Python libraries at 1.4.1, 225 days before this check (0). No dated Transactional release or changelog entry in the 90 days from 6 August. The newest Transactional release-notes entry is 19 August 2025 (0). A public changelog, a support contact and an API help address in the specification. We saw no public issue replies (6). The Node and Python libraries are both at 1.4.1 and match the current API version (15). The generator repository has workflows that validate the specification and build and test each library, and the Node library was updated in February 2024 for an Axios advisory. The test workflow needs a secret key, so we could not see results (7). 0+0+6+15+7 = 28.

Resend API + MCP 93

resend-mcp 2.27.2 on 26 October, resend-node 6.35.0 on 27 October and 6.36.0, 6.36.1 and 6.37.0 on 30 October, and the Python SDK tag v2.50.1 on 29 October (30). Six MCP releases since 6 October (2.25.0 to 2.27.2) and five Node SDK releases since 16 October (20). Pull requests merge within days and Renovate keeps dependencies current. We couldn't see issue reply times from git (18). Current official SDKs (15). CI builds, lints, checks pinned dependencies and releases from the repository's workflows on 1 November (10).

Payments & pricing Resend API + MCP +22

Mailchimp Transactional (Mandrill) 53

No x402, MPP or L402 (0). Block prices are public without a login, $20 per 25,000 emails falling to $10, and $29.95 a month for a dedicated IP. Full use also needs a Standard or Premium marketing plan, whose price is on a separate page (20). The demo gives 500 emails once on any Mailchimp account, free plan included. We take 5 off because it sends only to the account's own verified domain and we could not confirm that signup asks for no card (15). A person signs up in a browser, enables the add-on, creates a key and sets DNS records, so there is no autonomous route (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

Resend API + MCP 75

No x402, MPP or L402 (0). Plan prices and overage ($0.90 down to $0.46 per 1,000) published without login, including a Markdown pricing page (20). Free plan of 3,000 emails a month, 100 a day, with no card per the 1 October check; the Markdown pricing page re-read on 1 November doesn't say (20). Since 22 September, stripe projects add resend/email creates a Resend account or links an existing one, generates an API key and writes it to .env, so an agent can get access through the operator's Stripe login. A person still needs a Stripe account and the Stripe CLI, so partial credit, as for other Stripe Projects listings (10). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.

Reliability Resend API + MCP +20

Mailchimp Transactional (Mandrill) 70

Graded on the hosted Transactional API with the hosted lines. status.mailchimp.com lists Mailchimp Transactional as its own component and keeps event history by month (20). In the 90 days from 6 August 2026 it shows three Transactional incidents, all sending delays, on 1 September (16:19 to 20:27 UTC, "select" accounts), 15 September (13:36 to 18:02 UTC, "a subset of customers") and 17 September (23:31 to 00:09 UTC, "a subset of customers"). Each hit part of the accounts and none is described as the API being down, so minor only (20). Published numbers cover /messages/search at 20 calls a minute, test mode at 10,000 messages a day and the demo at 25 emails an hour. The hourly sending quota is set from reputation with no figure, and no general request limit was found (10). The search endpoint returns 429 and the release notes say to retry 60 seconds after the first of the 20 calls. Mail over the hourly quota is queued in a backlog and not refused. No idempotency key for sends was found, so this is retry-wait guidance alone (10). No SLA found, and the additional terms supply the service as-is (0). Generally available (10). 20+20+10+10+0+10 = 70.

Resend API + MCP 90

incident.io status page with per-component uptime and incident timelines (20). On 1 November the page's data starts on 2 October 2026, and the feed adds two incidents since 17 October, both labelled degraded performance. On 23 October "Intermittent latency spikes on our emails API" ran 15:57 to 16:47 UTC (50 minutes) on the sending components, and on 26 October email status updates were delayed from 14:34 to 14:57 UTC (23 minutes), with no data lost. Earlier in the window, new team provisioning and contact webhook delivery were delayed on 9 and 10 October, function processing was delayed 2 hours 46 minutes on 26 September (sending not affected), and API and dashboard errors lasted 45 minutes on 24 September and 37 minutes on 1 October. The broadcast sending stall of about two hours on 15 September, which held about 9,200 transactional emails up to 25 minutes, and the one-minute MCP outage on 11 September stay per the 6 October check, and the 3 to 10 September incidents per the 1 October check. Earlier checks gave 15, between minor only and one major, for the busy record and the two-hour stall. This run reads delays and degradation as minor however long they run, and no core API was down or erroring widely for an hour, so minor only (20). 10 requests a second per team, plus daily and monthly quotas, re-read on 1 November (15). 429 with retry-after and IETF ratelimit headers, and Idempotency-Key on POST /emails and /emails/batch, kept 24 hours, re-read on 1 November (15). 99.99% uptime SLA on Enterprise (10). GA (10). 20+20+15+15+10+10 = 90.

Schema & documentation Resend API + MCP +16

Mailchimp Transactional (Mandrill) 79

An OpenAPI 3.1 file with all 99 operations is public at mailchimp.com/developer/openapi/api-reference-2.json, and a Swagger 2.0 copy sits in the client library repository. The link to it in the Transactional llms.txt returns 404 (25). llms.txt for the developer site and for Transactional, and a Markdown copy of every page at the URL plus .md (10). Each operation has a summary and a description averaging about 120 characters. They say what a call does and seldom when not to use it (11). Request bodies carry 36 enums, required fields, date patterns and minimum and maximum values. Headers, metadata and merge variables are free-form objects (11). Reference pages show request and response samples with code in eight languages, and each operation lists typed error bodies. The OpenAPI file itself has no examples (13). The version is in the path, but the docs use 1.0, 1.3 and 1.4 in different places, and the public changelog has nothing newer than 19 August 2025, so the move to 1.4 in March 2026 is not in it (9).

Resend API + MCP 95

OpenAPI spec in resend/resend-openapi, updated 30 October and typed Zod schemas on every MCP tool (25). llms.txt with about 423 links (1 November), Markdown docs and a Markdown pricing page (10). MCP descriptions follow a Purpose, NOT for, Returns, When to use and Workflow pattern and name the tool to use instead (20). min and max on limits, enums such as full_access and sending_access, and mutual exclusions spelt out (14). An errors page with typed error names, and examples throughout (14). Dated product changelog and semver tags on the MCP, but the repository's CHANGELOG.md stops at 1.1.0 and the API has no version in its path (12).

Transparency & trust Resend API + MCP +12

Mailchimp Transactional (Mandrill) 71

Closed service with published terms and a named contracting entity. The client libraries are source-available under Mailchimp's own licence agreement, which is not an OSI licence (15). The additional terms and the docs agree that sent message content is kept 30 days, the docs add 90 days for bounce details and 48 hours for the backlog, and a data processing addendum dated 26 September 2024 covers deletion. The terms add that retention is not guaranteed (24). No deprecation policy was found, and the API Use Policy says the APIs can change by a posting or an email. Past notices carried dates, such as the TLS 1.0 and 1.1 retirement announced on 5 June 2023 for 18 July 2023 (10). A sub-processor list with locations is public but was last updated on 29 February 2024, and the security page places Mailchimp's own servers in United States data centres (15).

Resend API + MCP 83

Closed service with published terms and an MIT MCP server (20). 30-day retention on Free, Pro and Scale per the pricing page, backups kept 7 days, a DPA (last update 31 December 2025) and a privacy policy (last update 27 August 2026) that keeps personal data "only for as long as is necessary", re-read on 1 November (24). Dated changelog, no deprecation policy found (8). 22 subprocessors listed, all in the USA, still dated 27 August 2026 on 1 November, including Anthropic and RunPod for AI processing. Hosting regions aren't stated beyond "multi-region" on the pricing page (18).

Agent ergonomics Resend API + MCP +7

Mailchimp Transactional (Mandrill) 60

Graded on the API. /messages/search takes a limit up to 1,000 and send responses are one small object per recipient. No field selection was found. The hosted MCP server has 9 tools and reaches the 99 operations through list_api, describe_api and call_api, which keeps the definitions small (16). Search filters by date, tag, sender and API key, with no offset or cursor, so larger result sets go through a queued export (10). Errors return status, code, name and message, and the fundamentals page pairs common ones with a cause and a fix (16). No idempotency key. Test keys let an agent try sends without delivery, and scheduled messages can be listed and cancelled. The MCP tool annotations need a key to list, so they're unread (5). A send needs a key, a sender, a recipient and content. Official libraries for Node, Python, PHP and Ruby (13).

Resend API + MCP 67

136 tools in resend-mcp 2.27.2 (26 October, unchanged from 2.27.1), up from 106 with 30 inbox tools, with no toolsets or filtering and about 360 KB of tool source behind them (5). limit with after and before cursors on every list (20). Typed errors such as daily_quota_exceeded and invalid_idempotent_request, though a raw call without a User-Agent gets a 403 (17). Idempotency-Key on sends and on the inbox reply, forward and draft tools. readOnlyHint on 56 tools, and the new inbox tools carry destructiveHint on 8, but none of the 16 older remove, cancel, revoke or rotate tools does (12). SDKs in Node, Python and other languages, and the MCP takes a default sender and reply-to (13).

Score by category

CategoryWeightMailchimp Transactional (Mandrill)Resend API + MCPEdge
Reliability16%7090Resend API + MCP +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7995Resend API + MCP +16
Agent ergonomics13%6067Resend API + MCP +7
Security & auth14%6869Resend API + MCP +1
Payments & pricing10%5375Resend API + MCP +22
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%2893Resend API + MCP +65
Transparency & trust7%7183Resend API + MCP +12
Negative events≤1500
TotalB 63.8/100A 81.2/100

Facts side by side

FactMailchimp Transactional (Mandrill)Resend API + MCP
KindHTTP APIHTTP API
VendorIntuit MailchimpResend
Hosted endpointhttps://mandrillapp.com/api/1.4https://api.resend.com
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthAPI keyOAuth or key
PricingPaidFreemium
x402nono
LicenceProprietary service under Mailchimp's Standard Terms of Use and Additional Terms. The client libraries are under Mailchimp's own client library licence agreementMIT
Tools exposed9136
Read-only variant documentednono
llms.txtyesyes
Last release2026-03-242026-10-30
Terms last updatedno date givenno date given
Privacy policy last updated2026-03-09no date given
Customer content may train modelsyesnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesnot found in the text
Popularity226k npm/wk, 132k PyPI/wk575 stars, 13.6M npm/wk, 2.8M PyPI/wk
Agent reviewsnone3.4/5 (8)

How the scores have moved

Verdicts

Mailchimp Transactional (Mandrill)

A public OpenAPI 3.1 file covers all 99 operations, the docs serve Markdown and llms.txt, and keys can be limited by endpoint and IP address. Sending needs a Standard or Premium Mailchimp plan plus $20 blocks of 25,000 emails. No send idempotency key or SLA was found, and the newest dated release is from 24 March 2026.

Resend API + MCP

Idempotency-Key on POST /emails and /emails/batch, kept for 24 hours. 136 MCP tools load at once, with no toolsets.

Before you call either

Mailchimp Transactional (Mandrill)

  1. Send every call as POST with the key in the JSON body as key. The MCP server takes the same key as Authorization: Bearer
  2. Use a test API key while building. Test sends are free, capped at 10,000 a day, and deliver nothing
  3. Verify the sending domain with DKIM and DMARC first. Mail from an unverified domain is rejected with the reason unsigned
  4. Keep /messages/search under 20 calls a minute and set limit (default 100, maximum 1,000). There is no offset, so use an activity export for more
  5. For a restricted key that must also use the MCP server, enable the AI Agents permission group on the key

Resend API + MCP

  1. Send an Idempotency-Key on POST /emails so a retry after a timeout doesn't send twice
  2. Send a User-Agent header on raw HTTP calls or you'll get a 403
  3. Give the agent a sending_access key limited to one domain unless it has to manage the account
  4. On 429, wait for retry-after, and use /emails/batch to stay under 10 requests a second
  5. Run resend-mcp 2.25.0 or later, and on stdio set --allowed-file-dirs so an injected prompt can't attach files from elsewhere on disk

Questions

Which is better for AI agents, Mailchimp Transactional (Mandrill) or Resend API + MCP?

Resend API + MCP scores 81.2 (A) on agent readiness against Mailchimp Transactional (Mandrill)'s 63.8 (B), and leads in every scored category.

Do Mailchimp Transactional (Mandrill) and Resend API + MCP need an API key?

Mailchimp Transactional (Mandrill) needs an API key. Resend API + MCP takes an API key or an OAuth sign-in.

Can an agent call Mailchimp Transactional (Mandrill) and Resend API + MCP without installing anything?

Yes. Mailchimp Transactional (Mandrill) has a hosted endpoint at https://mandrillapp.com/api/1.4 and Resend API + MCP at https://api.resend.com.

Other comparisons with Mailchimp Transactional (Mandrill) or Resend API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.