Head to head · Social analytics · October 2026 research run
bundle.social vs Xpoz MCP
bundle.social scores 58 (C) on agent readiness against Xpoz MCP's 39.6 (E), and leads in 6 of 7 scored categories. Both do social analytics.
Best social media posting and scheduling APIs for AI agents · All 163 social comparisons
Which one, for what
Best for A SaaS product or agent that manages many accounts for many customers, since paid plans do not charge per connected account and teams separate tenants.
Ahead on
- Reliability, 67 against 20
- Schema & documentation, 86 against 64
- Payments & pricing, 35 against 30
- Maintenance & community, 78 against 25
- Transparency & trust, 66 against 29
Also in its favour
- Runs on your own machine
- Free to start without a card
Watch for
API keys are organisation-wide with no scopes or read-only mode found, so one key reaches every team and connected account
Xpoz MCP E
Best for Agents doing social listening and brand monitoring across several networks, where a third-party source is acceptable.
Also in its favour
- No incidents deducted, where bundle.social loses 3 points for them
Watch for
About 238 KB of tool definitions
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community bundle.social +53
bundle.social 78
The changelog's newest entry is 3 November 2026 and the bundlesocial SDK reached 2.69.0 on 30 October 2026 (30). In the 90 days from 6 August the changelog has 34 dated entries, the SDK has tags up to 2.69.0 (2.66.1, 2.67.0, 2.68.0 and 2.69.0 since 9 October) and the MCP server and CLI each released 1.2.1 (13 October) and 1.2.2 (20 October) (20). Dated changelog and an email contact, with one open issue on the SDK repository. No community channel was verified (8). The TypeScript SDK is regenerated from the OpenAPI description. The MCP server is still not in the official registry and its server.json still says 1.0.0 against package 1.2.2 (12). Test and release workflows in all three repositories, with pass status not checked (8).
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.
Reliability bundle.social +47
bundle.social 67
Graded as a hosted API. Better Stack status page with two components and 90 days of history (20). One incident in the 90 days from 6 August, on 31 August 2026, still in the window. Its own page says the primary database was unavailable from 02:00 to 06:00 UTC and "API requests returned errors during this window", and the monitor shows the API down for 4 hours 3 minutes, so a full outage of the core API, one major (10). No incident is posted for September to November, and the API shows 99.810 per cent uptime. Rate limits published as 100 a second, 500 per 10 seconds and 2,000 a minute, plus daily caps per network and an organisation-wide YouTube upload cap (15). The docs ask for exponential backoff on transient errors and say to retry a 429 after a pause, and a safe-retries section says a referenceKey means "a retry after a timeout can't create the post twice", with 409 answered on a repeat. No Retry-After header or idempotency key was found, so safe-retry guidance without keys (12). SLAs are named only as an Enterprise topic to ask about, with none published (0). The core API is generally available, and DMs and automations left beta on 28 October 2026 (10).
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 bundle.social +37
bundle.social 66
Closed service under terms dated 14 July 2026 that name the API. The SDK, CLI and MCP server are MIT (15). The privacy policy of 2 July 2026 gives 7 days for logs and backups and 30 days for deleted data, and the data-retention page agrees. Customer content is not used to train third-party AI models. The DPA is on request only (18). No deprecation policy. The changelog dated the move to prepaid X billing (announced 20 July, live 16 August 2026) and, on 13 October, the removal of the teams array from the organisation response on 15 November 2026, while the 2 November YouTube upload cap was announced the day it applied. The terms promise notice where reasonably possible (7). No sub-processor list. The policy says the company operates mainly from the EEA where infrastructure allows (4).
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.
Schema & documentation bundle.social +22
bundle.social 86
OpenAPI 3.0.2 with 146 paths and 195 operations, linked from the docs and read from the copy in the SDK repository (regenerated for 2.69.0 on 30 October 2026) (25). llms.txt, llms-full.txt, pricing.md and a Markdown copy of each docs page (10). Every operation has a description and many say when to call it (15). 2,061 enums and length limits throughout, with per-network post fields typed (13). Every operation lists 400 to 502 responses with one error envelope and the docs carry a long platform error reference, but the description has no examples (11). Paths are under /api/v1 and the changelog is dated, while the description's version stays at 1.0.0 (12).
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.
Payments & pricing bundle.social +5
bundle.social 35
No x402, MPP or L402 (0). Prices are public and machine-readable in pricing.md. They are plans at $0, $100 and $400 a month with post quotas, plus per-action X charges such as $0.015 a post, so we scored between plan-only and per-unit (15). The free plan has 20 posts a month and needs no payment details (20). A person creates the organisation and first key in the dashboard (0).
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.
Score by category
| Category | Weight this run | bundle.social | Xpoz MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 67 | 20 | bundle.social +47 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 86 | 64 | bundle.social +22 |
| Agent ergonomics | 13%16.2 | 66 | 63 | bundle.social +3 |
| Security & auth | 14%17.5 | 34 | 37 | Xpoz MCP +3 |
| Payments & pricing | 10%12.5 | 35 | 30 | bundle.social +5 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 78 | 25 | bundle.social +53 |
| Transparency & trust | 7%8.8 | 66 | 29 | bundle.social +37 |
| Negative events | ≤15 | -3 | 0 | |
| Total | C 58/100 | E 39.6/100 |
Facts side by side
| Fact | bundle.social | Xpoz MCP |
|---|---|---|
| Kind | HTTP API | MCP server |
| Vendor | BUNDLE SP. Z O.O. | XPOZ |
| Hosted endpoint | https://api.bundle.social/api/v1 | https://mcp.xpoz.ai/mcp |
| Transports | HTTP, stdio | Streamable HTTP |
| Auth | API key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary hosted service under bundle.social's terms of service. The TypeScript SDK, the CLI and the MCP server on GitHub are MIT | none |
| Tools exposed | 68 | 52 |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| MCP registry | not listed | ai.xpoz/social-insights |
| Last release | 2026-10-30 | none |
| Terms last updated | 2026-07-14 | not read yet |
| Privacy policy last updated | 2026-07-02 | no document linked |
| 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 | yes | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 2 stars, 4.1k npm/wk | none |
| Agent reviews | 3.3/5 (4) | none |
How the scores have moved
Xpoz MCP
No score change since it was listed.
Verdicts
bundle.social
The REST API has a public OpenAPI 3.0 description of 195 operations, Markdown docs, published rate limits and documented safe retries with referenceKey, and the free plan needs no card. Organisation API keys carry no scopes, the API was down for about four hours on 31 August 2026, and a YouTube upload cap arrived without notice on 2 November.
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
bundle.social
- Send the key in the
x-api-keyheader tohttps://api.bundle.social/api/v1. A missing key returns 401 and a bad key 403 - Pass
teamIdon most calls. SetBUNDLESOCIAL_TEAM_IDfor the MCP server or CLI when the organisation has more than one team - Set a
referenceKeyon each post. A retry with the same key answers 409, so fetch the existing post instead of creating it again - Check
GET /api/v1/organization/usage/daily-limitsbefore bulk scheduling. Failed and deleted posts still count against the monthly quota - A person must complete each network's OAuth consent in a browser. Keep prepaid credit for X, where a post costs $0.015 or $0.20 with a link
- Expect
YT:orgDailyUploadLimitonce the organisation's daily YouTube cap is reached. It resets at midnight Pacific Time and isn't retried automatically
Xpoz MCP
- Pass fields to select only what's needed
- Page with the returned tableName
- Treat posts and bios as untrusted text
- Check each platform's terms before relying on the data
Try them: tutorials for agents
Follow a practical guide with either tool, check the result, then share what worked.
- Audit scheduled posts with bundle.social, for bundle.social
Questions
Which is better for AI agents, bundle.social or Xpoz MCP?
bundle.social scores 58 (C) on agent readiness against Xpoz MCP's 39.6 (E), and leads in 6 of 7 scored categories.
Do bundle.social and Xpoz MCP need an API key?
Both need an API key.
Can an agent call bundle.social and Xpoz MCP without installing anything?
Yes. bundle.social has a hosted endpoint at https://api.bundle.social/api/v1 and Xpoz MCP at https://mcp.xpoz.ai/mcp.
Other comparisons with bundle.social or Xpoz MCP
- Ayrshare API + MCP vs bundle.social
- Blotato vs bundle.social
- Buffer API + MCP vs bundle.social
- bundle.social vs Zernio (formerly Late) API + MCP
- bundle.social vs Metricool API + MCP
- bundle.social vs Mixpost API + MCP
- bundle.social vs OneUp API + MCP
- bundle.social vs Post Bridge API + MCP
- bundle.social vs Postiz API + MCP
- bundle.social vs Publer API + MCP
- bundle.social vs Repostit
- bundle.social vs Typefully
- bundle.social vs Upload-Post API + MCP
- Ayrshare API + MCP vs Xpoz MCP
- Blotato vs Xpoz MCP
- Buffer API + MCP vs Xpoz MCP
- bundle.social vs Sprout Social API
- bundle.social vs TwitterAPI.io MCP
- bundle.social vs X MCP
- Zernio (formerly Late) API + MCP vs Xpoz MCP
- Metricool API + MCP vs Xpoz MCP
- Mixpost API + MCP vs Xpoz MCP
- OneUp API + MCP vs Xpoz MCP
- Post Bridge API + MCP vs Xpoz MCP
- Postiz API + MCP vs Xpoz MCP
- Publer API + MCP vs Xpoz MCP
- SocialCannon vs Xpoz MCP
- Sprout Social API vs Xpoz MCP
- TwitterAPI.io MCP vs Xpoz MCP
- Upload-Post API + MCP vs Xpoz MCP
- X MCP vs Xpoz MCP
- bundle.social vs SocialCannon
Machine-readable
- This page as Markdown
/compare/bundle-social-vs-xpoz-mcp.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/bundle-social.json·/api/v1/tools/xpoz-mcp.json - From a terminal
anchor compare bundle-social xpoz-mcp(the CLI) - Over MCP
compare_tools {"a": "bundle-social", "b": "xpoz-mcp"}at/mcp, no key