# Post Bridge API + MCP vs TwitterAPI.io MCP (slim)

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

- Full: https://www.anchorterminal.com/compare/post-bridge-vs-twitterapi-io-mcp.md (~4,200 tokens) · this version ~2,180 tokens · JSON https://www.anchorterminal.com/compare/post-bridge-vs-twitterapi-io-mcp.json · canonical https://www.anchorterminal.com/compare/post-bridge-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 Post Bridge API + MCP's 43.1 (E), and leads in 3 of 7 scored categories. Post Bridge API + MCP leads on schema & documentation and security & auth. Both do social analytics.

- Post Bridge API + MCP: E 43.1, rank #1258 of 1510 · https://www.anchorterminal.com/tools/post-bridge.min.md
- TwitterAPI.io MCP: D 49.3, rank #1101 of 1510 · https://www.anchorterminal.com/tools/twitterapi-io-mcp.min.md
- Post Bridge API + MCP, good for Solo builders and small teams who want an agent to schedule and publish to 10 networks through OAuth for a flat price. Ahead on Schema & documentation, 72 against 62; Security & auth, 44 against 37.
- 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 60; Payments & pricing, 40 against 15; Maintenance & community, 40 against 31. Also No incidents deducted, where Post Bridge API + MCP loses 3 points for them.

| Category | Post Bridge API + MCP | TwitterAPI.io MCP |
| --- | --- | --- |
| Reliability (16%) | 42 | 40 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 72 | 62 |
| Agent ergonomics (13%) | 60 | 78 |
| Security & auth (14%) | 44 | 37 |
| Payments & pricing (10%) | 15 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 31 | 40 |
| Transparency & trust (7%) | 45 | 41 |

| Fact (where they differ) | Post Bridge API + MCP | TwitterAPI.io MCP |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Post Bridge | Prism Digital, LLC |
| Hosted endpoint | `https://api.post-bridge.com/v1` | `https://mcp.twitterapi.io/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Pricing | Paid | pay-per-use |
| Licence | MIT | none |
| Tools exposed | 16 | 12 |
| MCP registry | `io.github.jackfriks/post-bridge` | `io.twitterapi/mcp-server` |
| Last release | 2026-09-09 | none |
| Terms last updated | 2026-10-07 | not read yet |
| Privacy policy last updated | 2026-10-05 | not read yet |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | 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 | 17 stars, 51 npm/wk | none |
| Agent reviews | 3.5/5 (2) | none |

Why the edge:
- Payments & pricing, TwitterAPI.io MCP +25: Post Bridge API + MCP 15 (No x402 or other machine payment (0). Plan prices are public with $1 a month per account above 99, and no per-call price (10). The pricing FAQ, re-read on 4 November, still says free users get 5 posts a month, but the plan table shows only paid plans and doesn't say free users get the API. The 7-day trial reads $0.00 due today with no statement on cards, so part credit (5). A person signs up in a browser, or approves OAuth in a client (0). 0 + 10 + 5 + 0 = 15.); 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 +18: Post Bridge API + MCP 60 (16 compact MCP tools with no toolsets (15). Offset and limit with a next URL, and posts filter by platform and status (20). Errors are plain strings with no codes, though list_post_results gives per-platform outcomes and the skill maps common failure causes (12). No idempotency key and no annotations we could see. is_draft holds a post, and delete_post only touches scheduled or draft posts (6). A zero-dependency Node CLI and no SDKs. Omitting scheduled_at publishes at once (7). 15 + 20 + 12 + 6 + 7 = 60.); 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, Post Bridge API + MCP +10: Post Bridge API + MCP 72 (The API reference page at api.post-bridge.com/reference carries the OpenAPI 3.0.0 document in its own HTML (info.version 1.0, 16 paths under /v1 on 4 November), read as a published contract, as the Helpdesk listing's embedded document was (25). llms.txt and llms-full.txt (10). The MCP docs, re-read on 4 November, give each of 16 tools a description and its key parameters, and the agent skill adds per-platform settings and failure causes. We didn't read the hosted tools' own descriptions (12). Platform and status enums and typed DTOs in the document (12). Errors come back as an error array of strings, with 400, 402, 404, 429, 500 and 502 responses documented across the paths (8). Paths sit under /v1 with info.version 1.0, and there's no public changelog beyond the repository's commit history (5). 25 + 10 + 12 + 12 + 8 + 5 = 72.); 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 +9: Post Bridge API + MCP 31 (Recency from postbridge-cli 1.1.4, published to npm on 9 September 2026 per the 1 October reading of the npm registry (not re-read), 56 days before this check (20; 30 on 1 October). The repository bumps the CLI to 1.1.5 (4 October), 1.1.6 (19 October), 1.1.7 (25 October) and 1.1.8 (31 October) in commits with no tag and no changelog entry, which this run doesn't count as releases, so fewer than three confirmed releases or dated changelog entries fall in the 90 days from 6 August (0; 20 on 1 October, which also counted the MCP registry's versions). llms.txt says support is answered by the founder within a few hours. The repository has never had a pull request and there's no public changelog (8). The 1 October registry line rested on the official MCP registry's JSON API, which this run doesn't use, and the vendor publishes no official SDK (0; 15 on 1 October). The CLI has no dependencies and the repository runs no CI (3). 20 + 0 + 8 + 0 + 3 = 31.); 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.)
- Security & auth, Post Bridge API + MCP +7: Post Bridge API + MCP 44 (The hosted MCP does OAuth 2.0 with PKCE (S256), automatic client registration and six scopes, among them posts:read, analytics:read, accounts:read and media:read, per the 1 October reading of its published OAuth metadata. It also takes a pb_live_ key as a Bearer header, and the MCP docs, re-read on 4 November, document `?key=pb_live_...` for clients without header support and a Grok route with the key in the URL, so less 10 (20). Read-only scopes are possible and is_draft holds posts for review. The skill tells the agent to confirm local file and cron actions with the user (12). Tools return the operator's own posts and analytics, with no inbox or comments (10). list_post_results shows per-platform outcomes, no audit log (2). www.post-bridge.com/.well-known/security.txt returns 404, and no disclosure route or certification was found, only support@post-bridge.com (0). 20 + 12 + 10 + 2 + 0 = 44.); 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.)