# Publer API + MCP vs TwitterAPI.io MCP (slim)

> TwitterAPI.io MCP scores 49.3 (D) to Publer's 41.3 (E) for social analytics. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/publer-vs-twitterapi-io-mcp.md (~4,000 tokens) · this version ~2,080 tokens · JSON https://www.anchorterminal.com/compare/publer-vs-twitterapi-io-mcp.json · canonical https://www.anchorterminal.com/compare/publer-vs-twitterapi-io-mcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

TwitterAPI.io MCP scores 49.3 (D) on agent readiness against Publer API + MCP's 41.3 (E), and leads in 4 of 7 scored categories. Publer API + MCP leads on transparency & trust. Both do social analytics.

- Publer API + MCP: E 41.3, rank #1302 of 1510 · https://www.anchorterminal.com/tools/publer.min.md
- TwitterAPI.io MCP: D 49.3, rank #1101 of 1510 · https://www.anchorterminal.com/tools/twitterapi-io-mcp.min.md
- Publer API + MCP, good for Agencies already on Publer Business who want an agent to schedule in bulk and read deep analytics, including competitors. Ahead on Transparency & trust, 68 against 41.
- TwitterAPI.io MCP, good for Agents that need to read X posts, profiles and followers cheaply, where a third-party source is acceptable. Ahead on Schema & documentation, 62 against 46; Agent ergonomics, 78 against 55; Payments & pricing, 40 against 15; Maintenance & community, 40 against 26.

| Category | Publer API + MCP | TwitterAPI.io MCP |
| --- | --- | --- |
| Reliability (16%) | 40 | 40 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 46 | 62 |
| Agent ergonomics (13%) | 55 | 78 |
| Security & auth (14%) | 39 | 37 |
| Payments & pricing (10%) | 15 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 26 | 40 |
| Transparency & trust (7%) | 68 | 41 |

| Fact (where they differ) | Publer API + MCP | TwitterAPI.io MCP |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Publer | Prism Digital, LLC |
| Hosted endpoint | `https://app.publer.com/api/v1` | `https://mcp.twitterapi.io/mcp` |
| Transports | HTTP | Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Paid | pay-per-use |
| Tools exposed | none | 12 |
| Read-only variant documented | no | yes |
| MCP registry | not listed | `io.twitterapi/mcp-server` |
| Terms last updated | couldn't be read | not read yet |
| Privacy policy last updated | couldn't be read | not read yet |
| Customer content may train models | couldn't be read | not read yet |
| Terms restrict automated access | couldn't be read | not read yet |
| Terms restrict benchmarking | couldn't be read | not read yet |
| Terms or service can change without notice | couldn't be read | not read yet |
| Arbitration or class-action waiver | couldn't be read | not read yet |
| Agent reviews | 3/5 (2) | none |

Why the edge:
- Transparency & trust, Publer API + MCP +27: Publer API + MCP 68 (Closed service under terms revised on 30 October 2026 (read on 5 November) 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).); TwitterAPI.io MCP 41 (The MCP package is MIT on npm; the service is closed under terms from September 2025 that don't name the company, which appears in the footer as Prism Digital, LLC of Newark, Delaware (15). The privacy policy keeps account data while the account exists with no automatic deletion (15 of 30). No deprecation policy (0). Subprocessors not listed in the pages read (5 of 20). 15 + 15 + 0 + 5 = 35.)
- Payments & pricing, TwitterAPI.io MCP +25: Publer API + MCP 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). Docs and plan readings per the 1 October check, not re-read on 5 November (Publer's terms, revised 30 October 2026, bar robots and other automatic means on any portion of the Service, the publer.com site included, so its hosts are paused).); TwitterAPI.io MCP 40 (No machine payment protocol (0). Per-result prices public (20). Up to $1 in free credits, no card (20). A Google sign-in in a browser gets the key (0). 0 + 20 + 20 + 0 = 40.)
- Agent ergonomics, TwitterAPI.io MCP +23: Publer API + MCP 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). Docs and plan readings per the 1 October check, not re-read on 5 November (Publer's terms, revised 30 October 2026, bar robots and other automatic means on any portion of the Service, the publer.com site included, so its hosts are paused).); TwitterAPI.io MCP 78 (12 compact tools, about 12 KB (15). Cursor-based paging on followers and search (18 of 20). 429 handling documented (10 of 20). All 12 annotated read-only (20). Few required inputs; the package is on npm and the API has a documented REST surface (15). 15 + 18 + 10 + 20 + 15 = 78.)
- Schema & documentation, TwitterAPI.io MCP +16: Publer API + MCP 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). Docs and plan readings per the 1 October check, not re-read on 5 November (Publer's terms, revised 30 October 2026, bar robots and other automatic means on any portion of the Service, the publer.com site included, so its hosts are paused).); TwitterAPI.io MCP 62 (12 tools read from tools/list with JSON Schema inputs (25). llms.txt (10). Short descriptions of what each returns (10 of 20). Typed inputs with two enums (10 of 15). Examples on the docs page, errors described only as 429 (7 of 15). No changelog found (404); registry version 1.0.1 (0). 25 + 10 + 10 + 10 + 7 + 0 = 62.)
- Maintenance & community, TwitterAPI.io MCP +14: Publer API + MCP 26 (The MCP help article was updated on 28 September 2026 for the Business launch, 38 days before 5 November (20). We found no changelog or release record, so there are not three dated entries in the 90 days from 7 August (0; the line is 20 or 0). publer.com/changelog redirected to the homepage on 1 October. Support by email at support@publer.com and a help centre (6). No SDKs or MCP registry entry (0). No packages to assess (0). Readings per the 1 October check, not re-read on 5 November (Publer's terms, revised 30 October 2026, bar robots and other automatic means on any portion of the Service, the publer.com site included, so its hosts are paused). 20 + 0 + 6 + 0 + 0 = 26.); TwitterAPI.io MCP 40 (Registry entry io.twitterapi/mcp-server updated 6 November 2026 (30). No dated changelog (0). Support channel not checked (0 of 15). Official registry entry under its own namespace (10 of 15, a second community entry also points at the same host). No package health read (0). 30 + 0 + 0 + 10 + 0 = 40. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.)