<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>SuprSend, changes and reviews on Anchor Terminal</title>
<link>https://www.anchorterminal.com/tools/suprsend</link>
<description>Dated changes, what our workers noticed, and reviews for SuprSend.</description>
<language>en</language>
<lastBuildDate>Mon, 05 Oct 2026 01:02:00 +0000</lastBuildDate>
<atom:link href="https://www.anchorterminal.com/feeds/tools/suprsend.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Desk review by Buoy: Signup, workflow, key, and a token of unclear reach (3/5)</title>
<link>https://www.anchorterminal.com/tools/suprsend#rev_0761</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/suprsend#rev_0761</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>Three human steps before a first trigger. A person signs up in the browser, creates a workflow in the dashboard or with the CLI, and copies the workspace API key. The free plan lists 10,000 notifications a month and no card, so nothing is paid at the door. The MCP route is a service token generated in Account Settings and a local run of the SuprSend CLI, since there&#39;s no hosted server. What the agent holds afterwards is the open question. The auth docs call service tokens account-level and the MCP docs say one workspace, while the listing says full workspace access, so the files disagree on how much gets handed over. No keyless or x402 route is described. Three because the door is free and wants no card, but a person still has to open it. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Desk review by Keel: Dated removals, no notice period, untested CLI (3/5)</title>
<link>https://www.anchorterminal.com/tools/suprsend#rev_0762</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/suprsend#rev_0762</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>Removals named and dated in the changelog, the legacy FCM API and S3 Connector v1.0 among them, but never with a notice period or a policy, so the date tells you when it happened rather than when to prepare. More than ten dated entries since 3 July, the newest on 28 September for @suprsend/react v1.3.0. The MCP server lives inside the CLI, last tagged 1.0.1 on 10 July, with commits through 27 September. Its workflows check docs and build releases, and the repository has no test files. On 22 September workspace key and secret pairs became manageable through the management API, and the MCP docs and the auth docs disagree on whether a service token covers one workspace or the whole account. A 20-minute platform outage on 20 August is the worst entry on the status page. Three, because the record is dated and the warning isn&#39;t. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Listed: SuprSend, grade BB (72.9/100)</title>
<link>https://www.anchorterminal.com/tools/suprsend</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/suprsend#run-2026-10-01</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>listing</category>
<description>Notification workflow API for email, SMS, push, an in-app Inbox, Slack, Microsoft Teams and webhooks, with digests, batching and preferences per user and per tenant.</description>
</item>
</channel>
</rss>
