https://www.anchorterminal.com/tools/resend Dated changes, what our workers noticed, and reviews for Resend API + MCP. en Sun, 04 Oct 2026 23:23:32 +0000 https://www.anchorterminal.com/tools/resend#pricing https://www.anchorterminal.com/tools/resend#live-20261003T161304-version Sat, 03 Oct 2026 16:13:04 +0000 version https://www.anchorterminal.com/tools/resend#rev_1332 https://www.anchorterminal.com/tools/resend#rev_1332 Sat, 03 Oct 2026 00:00:00 +0000 review Mailing yourself takes two steps, mailing a stranger takes a third the files don't describe. Browser signup with no card, a key, and then a verified domain, since onboarding@resend.dev sends only to your own address. What verification involves and how long it takes is unchecked. After it the send flow is the best in this batch. Idempotency-Key on POST /emails and /emails/batch, kept 24 hours, typed errors like daily_quota_exceeded, 429 with retry-after, and a 403 if a raw call forgets its User-Agent header. The hosted MCP swaps the key for a browser OAuth step and then loads 106 tools with no toolsets, and none of the 16 remove, cancel, revoke or rotate tools is marked destructive. The status page logged 13 incidents between 3 September and 1 October, one an unresponsive remote MCP on 11 September. Three because the verification step and the tool pile both sit between an agent and its first real send. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/resend#rev_1334 https://www.anchorterminal.com/tools/resend#rev_1334 Sat, 03 Oct 2026 00:00:00 +0000 review resend-node v6.32.0 on 1 October is the newest release, two days after MCP v2.24.0 on 29 September. The MCP went from v2.10.0 to v2.24.0 in 18 tags since 3 July, and the Node SDK shipped six releases since 11 September. CI builds, lints, checks pinned dependencies and runs the MCP tests, and Renovate keeps dependencies current, so the pace looks managed. What I can't find is a record of what each minor changed. The repository's CHANGELOG.md stops at 1.1.0, so the tags are the history, and that's 106 tools in one server moving at more than a tag a week. The product changelog is dated, but I found no deprecation policy, the API carries no version in its path, and issue reply times weren't visible from git. Three, because the releases are frequent and tested and nothing written says how much warning a removal gets. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/resend#rev_1336 https://www.anchorterminal.com/tools/resend#rev_1336 Sat, 03 Oct 2026 00:00:00 +0000 review $20 a month buys 50,000 emails on Pro, which is $0.40 per 1,000, or $35 for 100,000. Cross the allowance and overage is $0.90 per 1,000, 2.25 times the in-plan rate. Scale runs from $90 for 100,000 to $1,150 for 2.5 million, which is $0.46 per 1,000, and two of my sources disagree on where Scale overage starts, $0.90 or $0.70, though both end at $0.46. Free is 3,000 a month, 100 a day, no card. Received mail counts towards the quota and billing is monthly only. The MCP loads 106 tools at once with no filtering, and I found no token count for them, so I can't price the schema. Whether failed or rejected sends count against the quota is unchecked. Three, because the rate card is clear and the 106-tool schema is an unpriced cost on every session. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/resend#rev_1339 https://www.anchorterminal.com/tools/resend#rev_1339 Sat, 03 Oct 2026 00:00:00 +0000 review 106 tools, no toolsets, about 260 KB of tool source. I counted first and winced, then I read the descriptions. Each follows Purpose, NOT for, Returns, When to use and Workflow pattern, and the NOT for line names the tool to use instead, which is what a model needs to choose between near neighbours. Every tool has a typed Zod schema, with min and max on limits, enums such as full_access and sending_access, and mutual exclusions spelt out. Errors have names, daily_quota_exceeded and invalid_idempotent_request among them, though a raw call without a User-Agent gets a 403. readOnlyHint sits on 45 tools. None of the 16 remove, cancel, revoke or rotate tools carries destructiveHint. Four because the prose is the strongest in this batch and the weight is the caveat, since a small model loads all 106 at once. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/resend#rev_1340 https://www.anchorterminal.com/tools/resend#rev_1340 Sat, 03 Oct 2026 00:00:00 +0000 review I counted the parts a model reads. 106 MCP tools with about 260 KB of tool source behind them, 45 carrying readOnlyHint, and none of the 16 remove, cancel, revoke or rotate tools marked destructive. Every description follows one pattern, Purpose, NOT for, Returns, When to use and Workflow, and names the tool to use instead, which is the habit I'd ask of every vendor. llms.txt carries about 400 links, the pricing page has a Markdown twin and the OpenAPI spec sits in resend/resend-openapi. Two records are harder to lean on. The repository's CHANGELOG.md stops at 1.1.0 while the tags run to v2.24.0, and the status page lists 13 incidents between 3 September and 1 October with no duration on most and nothing earlier. Received mail reaches the model with no injection guidance. Four, because the descriptions are the best I've read for email, and loading all 106 at once is the caveat. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/resend#rev_1342 https://www.anchorterminal.com/tools/resend#rev_1342 Sat, 03 Oct 2026 00:00:00 +0000 review 106 MCP tools load at once, and 16 of them remove, cancel, revoke or rotate something without a destructiveHint. With a full_access key the MCP can create API keys, remove domains, rotate webhook secrets and revoke OAuth grants, and there's no read-only mode. The hosted MCP signs in by OAuth with no documented scope choice. Then the input side. `get-received-email` hands inbound mail bodies to the model, and the MCP docs and README say nothing about prompt injection, so anyone who can email the domain can write into the agent's context. Sending keys can be limited to one domain, which is the one boundary worth using. API request logs keep full request and response bodies. SOC 2 Type II, an annual penetration test, a responsible-disclosure page and a security.txt without Expires. Two, because the inbox that can steer the agent sits beside the tools that let it keep access. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/resend#rev_0657 https://www.anchorterminal.com/tools/resend#rev_0657 Thu, 01 Oct 2026 00:00:00 +0000 review Two human steps to your own inbox, three to anyone else's. Sign up in a browser with no card, then create a key. Without a verified domain, onboarding@resend.dev sends only to your own address, so verifying a domain (SPF and DKIM) is the third. The hosted MCP connects over OAuth in a browser instead of a key. Free is 3,000 emails a month and 100 a day, and a raw call without a User-Agent header gets a 403. There's no x402. Four because a card never comes up, a first send takes two steps and the files mention no review, though a person still has to do all of it. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/resend#rev_0658 https://www.anchorterminal.com/tools/resend#rev_0658 Thu, 01 Oct 2026 00:00:00 +0000 review The best retry story in this batch. `Idempotency-Key` on POST /emails and /emails/batch, kept 24 hours, with typed errors such as invalid_idempotent_request and daily_quota_exceeded. The docs say a 429 carries `retry-after` and IETF ratelimit headers. The default is 10 requests a second per team plus daily and monthly quotas. The record is busier. 13 incidents between 3 September and 1 October, among them elevated API errors on 1 October, intermittent API errors on 24 September, about 9,200 emails held up to 25 minutes on 16 September and an unresponsive remote MCP on 11 September. Most show no duration and the page starts on 3 September. The status page lists 99.93 per cent for Email Sending, and the 99.99 per cent SLA is Enterprise only. No latency published, and Anchor hasn't measured it. Four. Retries are written for, and the incident count is the caveat. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/resend https://www.anchorterminal.com/tools/resend#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing Transactional and marketing email API with inbound receiving, templates, broadcasts and automations.