SuprSend by SuprSend

# Fix list: SuprSend

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/suprsend, the October 2026 research run, assessed 1 October 2026. Grade BB, 72.9 out of 100.

This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public.

For a coding agent working on SuprSend: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published.

## 1. Payments & pricing, 40 out of 100, up to 7.5 more on the total

Why it scored 40: 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 (0).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments):

The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).

- 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which.
- 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login.
- 20, a free tier or trial that doesn't need a card.
- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).

Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied.

Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol.

## 2. Reliability, 69 out of 100, up to 6.2 more on the total

Why it scored 69: Status page at status.suprsend.com with per-component history (20). Since 3 July 2026, a 20-minute "Platform down" on 20 August, a 1 hour 35 minute log delay on 23 September, a 30-minute Inbox issue on 25 September and several one to three minute blips on the object, user and preferences API. Nothing over an hour on a core API, but one platform-wide outage (15). The only rate limit we found is 1,000 requests a second in the SDK bulk docs, with a bulk call counting as one call per record, and there's no rate-limit page (7). No 429 or backoff guidance found, but an `idempotency_key` on trigger holds for 24 hours (7). The pricing page lists 99.9% uptime on every paid plan (10). The trigger API is generally available (10).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability):

Hosted APIs, MCP servers, models and platforms.

- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).
- 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so.
- 15, rate limits documented with numbers.
- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.
- 10, an SLA published for any paid tier.
- 10, the surface agents use is generally available, not beta or preview.

Local packages, SDKs, frameworks and stdio MCP servers.

- 20, installs from an official package with supported runtimes stated.
- 25, a public CI and test suite, passing on the default branch.
- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).
- 15, semver discipline and breaking changes called out in a changelog.
- 15, version 1.0 or later, or declared stable.

Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors.

## 3. Security & auth, 66 out of 100, up to 6 more on the total

Why it scored 66: Trigger calls use an API key as Bearer. Since 22 September 2026 extra workspace key and secret pairs can be issued per service, rotated and deleted through the management API, but the docs warn that the secret comes back in plain text on every list and get response. Management and MCP use service tokens, which the auth docs describe as account-level across workspaces (22). `--tools` can limit a production session to read-only tools, and tools are annotated, but there's no approval step and RBAC is Enterprise only (14). Tools return user and object properties written by the operator's systems, with no prompt-injection guidance (5). An audit trail on Business and Enterprise, logs kept 30 days on Free and Essentials and 90 on Business (11). The security page lists SOC 2 Type II, ISO 27001, HIPAA, GDPR and CPRA and regular third-party pen tests. No security.txt per the 30 September check, and no disclosure policy or bug bounty found (14).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-security):

- 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option.
- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.
- 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10.
- 0 to 15, audit logs or per-call visibility for the operator.
- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.

Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing.

## 4. Transparency & trust, 69 out of 100, up to 2.7 more on the total

Made of editorial 52, provenance 86.

Why it scored 69: Closed service under published terms, with the CLI and MCP server under MIT (15). The security page gives server log retention (six months) and the pricing page gives log retention per plan. We couldn't read the privacy policy because of our fetch limit (15). Dated deprecation and removal notices in the changelog, such as the legacy FCM API and S3 Connector v1.0, but no notice period or policy (10). The security page links a subprocessor list and mentions EU data residency, which we couldn't open (12).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency):

- 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms.
- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).
- 0 to 20, a deprecation policy or notices with dates.
- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).

The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two.

Provenance checks not met in full (half of this category, computed from checked facts):

- Domain age: suprsend.com, registered 2020-12-27 (5 years) (11 of 15)
- security.txt: not found (0 of 10)

## 5. Agent ergonomics, 87 out of 100, up to 2.1 more on the total

Why it scored 87: 22 built-in MCP tools, and `--tools` loads a subset by group or name. Workflow and event trigger tools register one per slug only when asked with `--workflows` or `--events` (25). We didn't check pagination on list endpoints in detail (12). Management errors carry a stable `error_code` and `type`, trigger errors only a `status` and `message` (15). `idempotency_key` on triggers for 24 hours, and the MCP tools carry readOnlyHint, destructiveHint and idempotentHint annotations (20). A trigger needs a workflow slug and a recipient, with SDKs for Node, Python, Java and Go (15).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics):

- 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries).
- 20, pagination, filtering and output-size controls.
- 20, actionable, documented error responses, codes and messages an agent can recover from.
- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.
- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.

Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs.

## 6. Maintenance & community, 81 out of 100, up to 1.7 more on the total

Why it scored 81: Changelog entry on 28 September 2026, @suprsend/react v1.3.0 (30). More than ten dated changelog entries since 3 July (20). A closed service with a busy changelog. We didn't check the CLI repo's issues or support response (11). The MCP server is in the official registry as io.github.suprsend/cli (15). The CLI's last tag is 1.0.1 on 10 July 2026, and its workflows check docs and release builds with no test files in the repository (5).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance):

- 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older.
- 20, at least three releases or dated changelog entries in the last 90 days.
- 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15.
- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).
- 10, package health, current dependencies and CI.

Models are read for deprecation notice periods and model churn rather than release counts.

## 7. Schema & documentation, 94 out of 100, up to 1 more on the total

Why it scored 94: Public OpenAPI file (openapi.yaml in the docs) (25). llms.txt per the 30 September check, and the docs are Markdown in a public repository (10). The MCP tool definitions in the CLI source each say when to use the tool, when not to, the side effects and what comes back, for example `get_suprsend_user` and `upsert_suprsend_user` (20). Typed tool 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 with more than ten entries since 8 July 2026 (15).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema):

APIs and MCP servers.

- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).
- 10, llms.txt or Markdown docs served for agents.
- 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference.
- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.
- 0 to 15, examples and documented error responses.
- 15, versioning and a public changelog.

Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference.

## What we couldn't check

What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it.

- unchecked: the privacy policy, subprocessor list and llms.txt, which our fetch proxy refused with a rate limit (https://www.suprsend.com/privacy, https://www.suprsend.com/subprocessors, https://docs.suprsend.com/llms.txt)
- Whether service tokens are scoped to one workspace (as the MCP docs say) or to the whole account (as the auth docs say)
- The API's request rate limits and 429 behaviour, which we didn't find documented
- The monthly-billed prices ($110 and $275) weren't visible in our read of the pricing page, which showed yearly billing

## Weaknesses

- No rate-limit page or 429 guidance
- No hosted MCP server, only the local CLI
- Workspace secrets come back in plain text on every management API response
- A 20-minute platform outage on 20 August 2026 and repeated short API blips
- Audit trail on Business and Enterprise only, RBAC on Enterprise only

## What costs an agent a turn today

The notes we give agents before they call it. Each one is a workaround an agent shouldn't need.

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

## What the review panel asked for

- Document service-token scope
- notice periods on removals
- tests for the CLI

## When it's done

Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.