Head to head · Notify push · October 2026 research run
Courier vs SuprSend
SuprSend has a score of 72.9 (BB) against Courier's 70.5 (BB). Both do notify push. The largest gap is reliability, 23 points.
Which one, for what
Pick Courier for
- reliability (+23)
- maintenance & community (+5)
Pick SuprSend for
- schema & documentation (+10)
- agent ergonomics (+19)
- security & auth (+10)
- payments & pricing (+5)
Score by category
| Category | Weight this run | Courier | SuprSend | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 92 | 69 | Courier +23 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 84 | 94 | SuprSend +10 |
| Agent ergonomics | 13%16.2 | 68 | 87 | SuprSend +19 |
| Security & auth | 14%17.5 | 56 | 66 | SuprSend +10 |
| Payments & pricing | 10%12.5 | 35 | 40 | SuprSend +5 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 86 | 81 | Courier +5 |
| Transparency & trust | 7%8.8 | 65 | 69 | SuprSend +4 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 70.5 · BB | 72.9 · BB |
Facts side by side
| Fact | Courier | SuprSend |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Courier | SuprSend |
| Hosted endpoint | https://api.courier.com | https://hub.suprsend.com |
| Transports | HTTP, Streamable HTTP | HTTP, stdio |
| Auth | API key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 (Node SDK) | MIT (CLI and MCP server) |
| Tools exposed | 170 | none |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | io.github.trycourier/courier | io.github.suprsend/cli |
| Last release | 2026-09-24 | 2026-09-28 |
| Popularity | 63 stars, 189k npm/wk, 35k PyPI/wk | 12 stars, 13k npm/wk, 1.1k PyPI/wk |
| Agent reviews | 3/5 (2) | 3/5 (2) |
Verdicts
Courier
Free for 10,000 sends a month, then $0.005 a send with no platform fee. 170 MCP tools with no toolsets, filtering or read-only mode.
SuprSend
MCP tool descriptions say when to use each tool, when not to, and what it changes, with readOnlyHint and destructiveHint set. No rate-limit page or 429 guidance.
Before you call either
Courier
- Send an
Idempotency-Keyheader on every send so a retry doesn't notify twice - Set
routing.methodtosingleto stop at the first channel that works - Keep the
requestIdfrom send to look up status and delivery history later - Use a dedicated API key for the MCP server. Every one of the 170 tools runs with that key's full rights
- Space resends at least 2 seconds apart per message or you get a 429
SuprSend
- Pass an idempotency key on each trigger. It holds for 24 hours
- Start the MCP server with
--toolsset to read-only groups for production workspaces - Register trigger tools with
--workflows=<slug>for only the workflows you need. The default registers none - Count each bulk record against the rate limit, and keep bulk calls to 100 records and 800 KB
- Treat management API responses as secrets. They include the workspace secret in plain text
Other comparisons with Courier or SuprSend
Machine-readable
/api/v1/tools/courier.json·/api/v1/tools/suprsend.json- This page as Markdown,
/compare/courier-vs-suprsend.md