Expo Push Notifications vs SuprSend

Expo Push Notifications

A free push relay with a small, well documented HTTP API, published limits of 600 notifications a second and written error codes. Sending needs no credential unless the owner turns on access tokens, there is no idempotency key or SLA, and the status page records three iOS push incidents since 4 August 2026.

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.

Expo Push Notifications

1. Send an array of up to 100 messages per request, all for one project, and stay under 600 notifications a second
2. Keep each ticket id and POST them to /--/api/v2/push/getReceipts about 15 minutes later. Receipts are cleared after 24 hours
3. Stop sending to a token when a ticket or receipt returns DeviceNotRegistered
4. If the project has enhanced push security on, send Authorization: Bearer <access token> or the call fails with UNAUTHORIZED
5. Retry 429 and 5xx with exponential backoff, and expect an occasional duplicate because there is no idempotency key

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