# Fix list: Blotato From Anchor Terminal's listing at https://www.anchorterminal.com/tools/blotato, the October 2026 research run, assessed 8 October 2026. Grade D, 46.1 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 Blotato: 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. Reliability, 38 out of 100, up to 12.4 more on the total Why it scored 38: Graded as a hosted service. No status page was found. The help pages link none, `status.blotato.com` did not connect, and the FAQ points users to downdetector.com for platform outages (0). With no page there is no incident history to read (5). Request limits are published per route, such as 30 a minute for creating posts, 60 for status reads and 120 for upload URLs (15). 429 is documented with a `message` that gives retry timing and guidance to stop, wait and reduce concurrency, with no `Retry-After` header documented. The help pages say there is no client idempotency header and describe how to check existing work before repeating a write (8). No SLA was found and the terms supply the service as is (0). The API and MCP server are not labelled beta (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. ## 2. Security & auth, 29 out of 100, up to 12.4 more on the total Why it scored 29: The MCP server takes OAuth through a browser flow, and its protected-resource metadata names a Supabase authorisation server. No scopes are documented. REST takes one key per account in a header, with full access, revoked only by regenerating it (15). No read-only key, scope or approval step enforced by the server. The help pages tell agents to get the user's approval before activating an automation or sending, and automations start as drafts (5). Tools return comments and direct messages from strangers and text extracted from URLs, and no injection guidance was found (0). A Logs page in the dashboard shows each request's payload, response and error, and responses carry a request ID. Team access means sharing the owner's login code, which the help page says leaves no audit trail (9). No security.txt, disclosure route, bug bounty or certification was found (0). Automation webhooks reject private and loopback addresses, which is noted and not scored. 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. ## 3. Payments & pricing, 10 out of 100, up to 11.3 more on the total Why it scored 10: No x402, MPP or L402 (0). Plan prices are public without a login at $29, $97 and $499 a month, and extra credits cost $6 per 1,000. The API has no price per call, so this is plan pricing (10). The 7-day trial needs a card and excludes the API and MCP, and generating a key starts the paid plan (0). A person signs up in a browser and copies the key from settings (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. ## 4. Agent ergonomics, 57 out of 100, up to 7 more on the total Why it scored 57: 36 MCP tools with no toolsets or read-only subset found. REST and MCP lists take a `limit` with a default of 50 and a maximum of 250, with no field selection (8). Cursor pagination with `since`, `until`, `status` and `platform` filters on posts (20). Errors carry `code`, `reqId`, `message`, `action` and `details`, and the error reference gives a fix for each code (17). No idempotency key. DM automations start as inactive drafts, and MCP tool annotations were not read (5). `blotato_create_post` needs three arguments. There are official n8n and Make nodes and no SDK in any language (7). 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. ## 5. Transparency & trust, 45 out of 100, up to 4.8 more on the total Made of editorial 27, provenance 62. Why it scored 45: Closed service under Terms of Use dated 18 May 2026 that name Blotato Inc. and Utah law. The terms take a perpetual, irrevocable, sub-licensable licence to user content (15). The privacy policy names Blotato Inc. with a Salt Lake City address and says data from third-party APIs is not used to train general models. It gives no retention period, repeats sections 8 to 15 of the terms inside it, and shows both 18 May 2026 and an effective date of 17 October 2024. No DPA was found (8). No deprecation policy, and the terms allow changes or discontinuation with or without notice (0). The help pages name Stripe for payments and ElevenLabs for voices, and the policy says the company is based in the United States. No sub-processor list or data locations were found (4). 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: blotato.com, registered 2020-08-08 (6 years) (11 of 15) - Terms of service: read, states 5 of the 7 things a reader expects, and has 1 clause that costs points (6.3 of 10) - Privacy policy: read, states 7 of the 8 things a reader expects (9.3 of 10) - Status page: not found (0 of 10) - Changelog: not found (0 of 10) - security.txt: not found (0 of 10) ## 6. Maintenance & community, 65 out of 100, up to 3.1 more on the total Why it scored 65: The MCP server was published to the official registry on 10 September 2026 and `llms.txt` is dated 5 October 2026 (30). Dated changes in the last 90 days are DM automations on 6 August, the comments and messaging API post on 7 August and the registry entry on 10 September, found in blog posts and the registry because there is no changelog (10). Support is in-app chat and email, weekly office hours have ended, and no public issue tracker for the API was read (6). Registry entry `com.blotato/mcp` under the vendor's domain namespace (15). The n8n node `@blotato/n8n-nodes-blotato` 1.0.10 dates from 29 January 2026 and there is no SDK (4). 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, 82 out of 100, up to 2.9 more on the total Why it scored 82: Public OpenAPI 3.0.3 document at `backend.blotato.com/openapi.json` with 45 operations. The help pages say account usage and schedule slots are implemented but absent from it (25). `llms.txt` on both hosts, a 1.3 MB full export, a Markdown twin of every help page and a documentation MCP endpoint (10). The MCP tools reference and the agent workflow pages state purpose, order of calls and what not to do, such as not resubmitting an unresolved post (17). The document has 214 enums and typed targets per platform, though error `details` is a free-form object. The hosted MCP tool schemas were not read (12). 320 examples in the document, error responses on most operations and an error reference with numeric codes (13). The version is in the path and `info.version` is 2.0.0, with no changelog found (5). 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 hosted MCP server's tool input schemas and annotations, which need a paid account to list - unchecked: the scopes and client registration of the OAuth flow. The metadata names a Supabase authorisation server, which was not queried - unchecked: GitHub stars and open issues for Blotato-Inc/n8n-nodes-blotato - Whether a status page exists anywhere. None is linked from the site or help pages, and status.blotato.com did not connect - The scheduling horizon. pricing.md gives 9 months, 1 year and 2 years by plan, and the help pages say 9 months on every plan - Which date governs the privacy policy, since the page shows 18 May 2026 and an effective date of 17 October 2024 - The site's llms.txt tells AI models that its statements are authoritative where other sources disagree, and the AI info page gives guidelines for describing the product. Neither was acted on and no deduction was taken ## Weaknesses - No status page, incident history or SLA was found, and the help pages send users to a third-party outage site - Each account has one API key with full access. There are no scopes, no read-only key and no team logins - The 7-day trial needs a card and excludes the API and MCP. Generating a key starts the paid Starter plan at once - No changelog, deprecation policy, security.txt or disclosure route was found, and the terms allow changes without notice - The privacy policy gives no retention period or sub-processor list, and the terms take a perpetual, irrevocable licence to user content - No idempotency key for creating posts, which the help pages state plainly ## 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. - Call `blotato_list_accounts` or `GET /v2/users/me/accounts` first, and fetch `pageId` or `boardId` before posting to a Facebook Page, LinkedIn company Page or Pinterest - Keep the `postSubmissionId` and poll the status until `published`, `scheduled` or `failed`. It is a receipt, not proof of publication - After a timeout on a create call, list existing posts before sending again, because there is no idempotency key - Do not generate an API key on a trial account unless the owner accepts the Starter charge - Keep REST bodies and MCP arguments apart. REST nests `post.content` and `post.target`, and the MCP tool takes flat arguments ## 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.