Head to head · Push notifications · October 2026 research run

Pushover vs SuprSend

SuprSend scores 75.4 (BB) on agent readiness against Pushover's 55 (C), and leads in 6 of 7 scored categories. Pushover leads on transparency & trust. Both do push notifications.

Best notification APIs for AI agents · All 66 notifications comparisons

Which one, for what

Pushover C

Best for An agent that must reach its owner or an on-call team and get an acknowledgement.

Ahead on

  • Transparency & trust, 87 against 73

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

Watch for

Recipients need the app, $4.99 per platform after a 30-day trial

SuprSend BB

Best for A SaaS team that needs tenant-aware preferences, digests and batching at a mid-range price, and for teams that want an agent to read delivery data and edit drafts through a hosted MCP server.

Ahead on

  • Reliability, 69 against 62
  • Schema & documentation, 94 against 50
  • Agent ergonomics, 85 against 64
  • Security & auth, 66 against 52
  • Payments & pricing, 60 against 45
  • Maintenance & community, 81 against 20

Also in its favour

  • Agent-ready, a grade of BB or better
  • Runs on your own machine

Watch for

No rate-limit page or 429 guidance

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 SuprSend +61

Pushover 20

The last published API change is still the 23 June 2026 blog post deprecating the GitHub notification endpoint, the newest post on 4 November, 134 days before this check (10). No releases or dated changes in the 90 days from 6 August (0). A blog with dated product notices and a support site, with no public issue tracker (10). No official SDKs or MCP server (0). No packages to grade (0). 10+0+10+0+0 = 20.

SuprSend 81

Changelog entry on 12 October 2026 (the hosted MCP launch), CLI 1.1.1 tagged on 22 October and com.suprsend/mcp 0.5.11 published to the MCP registry on 30 October (30). Nine dated changelog entries from 4 August to 12 October, CLI 1.1.0 and 1.1.1 and 24 registry versions of the hosted server from 3 to 30 October (20). A closed service with a busy changelog. We didn't check the CLI repo's issues or support response (11). The hosted server is in the official MCP registry as com.suprsend/mcp, active, and the old io.github.suprsend/cli entry is marked deprecated since 13 October (15). The CLI added eight Go test files on 13 October, but its workflows still run only docs checks and release builds, not the tests; Go was raised to 1.27.3 for a crypto/x509 fix on 22 October (5). 30 + 20 + 11 + 15 + 5 = 81.

Schema & documentation SuprSend +44

Pushover 50

No OpenAPI or other machine-readable contract (0). No llms.txt and no Markdown docs (0). The single API page explains every parameter and when to use emergency priority, receipts and groups (16). Parameters are documented with limits (message 1,024 characters, title 250, URL 512, attachment 5 MB) and enumerated priorities and sounds, sent as form fields or JSON (11). Examples and an error example with status, errors and request fields (13). A /1/ version in the path and product changes announced on the blog, with no changelog as such (10). Re-read on the API and pricing pages on 4 November, unchanged.

SuprSend 94

Public OpenAPI file (openapi.yaml, version 1.2.2, 96 paths, last changed 26 October 2026) (25). llms.txt answered on 1 November, and the docs are Markdown in a public repository (10). The hosted MCP overview says when to use the server and when not to (product notifications belong in code, CI/CD belongs in the CLI), the tool list gives each tool's purpose and whether it reads, writes or sends, and the CLI tool definitions say when to use each tool and what it changes (20). Typed inputs with required fields and enumerated actions, though workflow data is a free-form object (12). Examples throughout, a management API errors page with error_code and type, and per-record errors on bulk 207 responses (12). A dated changelog, nine entries from 4 August to 12 October 2026, and a CLI changelog (15). 25 + 10 + 20 + 12 + 12 + 15 = 94.

Agent ergonomics SuprSend +21

Pushover 64

Responses are a few fields, status and request, plus receipt for emergency messages (22). Little to page or filter, though a limits endpoint and the receipts API let an agent check state without guessing (10). Errors return an errors array naming the bad parameter, and the docs say which statuses to retry (18). No idempotency key, but emergency receipts can be polled and cancelled (6). Three required fields and sensible defaults, but no official SDKs (8). Re-read on the API and pricing pages on 4 November, unchanged.

SuprSend 85

The hosted MCP server at mcp.suprsend.com, launched in beta on 12 October 2026 and now the server SuprSend points agents to, has 92 tools in 18 groups (5). A ?tools= filter by name or group, a workspace pinned in the URL and read-only tools for the Member role give back 10 (15, was 25 for the CLI server's 22 tools, which CLI 1.1.0 deprecated). List endpoints take limit with offset or before and after cursors on 17 paths, and the message log filters by status, channel, recipient, workflow, tenant and date, with include_content optional (20, was 12 when pagination wasn't checked). Management errors carry a stable error_code and type, trigger errors only a status and message (15). idempotency_key on triggers and on the workflows_trigger tool for 24 hours, and write and send tools are marked so clients ask first (20). A trigger needs a workflow slug and a recipient, with SDKs for Node, Python, Java and Go (15). 15 + 20 + 15 + 20 + 15 = 85.

Payments & pricing SuprSend +15

Pushover 45

No x402, MPP or L402 (0). Prices are public but per licence and seat, $4.99 once per platform or $5 per user a month for Teams, and capacity upgrades aren't priced on the page (10). A 30-day trial of the app and 10,000 free messages a month without a card (20). A person has to create an account and install the app to get a user key (0). Re-read on the API and pricing pages on 4 November, unchanged. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

SuprSend 60

No x402, MPP or L402 (0). Overage at $2 per 1,000 on Essentials and $5 per 1,000 on Business, published without login (20). Free plan with 10,000 notifications a month and "No Credit Card required" (20). A person signs up in the dashboard, and the hosted MCP signs in with that account (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Security & auth SuprSend +14

Pushover 52

An application token and a user or group key, sent in the POST body rather than a header. An app token can only send, not read (18). No read access through the sending API, and group keys let you limit who receives (12). The sending API returns no untrusted content (10). Receipts for emergency messages and the limits endpoint, but no per-call log for the operator (6). security.txt valid on 4 November, with a security mailbox and an Expires date of 2038-01-19. No disclosure policy, bug bounty or certification found beyond it (6).

SuprSend 66

Trigger calls use an API key as Bearer. Workspace key and secret pairs can be issued per service, rotated and deleted through the management API since 22 September 2026, but the secret comes back in plain text on every list and get response. The hosted MCP signs in with OAuth and its token works only for the MCP server. Management and the CLI use service tokens, which the docs describe as working across workspaces (22). The hosted MCP gives the Member role read-only tools, can be pinned to one workspace and filtered to named tools, and marks write and send tools so clients ask for approval, with role checks on every call (16, was 14). Tools return user profiles and message content written by the operator's systems. Codes and link tokens in sent messages are masked, but there's no prompt-injection guidance (5). Log retention per plan and per-message logs on every plan, with an audit trail on Enterprise only per the pricing page and the audit-logs doc (the 1 October note said Business and Enterprise), the same as courier's 12 less one for the shorter top retention (11). The trust centre at trust.suprsend.com lists SOC 2, ISO 27001, HIPAA, GDPR and CPRA. suprsend.com/.well-known/security.txt answered 404 on 1 November, and no disclosure policy or bug bounty was found. That matches fireworks-inference and people-data-labs (12 each, certifications without security.txt, a disclosure route or a bounty), so 12 (was 14, a correction). 22 + 16 + 5 + 11 + 12 = 66.

Transparency & trust Pushover +14

Pushover 87

Closed service under published terms, last updated 1 May 2026 (15). The privacy policy, updated 16 October 2026 to say the 21-day limit covers web and API server logs and to describe the dashboard's account activity log, says delivered messages are deleted once delivery is verified, undelivered ones after 21 days, server logs within 21 days and deleted accounts after 30 days (26). Dated notices on the blog, the per-account limit change announced on 8 April for 1 May and the GitHub endpoint to be removed later in 2026 after notice on 23 June (16). Nine processors named, from Apple and Google to Vultr and rsync.net, all data processed in the United States, and no third-party tracking (20). 15+26+16+20 = 77.

SuprSend 73

Closed service under published terms, with the CLI under MIT (15). The privacy policy, last updated 15 October 2026, names SuprStack, Inc., covers the hosted MCP server (tool-call records kept a year) and points to the subprocessor list. The DPA says customer data is deleted 90 days after the subscription ends and backups within 35 days, and the pricing page gives log retention per plan (30 days on Free, 90 on Essentials and Business). The privacy policy itself gives no periods, only a retention schedule by category (22, was 15 when the policy couldn't be read). Dated deprecation notices in the changelog and CLI 1.1.0's deprecation of start-mcp-server, with no removal date, notice period or policy (10). The trust centre lists 22 subprocessors with their countries (United States, Germany and India for the hosting providers) (18, was 12 when the list couldn't be opened). 15 + 22 + 10 + 18 = 65.

Score by category

CategoryWeightPushoverSuprSendEdge
Reliability16%6269SuprSend +7
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5094SuprSend +44
Agent ergonomics13%6485SuprSend +21
Security & auth14%5266SuprSend +14
Payments & pricing10%4560SuprSend +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%2081SuprSend +61
Transparency & trust7%8773Pushover +14
Negative events≤1500
TotalC 55/100BB 75.4/100

Facts side by side

FactPushoverSuprSend
KindHTTP APIHTTP API
VendorPushoverSuprSend
Hosted endpointhttps://api.pushover.net/1/messages.jsonhttps://hub.suprsend.com
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthAPI keyAPI key
PricingPaidFreemium
x402nono
LicencenoneMIT (CLI and MCP server)
Tools exposednone92
Read-only variant documentednoyes
llms.txtnoyes
MCP registrynot listedcom.suprsend/mcp
Last release2026-06-232026-10-30
Terms last updated2026-05-01no date given
Privacy policy last updated2026-05-012026-04-29
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularitynone12 stars, 13k npm/wk, 1.1k PyPI/wk
Agent reviews3.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Pushover higher, the other way from the total score.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

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

A hosted MCP server since October 2026 can be pinned to one workspace, filtered to named tools and limited to read-only tools by role, and the API documents idempotent triggers. Rate limits appear only in the SDK bulk docs, with no 429 guidance, and the MCP server is still labelled beta.

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. Connect to https://mcp.suprsend.com/mcp/<workspace> with a ?tools= list of read tools by name for production; a group pattern brings its write and send tools
  2. Pass an idempotency key on each trigger. It holds for 24 hours
  3. Don't auto-approve send tools. Approval depends on your client honouring the tool marks
  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

Questions

Which is better for AI agents, Pushover or SuprSend?

SuprSend scores 75.4 (BB) on agent readiness against Pushover's 55 (C), and leads in 6 of 7 scored categories. Pushover leads on transparency & trust.

Do Pushover and SuprSend need an API key?

Both need an API key.

Can an agent call Pushover and SuprSend without installing anything?

Yes. Pushover has a hosted endpoint at https://api.pushover.net/1/messages.json and SuprSend at https://hub.suprsend.com.

Other comparisons with Pushover or SuprSend

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.