# Post Bridge API + MCP vs Xpoz MCP (slim)

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

- Full: https://www.anchorterminal.com/compare/post-bridge-vs-xpoz-mcp.md (~4,350 tokens) · this version ~2,480 tokens · JSON https://www.anchorterminal.com/compare/post-bridge-vs-xpoz-mcp.json · canonical https://www.anchorterminal.com/compare/post-bridge-vs-xpoz-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)

Post Bridge API + MCP scores 43.1 (E) on agent readiness against Xpoz MCP's 39.6 (E), and leads in 5 of 7 scored categories. Xpoz MCP leads on payments & pricing. Both do social analytics.

- Post Bridge API + MCP: E 43.1, rank #1258 of 1510 · https://www.anchorterminal.com/tools/post-bridge.min.md
- Xpoz MCP: E 39.6, rank #1339 of 1510 · https://www.anchorterminal.com/tools/xpoz-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 Reliability, 42 against 20; Schema & documentation, 72 against 64; Security & auth, 44 against 37; Maintenance & community, 31 against 25; Transparency & trust, 45 against 29.
- Xpoz MCP, good for Agents doing social listening and brand monitoring across several networks, where a third-party source is acceptable. Ahead on Payments & pricing, 30 against 15. Also No incidents deducted, where Post Bridge API + MCP loses 3 points for them.

| Category | Post Bridge API + MCP | Xpoz MCP |
| --- | --- | --- |
| Reliability (16%) | 42 | 20 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 72 | 64 |
| Agent ergonomics (13%) | 60 | 63 |
| Security & auth (14%) | 44 | 37 |
| Payments & pricing (10%) | 15 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 31 | 25 |
| Transparency & trust (7%) | 45 | 29 |

| Fact (where they differ) | Post Bridge API + MCP | Xpoz MCP |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Post Bridge | XPOZ |
| Hosted endpoint | `https://api.post-bridge.com/v1` | `https://mcp.xpoz.ai/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | API key |
| Pricing | Paid | Freemium |
| Licence | MIT | none |
| Tools exposed | 16 | 52 |
| llms.txt | yes | no |
| MCP registry | `io.github.jackfriks/post-bridge` | `ai.xpoz/social-insights` |
| Last release | 2026-09-09 | none |
| Terms last updated | 2026-10-07 | not read yet |
| Privacy policy last updated | 2026-10-05 | no document linked |
| 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:
- Reliability, Post Bridge API + MCP +22: Post Bridge API + MCP 42 (No readable status page. On 4 November 2026 status.post-bridge.com answered its robots.txt request with a redirect to a sign-in page, so the host is read as blocked and the 1 October reading of it is struck (0). No incident history to read (5). The OpenAPI document embedded in the API reference page, re-read on 4 November, sets 10 requests a second per key and one analytics sync per account every 30 minutes (15). The reference says to throttle and retry 429 responses with backoff, the analytics sync documents its own 429, and the agent skill says posts that report a platform 500 often publish anyway, so check results before republishing. That is backoff and safe-retry guidance without idempotency keys (12; the 1 October 5 wasn't a checklist value). No SLA found (0). The API and MCP aren't labelled beta (10). 0 + 5 + 15 + 12 + 0 + 10 = 42.); Xpoz MCP 20 (No status page found (0). No history (5). Credit allowances, no rate limits found (5 of 15). No retry guidance (0). No SLA (0). Not labelled beta (10). 0 + 5 + 5 + 0 + 0 + 10 = 20.)
- Transparency & trust, Post Bridge API + MCP +16: Post Bridge API + MCP 45 (The CLI, skills and plugin are MIT. The hosted service runs under terms that name only Post Bridge with Canadian governing law, no company type or registration, and a 24-hour refund window that the pricing FAQ gives as 7 days. The terms' Last Updated line showed the day of each check, 1 October and 4 November 2026 (10). The privacy policy, updated 5 October 2026, sets retention per data type, deletes personal data within 30 days of account deletion and names Supabase, Cloudflare, Stripe, Trigger.dev, Mailgun, Unkey and Vercel, with no DPA and no data locations (20). No deprecation policy. The terms promise email notice of changes (3). Subprocessors named, locations not (12). 10 + 20 + 3 + 12 = 45.); Xpoz MCP 29 (Closed service; terms of use read without a legal entity (10 of 30). Data handling not read (5 of 30). No deprecation policy (0). Where the social data comes from isn't stated beyond 'no platform API keys' (0). 10 + 5 + 0 + 0 = 15.)
- Payments & pricing, Xpoz MCP +15: 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.); Xpoz MCP 30 (No machine payment protocol (0). Plan prices public (10). Free 500 credits (20). A person signs in for a key (0). 0 + 10 + 20 + 0 = 30.)
- Schema & documentation, Post Bridge API + MCP +8: 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.); Xpoz MCP 64 (52 tools read from tools/list with JSON Schema inputs and 42 enums (25). No llms.txt read (0). Server instructions explain paging and field selection (16 of 20). Typed inputs with enums (15). Examples on the home page (5 of 15). Registry 1.4.1 from July, server 3.0.0; no changelog (3 of 15). 25 + 0 + 16 + 15 + 5 + 3 = 64.)
- 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.); Xpoz MCP 37 (One API key (20 of 30). 49 of 52 tools read-only (15 of 20). Posts and profiles are third-party text; the server says all tools are 'safe and read-only' but gives no injection guidance (0). No audit log (0). No security programme found (2 of 20). 20 + 15 + 0 + 0 + 2 = 37.)
- Maintenance & community, Post Bridge API + MCP +6: 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.); Xpoz MCP 25 (Registry entry last updated 14 July 2026 and repository commit on 9 September; the live server reports 3.0.0 (10). No dated releases in 90 days (0). Issues not read (0). Official registry entry ai.xpoz/social-insights (15). Docker packaging only (0). 10 + 0 + 0 + 15 + 0 = 25. 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.)