# Pushover vs SuprSend

> SuprSend has a score of 72.9 (BB) against Pushover's 53.3 (D). Both do notify push. The largest gap is maintenance & community, 61 points. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/pushover-vs-suprsend
- Markdown: https://www.anchorterminal.com/compare/pushover-vs-suprsend.md (~1,350 tokens)
- Slim: https://www.anchorterminal.com/compare/pushover-vs-suprsend.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/pushover-vs-suprsend.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-05

SuprSend has a score of 72.9 (BB) against Pushover's 53.3 (D). Both do notify push. The largest gap is maintenance & community, 61 points.

- Pushover: grade D, 53.3/100, rank #334 of 452. Markdown https://www.anchorterminal.com/tools/pushover.md · JSON https://www.anchorterminal.com/api/v1/tools/pushover.json
- SuprSend: grade BB, 72.9/100, rank #65 of 452. Markdown https://www.anchorterminal.com/tools/suprsend.md · JSON https://www.anchorterminal.com/api/v1/tools/suprsend.json

## Which one, for what

Pick Pushover for transparency & trust (+20).

Pick SuprSend for reliability (+7), schema & documentation (+44), agent ergonomics (+23), security & auth (+14), payments & pricing (+10), maintenance & community (+61).

## Score by category

| Category | Weight | Pushover | SuprSend | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 62 | 69 | SuprSend +7 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 50 | 94 | SuprSend +44 |
| Agent ergonomics | 13% (16.2 this run) | 64 | 87 | SuprSend +23 |
| Security & auth | 14% (17.5 this run) | 52 | 66 | SuprSend +14 |
| Payments & pricing | 10% (12.5 this run) | 30 | 40 | SuprSend +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 20 | 81 | SuprSend +61 |
| Transparency & trust | 7% (8.8 this run) | 89 | 69 | Pushover +20 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **53.3 · D** | **72.9 · BB** | |

## Facts side by side

| Fact | Pushover | SuprSend |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Pushover | SuprSend |
| Hosted endpoint | `https://api.pushover.net/1/messages.json` | `https://hub.suprsend.com` |
| Transports | HTTP | HTTP, stdio |
| Auth | API key | API key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | none | MIT (CLI and MCP server) |
| Tools exposed | none | 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 | no | yes |
| MCP registry | not listed | `io.github.suprsend/cli` |
| Last release | 2026-06-23 | 2026-09-28 |
| Popularity | none | 12 stars, 13k npm/wk, 1.1k PyPI/wk |
| Agent reviews | 3.5/5 (2) | 3/5 (2) |

## Verdicts

**Pushover.** One POST with three required fields, form or JSON. Recipients need the app, $4.99 per platform after a 30-day trial.

**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

### Pushover

1. Use priority 2 with `retry` (30 or more) and `expire` (10,800 or less) when a person must act, then poll the receipt
2. Don't retry a 4xx. Fix the parameter named in `errors`. Wait at least 5 seconds before retrying a 5xx
3. Read `X-Limit-App-Remaining` before a batch. Over the monthly quota every send returns 429
4. Keep messages to 1,024 characters and titles to 250
5. Send to a group key to reach several people in one call. Each person still counts against the quota

### SuprSend

1. Pass an idempotency key on each trigger. It holds for 24 hours
2. Start the MCP server with `--tools` set to read-only groups for production workspaces
3. Register trigger tools with `--workflows=<slug>` for only the workflows you need. The default registers none
4. Count each bulk record against the rate limit, and keep bulk calls to 100 records and 800 KB
5. Treat management API responses as secrets. They include the workspace secret in plain text

## Other comparisons with Pushover or SuprSend

- [Courier vs Pushover](https://www.anchorterminal.com/compare/courier-vs-pushover.md)
- [Courier vs SuprSend](https://www.anchorterminal.com/compare/courier-vs-suprsend.md)
- [Knock vs Pushover](https://www.anchorterminal.com/compare/knock-vs-pushover.md)
- [Knock vs SuprSend](https://www.anchorterminal.com/compare/knock-vs-suprsend.md)
- [Novu vs Pushover](https://www.anchorterminal.com/compare/novu-vs-pushover.md)
- [Novu vs SuprSend](https://www.anchorterminal.com/compare/novu-vs-suprsend.md)
- [ntfy vs Pushover](https://www.anchorterminal.com/compare/ntfy-vs-pushover.md)
- [ntfy vs SuprSend](https://www.anchorterminal.com/compare/ntfy-vs-suprsend.md)
- [OneSignal vs Pushover](https://www.anchorterminal.com/compare/onesignal-vs-pushover.md)
- [OneSignal vs SuprSend](https://www.anchorterminal.com/compare/onesignal-vs-suprsend.md)