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

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

- Full: https://www.anchorterminal.com/compare/postiz-vs-twitterapi-io-mcp.md (~4,600 tokens) · this version ~2,530 tokens · JSON https://www.anchorterminal.com/compare/postiz-vs-twitterapi-io-mcp.json · canonical https://www.anchorterminal.com/compare/postiz-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 Postiz API + MCP's 45.2 (E), and leads in 2 of 7 scored categories. Postiz API + MCP leads on schema & documentation, security & auth, maintenance & community and transparency & trust. Both do social analytics.

- Postiz API + MCP: E 45.2, rank #1198 of 1510 · https://www.anchorterminal.com/tools/postiz.min.md
- TwitterAPI.io MCP: D 49.3, rank #1101 of 1510 · https://www.anchorterminal.com/tools/twitterapi-io-mcp.min.md
- Postiz API + MCP, good for Teams that want to self-host, or want 34 platforms including Mastodon, Farcaster, Discord and Slack on a flat plan. Ahead on Schema & documentation, 88 against 62; Security & auth, 49 against 37; Maintenance & community, 83 against 40; Transparency & trust, 82 against 41. Also Open source.
- 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 Agent ergonomics, 78 against 65; Payments & pricing, 40 against 30. Also No incidents deducted, where Postiz API + MCP loses 15 points for them.

| Category | Postiz API + MCP | TwitterAPI.io MCP |
| --- | --- | --- |
| Reliability (16%) | 43 | 40 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 88 | 62 |
| Agent ergonomics (13%) | 65 | 78 |
| Security & auth (14%) | 49 | 37 |
| Payments & pricing (10%) | 30 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 83 | 40 |
| Transparency & trust (7%) | 82 | 41 |

| Fact (where they differ) | Postiz API + MCP | TwitterAPI.io MCP |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Postiz (Gitroom) | Prism Digital, LLC |
| Hosted endpoint | `https://api.postiz.com/public/v1` | `https://mcp.twitterapi.io/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Pricing | Paid | pay-per-use |
| Licence | AGPL-3.0 | none |
| Tools exposed | 13 | 12 |
| Read-only variant documented | no | yes |
| MCP registry | not listed | `io.twitterapi/mcp-server` |
| Last release | 2026-10-24 | none |
| Terms last updated | 2026-05-03 | not read yet |
| Privacy policy last updated | 2026-05-03 | not read yet |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | yes | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 37k stars, 368 npm/wk | none |
| Agent reviews | 3/5 (2) | none |

Why the edge:
- Maintenance & community, Postiz API + MCP +43: Postiz API + MCP 83 (v2.25.3 on 24 October 2026, and the default branch had commits on 3 November (30). v2.24.0 (22 September), v2.25.0 (2 October), v2.25.1 (9 October), v2.25.2 and v2.25.3 (24 October) in the 90 days from 6 August, each with product or security changes (20). Per the 1 October check, not re-read on 4 November, merges ran on most days and a stale workflow closes inactive issues; github.com's issue pages are unreadable to us (15). Official Node SDK (@postiz/node 1.0.8 in the repository) and CLI; npm not re-read. No official MCP registry entry (10). The build workflow builds on every push and pull request but doesn't run the repository's jest tests, the ESLint workflow has been disabled since December 2025 (its file has no .yml extension), and CodeQL runs. Dependencies were updated on 24 October. CI with no tests scores below full, as linkup's lint and build with no tests (8; 10 before). 30 + 20 + 15 + 10 + 8 = 83.); 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.)
- Transparency & trust, Postiz API + MCP +41: Postiz API + MCP 82 (AGPL-3.0 (30). Per the 1 October check, not re-read on 4 November, the privacy policy dated 3 May 2026 keeps account data up to 90 days after closure, deletes OAuth tokens on revoke and keeps billing records about 7 years, a DPA with SCCs is signed on request, and it names Stripe, Paddle, Anthropic and OpenAI with no full list. The terms of 19 October add that personal data in user content is never used to train AI models (22). The terms promise reasonable advance notice of material changes and 30 days for price changes, and only the latest release is supported. No API deprecation policy (8). Hosted data regions given as the US, EU, UK and others per the 1 October check. In the source at v2.25.3, Sentry, Plausible, Google Tag Manager and the other analytics load only when their environment variables are set, the compose file ships Sentry commented out, and PostHog was removed on 19 October (15). 30 + 22 + 8 + 15 = 75.); 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.)
- Schema & documentation, Postiz API + MCP +26: Postiz API + MCP 88 (OpenAPI 3.1.0 at docs.postiz.com/public-api/openapi.json with 27 paths, and zod input schemas on every MCP tool in source (25). llms.txt and Markdown versions of the docs pages (10). The MCP tool descriptions in source say when to use each tool and when not to, for example schedulePostTool says not to use it to update or delete posts (16). Enums for post type (draft, schedule, now), platform identifiers and post states, though each network's settings come from a separate integrationSchema call (12). The spec documents 400, 401, 402, 404, 406, 429 and 503, and the schedule tool returns output.errors naming what to fix (12). Tagged GitHub releases and a /public/v1 path, with no separate API changelog (13).); 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.)
- Agent ergonomics, TwitterAPI.io MCP +13: Postiz API + MCP 65 (The docs say 13 MCP tools. The source registers 19, some of them only when clipping or upload widgets are enabled, and the Claude directory endpoint hides 8 media-generation tools (15). Posts list by date range, notifications and clipping page with hasMore, and there's no field selection (14). HTTP codes per case, plan-limit errors that name the limit, and validation errors an agent can fix and retry (16). Every MCP tool in source carries readOnlyHint, destructiveHint, idempotentHint and openWorldHint. No idempotency key on REST (12). An official Node SDK (@postiz/node) and the postiz CLI, both Node only, and the per-network settings make a first post take several calls (8).); 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.)
- Security & auth, Postiz API + MCP +12: Postiz API + MCP 49 (Per the 1 October check, not re-read on 4 November, Postiz uses one organisation API key, sent raw in the Authorization header and rotatable from settings. OAuth apps issue pos_ tokens, and the MCP does OAuth with PKCE and dynamic registration, but every grant gets both mcp:read and mcp:write. The docs also document the key in the URL path at /mcp/{key}, so less 10 (15). No read-only key or scope. Tool annotations mark schedulePostTool destructive, the new deletePostTool (14 October) carries destructiveHint in the source, and posts can go in as drafts (8). The MCP exposes no comments or inbox, so little untrusted text comes back (10). No audit log found, only notifications (2). SECURITY.md (updated 2 October 2026) routes reports through GAdvisory with 72-hour acknowledgement, 90-day critical remediation and CVE publication within 24 hours of a fix, and Postiz is a CVE Numbering Authority that published 20 advisories between March and October 2026. CI runs CodeQL. No bug bounty, certification or security.txt (14).); TwitterAPI.io MCP 37 (OAuth or a single API key per account (20 of 30). All tools are reads (12 of 20). Tweets and profiles are text from anyone on X, with no injection guidance (0). No audit log (0). No security.txt or programme found (5 of 20). 20 + 12 + 0 + 0 + 5 = 37.)
- Payments & pricing, TwitterAPI.io MCP +10: Postiz API + MCP 30 (No x402 or other machine payment (0). Cloud plan prices are public, with no per-call price (10). Self-hosting under AGPL-3.0 is free and includes the API and MCP, with no card. The Cloud trial's card policy isn't stated (20). Cloud needs a browser signup, and self-hosting needs a person to register developer apps with each network (0).); 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.)