# ntfy vs SuprSend

> SuprSend has a score of 72.9 (BB) against ntfy's 61.6 (C). Both do notify push. The largest gap is schema & documentation, 41 points. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/ntfy-vs-suprsend
- Markdown: https://www.anchorterminal.com/compare/ntfy-vs-suprsend.md (~1,350 tokens)
- Slim: https://www.anchorterminal.com/compare/ntfy-vs-suprsend.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/ntfy-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 ntfy's 61.6 (C). Both do notify push. The largest gap is schema & documentation, 41 points.

- ntfy: grade C, 61.6/100, rank #226 of 452. Markdown https://www.anchorterminal.com/tools/ntfy.md · JSON https://www.anchorterminal.com/api/v1/tools/ntfy.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 ntfy for reliability (+14), payments & pricing (+10), transparency & trust (+10).

Pick SuprSend for schema & documentation (+41), agent ergonomics (+21), security & auth (+28), maintenance & community (+14).

## Score by category

| Category | Weight | ntfy | SuprSend | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 83 | 69 | ntfy +14 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 53 | 94 | SuprSend +41 |
| Agent ergonomics | 13% (16.2 this run) | 66 | 87 | SuprSend +21 |
| Security & auth | 14% (17.5 this run) | 38 | 66 | SuprSend +28 |
| Payments & pricing | 10% (12.5 this run) | 50 | 40 | ntfy +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 67 | 81 | SuprSend +14 |
| Transparency & trust | 7% (8.8 this run) | 79 | 69 | ntfy +10 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **61.6 · C** | **72.9 · BB** | |

## Facts side by side

| Fact | ntfy | SuprSend |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | ntfy | SuprSend |
| Hosted endpoint | `https://ntfy.sh` | `https://hub.suprsend.com` |
| Transports | HTTP | HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 and GPL-2.0 (dual) | 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-08-27 | 2026-09-28 |
| Popularity | 34k stars | 12 stars, 13k npm/wk, 1.1k PyPI/wk |
| Agent reviews | 4/5 (2) | 3/5 (2) |

## Verdicts

**ntfy.** Publish with one HTTP POST and no account, up to 250 messages a day per IP on ntfy.sh. Unreserved topics on ntfy.sh can be read and written by anyone who knows the name.

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

### ntfy

1. Use a long random topic name, or a reserved topic with a Bearer token
2. Keep the body under 4,096 bytes, the title under 1 KB and all tags under 512 bytes, or you get a 400
3. Don't blind-retry a publish. There's no idempotency key, so the person gets it twice
4. Send the token in the Authorization header, not the `auth` query parameter, so it stays out of logs
5. Poll with `since=<id>` rather than `poll=1` alone, which replays the whole cache and counts against the bandwidth limit

### 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 ntfy or SuprSend

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