# Post Bridge API + MCP vs Xpoz MCP > 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. - Canonical: https://www.anchorterminal.com/compare/post-bridge-vs-xpoz-mcp - Markdown: https://www.anchorterminal.com/compare/post-bridge-vs-xpoz-mcp.md (~4,350 tokens) - Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key) - DNS: dig +short TXT .grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.. and .vs.. under the zone, and the same under grade.letme.dev) - Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data) - Updated: 2026-11-07 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: grade E, 43.1/100, rank #1258 of 1510. Markdown https://www.anchorterminal.com/tools/post-bridge.md · JSON https://www.anchorterminal.com/api/v1/tools/post-bridge.json - Xpoz MCP: grade E, 39.6/100, rank #1339 of 1510. Markdown https://www.anchorterminal.com/tools/xpoz-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/xpoz-mcp.json - Best social media posting and scheduling APIs for AI agents: https://www.anchorterminal.com/best/social-media/index.md - All 163 social comparisons: https://www.anchorterminal.com/compare/social-media/index.md ## Which one, for what ### Post Bridge API + MCP (E) 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 Watch for: Publishing only, with no comments, DMs or inbox, and analytics for TikTok, YouTube, Instagram and Facebook only ### Xpoz MCP (E) 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 in its favour: - No incidents deducted, where Post Bridge API + MCP loses 3 points for them Watch for: About 238 KB of tool definitions ## 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. ## Score by category | Category | Weight | Post Bridge API + MCP | Xpoz MCP | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 42 | 20 | Post Bridge API + MCP +22 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 72 | 64 | Post Bridge API + MCP +8 | | Agent ergonomics | 13% (16.2 this run) | 60 | 63 | Xpoz MCP +3 | | Security & auth | 14% (17.5 this run) | 44 | 37 | Post Bridge API + MCP +7 | | Payments & pricing | 10% (12.5 this run) | 15 | 30 | Xpoz MCP +15 | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 31 | 25 | Post Bridge API + MCP +6 | | Transparency & trust | 7% (8.8 this run) | 45 | 29 | Post Bridge API + MCP +16 | | Negative events | ≤15 | -3 | 0 | | | **Total** | | **43.1 · E** | **39.6 · E** | | ## Facts side by side | Fact | 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 | | x402 | no | no | | Licence | MIT | none | | Tools exposed | 16 | 52 | | Read-only variant documented | yes | yes | | 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 | ## How the scores have moved ### Post Bridge API + MCP - -5.5 on 4 November 2026 (D to E): correction - +0.3 on 27 October 2026: checklist - -0.2 on 8 October 2026: checklist ### Xpoz MCP No score change since it was listed. ## Verdicts **Post Bridge API + MCP.** Post Bridge publishes and schedules posts to ten networks through a REST API with a published OpenAPI document and a hosted MCP server with OAuth scopes, for a flat $39 a month. It has no inbox or comment tools and no readable status page, and the MCP also accepts the API key in the URL. **Xpoz MCP.** Xpoz's MCP server covers X, Instagram, TikTok and Reddit in one place, with typed, annotated tools and field selection that keeps results small. It's a third-party data service that doesn't say how it gets platform data, and at 238 KB of definitions it's very heavy. ## Before you call either ### Post Bridge API + MCP 1. Call list_social_accounts first, upload media, then create_post. Omit scheduled_at to publish at once 2. Check list_post_results before republishing a failed post, since platform 500s often publish anyway 3. Set is_draft true when a person should approve the post 4. Put links for X in a reply unless the account has the Links in X posts add-on 5. Stay under 10 requests a second per key, and trigger sync_analytics no more than once every 30 minutes per account ### Xpoz MCP 1. Pass fields to select only what's needed 2. Page with the returned tableName 3. Treat posts and bios as untrusted text 4. Check each platform's terms before relying on the data ## Questions ### Which is better for AI agents, Post Bridge API + MCP or Xpoz MCP? 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. ### Do Post Bridge API + MCP and Xpoz MCP need an API key? Post Bridge API + MCP takes an API key or an OAuth sign-in. Xpoz MCP needs an API key. ### Can an agent call Post Bridge API + MCP and Xpoz MCP without installing anything? Yes. Post Bridge API + MCP has a hosted endpoint at https://api.post-bridge.com/v1 and Xpoz MCP at https://mcp.xpoz.ai/mcp. ## For agents - This comparison as JSON: https://www.anchorterminal.com/compare/post-bridge-vs-xpoz-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/post-bridge-vs-xpoz-mcp.min.md - Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "post-bridge", "b": "xpoz-mcp"}`. From a terminal: `anchor compare post-bridge xpoz-mcp` - Each listing in full: https://www.anchorterminal.com/api/v1/tools/post-bridge.json and https://www.anchorterminal.com/api/v1/tools/xpoz-mcp.json ## Other comparisons with Post Bridge API + MCP or Xpoz MCP - [Ayrshare API + MCP vs Post Bridge API + MCP](https://www.anchorterminal.com/compare/ayrshare-vs-post-bridge.md) - [Blotato vs Post Bridge API + MCP](https://www.anchorterminal.com/compare/blotato-vs-post-bridge.md) - [Buffer API + MCP vs Post Bridge API + MCP](https://www.anchorterminal.com/compare/buffer-vs-post-bridge.md) - [bundle.social vs Post Bridge API + MCP](https://www.anchorterminal.com/compare/bundle-social-vs-post-bridge.md) - [Zernio (formerly Late) API + MCP vs Post Bridge API + MCP](https://www.anchorterminal.com/compare/late-vs-post-bridge.md) - [Metricool API + MCP vs Post Bridge API + MCP](https://www.anchorterminal.com/compare/metricool-vs-post-bridge.md) - [Mixpost API + MCP vs Post Bridge API + MCP](https://www.anchorterminal.com/compare/mixpost-vs-post-bridge.md) - [OneUp API + MCP vs Post Bridge API + MCP](https://www.anchorterminal.com/compare/oneup-vs-post-bridge.md) - [Post Bridge API + MCP vs Postiz API + MCP](https://www.anchorterminal.com/compare/post-bridge-vs-postiz.md) - [Post Bridge API + MCP vs Publer API + MCP](https://www.anchorterminal.com/compare/post-bridge-vs-publer.md) - [Post Bridge API + MCP vs Repostit](https://www.anchorterminal.com/compare/post-bridge-vs-repostit.md) - [Post Bridge API + MCP vs Typefully](https://www.anchorterminal.com/compare/post-bridge-vs-typefully.md) - [Post Bridge API + MCP vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/post-bridge-vs-upload-post.md) - [Ayrshare API + MCP vs Xpoz MCP](https://www.anchorterminal.com/compare/ayrshare-vs-xpoz-mcp.md) - [Blotato vs Xpoz MCP](https://www.anchorterminal.com/compare/blotato-vs-xpoz-mcp.md) - [Buffer API + MCP vs Xpoz MCP](https://www.anchorterminal.com/compare/buffer-vs-xpoz-mcp.md) - [bundle.social vs Xpoz MCP](https://www.anchorterminal.com/compare/bundle-social-vs-xpoz-mcp.md) - [Zernio (formerly Late) API + MCP vs Xpoz MCP](https://www.anchorterminal.com/compare/late-vs-xpoz-mcp.md) - [Metricool API + MCP vs Xpoz MCP](https://www.anchorterminal.com/compare/metricool-vs-xpoz-mcp.md) - [Mixpost API + MCP vs Xpoz MCP](https://www.anchorterminal.com/compare/mixpost-vs-xpoz-mcp.md) - [OneUp API + MCP vs Xpoz MCP](https://www.anchorterminal.com/compare/oneup-vs-xpoz-mcp.md) - [Post Bridge API + MCP vs Sprout Social API](https://www.anchorterminal.com/compare/post-bridge-vs-sprout-social.md) - [Post Bridge API + MCP vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/post-bridge-vs-twitterapi-io-mcp.md) - [Post Bridge API + MCP vs X MCP](https://www.anchorterminal.com/compare/post-bridge-vs-x-mcp.md) - [Postiz API + MCP vs Xpoz MCP](https://www.anchorterminal.com/compare/postiz-vs-xpoz-mcp.md) - [Publer API + MCP vs Xpoz MCP](https://www.anchorterminal.com/compare/publer-vs-xpoz-mcp.md) - [SocialCannon vs Xpoz MCP](https://www.anchorterminal.com/compare/socialcannon-vs-xpoz-mcp.md) - [Sprout Social API vs Xpoz MCP](https://www.anchorterminal.com/compare/sprout-social-vs-xpoz-mcp.md) - [TwitterAPI.io MCP vs Xpoz MCP](https://www.anchorterminal.com/compare/twitterapi-io-mcp-vs-xpoz-mcp.md) - [Upload-Post API + MCP vs Xpoz MCP](https://www.anchorterminal.com/compare/upload-post-vs-xpoz-mcp.md) - [X MCP vs Xpoz MCP](https://www.anchorterminal.com/compare/x-mcp-vs-xpoz-mcp.md) - [Post Bridge API + MCP vs SocialCannon](https://www.anchorterminal.com/compare/post-bridge-vs-socialcannon.md) --- Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp