Publer API + MCP by Publer

# Fix list: Publer API + MCP

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/publer, the October 2026 research run, assessed 1 October 2026. Grade D, 47.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 Publer API + MCP: 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, 15 out of 100, up to 10.6 more on the total

Why it scored 15: No x402 or other machine payment (0). Business is priced per social account a month ($7, plus $3 per extra member, per the 30 September check, since the plans page loads prices by script), with no per-call price (15). The free plan has no API or MCP, and we found no statement on whether the paid trial needs a card (0). A person has to sign up in a browser and buy Business (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. Security & auth, 41 out of 100, up to 10.3 more on the total

Why it scored 41: Keys carry chosen scopes (workspaces and accounts always, plus posts, media and analytics), a revoked key returns 401, and the docs advise rotating every 90 to 180 days (28). The MCP article documents the key inside the generated server URL as one option, so less 10 (18). A key without the posts scope can't write, but posts covers both reading and writing, and the MCP article gives no approval guidance (8). Competitor analysis and post insights bring back other accounts' public content, with no injection guidance, and there's no inbox or comment tool (8). No audit log or key usage view found (0). The privacy policy claims ISO/IEC 27001 certification. No security.txt or disclosure route found (7).

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. Schema & documentation, 46 out of 100, up to 8.8 more on the total

Why it scored 46: No OpenAPI or other machine-readable contract found (0). llms.txt and a Markdown copy of every docs page via .md (10). Endpoint pages say what each call does. The MCP article lists no tools, so we couldn't read their descriptions (8). Parameters are typed with enums for state and postType, but the schedule body is a nested bulk structure per network (10). 401, 403 and 422 explained per endpoint, the 429 body shown, and job failures carry a per-account message (13). The docs claim semantic versioning under v1, and we found no public changelog (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.

## 4. Reliability, 60 out of 100, up to 8 more on the total

Why it scored 60: A status page at status.publer.com, per the 30 September check (20). Its robots.txt blocked our reader on 1 October for both the page and its history, so we have no incident record. That's our limit, not proof of a clean one (5). 100 requests per 2-minute fixed window per user across all keys, plus daily caps per network and plan, such as 25 Instagram posts a day per profile on Business (15). A 429 returns a JSON error with X-RateLimit-Remaining and X-RateLimit-Reset, and the docs advise exponential backoff. No Retry-After and no idempotency key for the async post jobs (10). No SLA, and the terms disclaim uptime (0). The API isn't 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.

## 5. Agent ergonomics, 55 out of 100, up to 7.3 more on the total

Why it scored 55: No field selection, and we couldn't count the MCP tools, which the help article doesn't list (10). List posts takes page, state, from and to, account_ids, query, postType and member_id, and returns total and total_pages (20). Errors say whether a scope or the Publer-Workspace-Id header is missing, and job failures name the account and the cause (16). Post creation is an async job polled at /job_status, with no idempotency key. Drafts exist (5). No SDKs, and every call needs the non-standard Bearer-API scheme plus a workspace header (4).

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, 41 out of 100, up to 5.2 more on the total

Why it scored 41: The MCP help article was updated on 28 September 2026 for the Business launch (30). We found no changelog, so we can't count releases in the last 90 days. publer.com/changelog redirects to the homepage (5). Support by email at support@publer.com and a help centre (6). No SDKs or MCP registry entry (0). No packages to assess (0).

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. Transparency & trust, 69 out of 100, up to 2.7 more on the total

Made of editorial 58, provenance 80.

Why it scored 69: Closed service under terms updated 13 February 2026 from Kalemi Code of Tirana (registration L71705026N) and Kalemi Code LLC of Sheridan, Wyoming, under Albanian law (15). The privacy policy revised 8 July 2026 keeps data 7 days after account deletion and then deletes it, links a DPA and a sub-processor list, and names Paddle and PayPro Global. It says nothing on AI providers (26). No deprecation policy or dated notices found (2). Servers in Frankfurt and a sub-processor list linked. We didn't read the list itself (15).

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):

- Changelog: not found (0 of 10)
- security.txt: not found (0 of 10)

## 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: status history, since robots.txt blocks status.publer.com
- unchecked: the MCP tool list, count and annotations, which the help article doesn't give
- Whether Publer keeps an API or product changelog somewhere we didn't find
- Whether the Business trial needs a card
- unchecked: Business per-account price on 1 October, since the plans page loads prices by script

## Weaknesses

- API and MCP only on Business and Enterprise, and the free plan has no API
- Async job polling for every post creation, with no idempotency key
- No OpenAPI spec, no public changelog and no SDKs
- The MCP article lists no tools and allows the key inside the server URL
- Status history unreadable to us, since robots.txt blocks status.publer.com

## 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.

- List workspaces first and send Publer-Workspace-Id on later calls, or expect a 403
- Poll /job_status/{job_id} after posts/schedule and read payload.failures, since status reads complete even when posts failed
- Use the Bearer-API scheme, not Bearer
- Leave a one-minute gap between posts to the same account, or the job fails
- Read X-RateLimit-Reset after a 429 and wait until then, as there's no Retry-After

## What the review panel asked for

- Failed status on failures
- MCP tool list
- separate posts read scope
- publish MCP tool list

## 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.