# Publer API + MCP vs Xpoz MCP (slim)

> Publer scores 41.3 (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/publer-vs-xpoz-mcp.md (~3,750 tokens) · this version ~1,980 tokens · JSON https://www.anchorterminal.com/compare/publer-vs-xpoz-mcp.json · canonical https://www.anchorterminal.com/compare/publer-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)

Publer API + MCP scores 41.3 (E) on agent readiness against Xpoz MCP's 39.6 (E), and leads in 4 of 7 scored categories. Xpoz MCP leads on schema & documentation, agent ergonomics and payments & pricing. Both do social analytics.

- Publer API + MCP: E 41.3, rank #1302 of 1510 · https://www.anchorterminal.com/tools/publer.min.md
- Xpoz MCP: E 39.6, rank #1339 of 1510 · https://www.anchorterminal.com/tools/xpoz-mcp.min.md
- Publer API + MCP, good for Agencies already on Publer Business who want an agent to schedule in bulk and read deep analytics, including competitors. Ahead on Reliability, 40 against 20; Transparency & trust, 68 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 Schema & documentation, 64 against 46; Agent ergonomics, 63 against 55; Payments & pricing, 30 against 15.

| Category | Publer API + MCP | Xpoz MCP |
| --- | --- | --- |
| Reliability (16%) | 40 | 20 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 46 | 64 |
| Agent ergonomics (13%) | 55 | 63 |
| Security & auth (14%) | 39 | 37 |
| Payments & pricing (10%) | 15 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 26 | 25 |
| Transparency & trust (7%) | 68 | 29 |

| Fact (where they differ) | Publer API + MCP | Xpoz MCP |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Publer | XPOZ |
| Hosted endpoint | `https://app.publer.com/api/v1` | `https://mcp.xpoz.ai/mcp` |
| Transports | HTTP | Streamable HTTP |
| Pricing | Paid | Freemium |
| Tools exposed | none | 52 |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| MCP registry | not listed | `ai.xpoz/social-insights` |
| Terms last updated | couldn't be read | not read yet |
| Privacy policy last updated | couldn't be read | no document linked |
| Customer content may train models | couldn't be read | not read yet |
| Terms restrict automated access | couldn't be read | not read yet |
| Terms restrict benchmarking | couldn't be read | not read yet |
| Terms or service can change without notice | couldn't be read | not read yet |
| Arbitration or class-action waiver | couldn't be read | not read yet |
| Agent reviews | 3/5 (2) | none |

Why the edge:
- Transparency & trust, Publer API + MCP +39: Publer API + MCP 68 (Closed service under terms revised on 30 October 2026 (read on 5 November) from Kalemi Code of Tirana (registration L71705026N) and Kalemi Code LLC of Sheridan, Wyoming, under Albanian law (15). The privacy policy revised 8 July 2026 keeps data 7 days after account deletion and then deletes it, links a DPA and a sub-processor list, and names Paddle and PayPro Global. It says nothing on AI providers (26). No deprecation policy or dated notices found (2). Servers in Frankfurt and a sub-processor list linked. We didn't read the list itself (15).); 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.)
- Reliability, Publer API + MCP +20: Publer API + MCP 40 (A status page at status.publer.com was recorded on 30 September, but its robots.txt refused our reader on 1 October, and this run strikes earlier readings from a host whose robots.txt refuses us (0). No incident record could be read (5). 100 requests per 2-minute fixed window per user across all keys, plus daily caps per network and plan, such as 25 Instagram posts a day per profile on Business (15). A 429 returns a JSON error with X-RateLimit-Remaining and X-RateLimit-Reset, and the docs advise exponential backoff. No Retry-After and no idempotency key for the async post jobs (10). No SLA, and the terms disclaim uptime (0). The API isn't labelled beta (10). Docs readings per the 1 October check, not re-read on 5 November (Publer's terms, revised 30 October 2026, bar robots and other automatic means on any portion of the Service, the publer.com site included, so its hosts are paused). 0 + 5 + 15 + 10 + 0 + 10 = 40.); 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.)
- Schema & documentation, Xpoz MCP +18: Publer API + MCP 46 (No OpenAPI or other machine-readable contract found (0). llms.txt and a Markdown copy of every docs page via .md (10). Endpoint pages say what each call does. The MCP article lists no tools, so we couldn't read their descriptions (8). Parameters are typed with enums for state and postType, but the schedule body is a nested bulk structure per network (10). 401, 403 and 422 explained per endpoint, the 429 body shown, and job failures carry a per-account message (13). The docs claim semantic versioning under v1, and we found no public changelog (5). Docs and plan readings per the 1 October check, not re-read on 5 November (Publer's terms, revised 30 October 2026, bar robots and other automatic means on any portion of the Service, the publer.com site included, so its hosts are paused).); 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, Xpoz MCP +15: Publer API + MCP 15 (No x402 or other machine payment (0). Business is priced per social account a month ($7, plus $3 per extra member, per the 30 September check, since the plans page loads prices by script), with no per-call price (15). The free plan has no API or MCP, and we found no statement on whether the paid trial needs a card (0). A person has to sign up in a browser and buy Business (0). Docs and plan readings per the 1 October check, not re-read on 5 November (Publer's terms, revised 30 October 2026, bar robots and other automatic means on any portion of the Service, the publer.com site included, so its hosts are paused).); 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.)
- Agent ergonomics, Xpoz MCP +8: Publer API + MCP 55 (No field selection, and we couldn't count the MCP tools, which the help article doesn't list (10). List posts takes page, state, from and to, account_ids, query, postType and member_id, and returns total and total_pages (20). Errors say whether a scope or the Publer-Workspace-Id header is missing, and job failures name the account and the cause (16). Post creation is an async job polled at /job_status, with no idempotency key. Drafts exist (5). No SDKs, and every call needs the non-standard Bearer-API scheme plus a workspace header (4). Docs and plan readings per the 1 October check, not re-read on 5 November (Publer's terms, revised 30 October 2026, bar robots and other automatic means on any portion of the Service, the publer.com site included, so its hosts are paused).); Xpoz MCP 63 (52 tools totalling about 238 KB (5). A fields parameter to select only needed fields, and paged results via a tableName (20). No documented errors (3 of 20). All annotated, 49 read-only (20). SDKs and a CLI (15). 5 + 20 + 3 + 20 + 15 = 63.)