# Upload-Post API + MCP vs Xpoz MCP (slim)

> Upload-Post scores 50.6 (D) 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/upload-post-vs-xpoz-mcp.md (~4,200 tokens) · this version ~2,230 tokens · JSON https://www.anchorterminal.com/compare/upload-post-vs-xpoz-mcp.json · canonical https://www.anchorterminal.com/compare/upload-post-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)

Upload-Post API + MCP scores 50.6 (D) on agent readiness against Xpoz MCP's 39.6 (E), and leads in 5 of 7 scored categories. Both do social analytics.

- Upload-Post API + MCP: D 50.6, rank #1054 of 1510 · https://www.anchorterminal.com/tools/upload-post.min.md
- Xpoz MCP: E 39.6, rank #1339 of 1510 · https://www.anchorterminal.com/tools/xpoz-mcp.min.md
- Upload-Post API + MCP, good for Video-heavy publishing to TikTok, Reels and Shorts at a low price, and for white-label products that link end users through JWT connect pages. Ahead on Reliability, 57 against 20; Schema & documentation, 81 against 64; Agent ergonomics, 72 against 63; Maintenance & community, 79 against 25; Transparency & trust, 73 against 29. Also Runs on your own machine; Free to start without a card.
- Xpoz MCP, good for Agents doing social listening and brand monitoring across several networks, where a third-party source is acceptable. Also No incidents deducted, where Upload-Post API + MCP loses 9 points for them.

| Category | Upload-Post API + MCP | Xpoz MCP |
| --- | --- | --- |
| Reliability (16%) | 57 | 20 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 81 | 64 |
| Agent ergonomics (13%) | 72 | 63 |
| Security & auth (14%) | 36 | 37 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 79 | 25 |
| Transparency & trust (7%) | 73 | 29 |

| Fact (where they differ) | Upload-Post API + MCP | Xpoz MCP |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Upload-Post | XPOZ |
| Hosted endpoint | `https://api.upload-post.com/api` | `https://mcp.xpoz.ai/mcp` |
| Transports | HTTP, Streamable HTTP, stdio | Streamable HTTP |
| Auth | OAuth or key | API key |
| Licence | MIT | none |
| Tools exposed | 74 | 52 |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| MCP registry | `com.upload-post/mcp` | `ai.xpoz/social-insights` |
| Last release | 2026-10-28 | none |
| Terms last updated | 2026-10-02 | not read yet |
| Privacy policy last updated | 2026-09-04 | no document linked |
| Customer content may train models | yes, with an opt-out | not read yet |
| Terms restrict automated access | yes | not read yet |
| Terms restrict benchmarking | yes | 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 | 8 stars, 1.9k npm/wk, 6.2k PyPI/wk | none |
| Agent reviews | 3/5 (2) | none |

Why the edge:
- Maintenance & community, Upload-Post API + MCP +54: Upload-Post API + MCP 79 (MCP tags v0.17.1 and v0.17.2 on 28 October 2026, 7 days before this check (30). In the 90 days from 6 August, MCP tags v0.8.0 and v0.10.0 (31 August), v0.11.0 (7 September), v0.11.1 (9 September), v0.11.2 (25 September), v0.11.3 and v0.11.4 (27 September), v0.17.1 and v0.17.2 (28 October) (20). Commits landed in every week of October, under five author names. GitHub's issue pages answer 403 in this session, and there's no public API changelog (10). Official registry entry com.upload-post/mcp, carried from the 1 October reading; server.json in the repository declares that name at 0.17.3 (15). The only workflow publishes to npm on a tag with provenance and runs no tests; the repository's npm run check scripts aren't wired to CI. Versions 0.11.5 to 0.17.0 and 0.17.3 were bumped in package.json without tags, and npm couldn't be read to say which were published (4).); 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.)
- Transparency & trust, Upload-Post API + MCP +44: Upload-Post API + MCP 73 (Closed API under clear terms from TONVI TECH SL (CIF B-19780394, Málaga), version 2.7 updated 19 October 2026 (the page header says 2 October), with the MCP server under MIT (20). Per the 1 October check, not re-read on 4 November: the privacy policy updated 4 September 2026 gives retention per data type, from 30 days for backups and 90 days for logs, DMs and comments to 6 years for invoices, and links a DPA, which the 19 October terms now incorporate by reference (30). The terms still promise at least 30 days' notice of material changes to the terms. No API deprecation policy (8). Subprocessors named with countries, Hetzner in Germany for primary hosting, and the policy says full videos go to Google Gemini for the Shorts analyser (20).); 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, Upload-Post API + MCP +37: Upload-Post API + MCP 57 (Upload-Post's terms (version 2.7, 19 October 2026) bar automated scripts or bots from the Services, which they define to include the website, so the status page, docs and pricing weren't requested on 4 November and the 1 October readings stand, per the 1 October check, not re-read on 4 November. An own status page at upload-post.com/status that loaded its data by script and showed our reader only Loading status, so we couldn't see components (15). No readable incident history (5). X-RateLimit-Limit, Remaining and Reset headers, daily caps per account per network (Instagram 50, TikTok 15, YouTube 10, LinkedIn 20) and per-plan request limits (15). The rate-limits guide says to wait for X-RateLimit-Reset, back off exponentially and send an Idempotency-Key on every upload, though the error guide and spec don't mention the key and there's no Retry-After (12). No SLA, and the terms of 19 October still disclaim uninterrupted service (0). GA (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.)
- Schema & documentation, Upload-Post API + MCP +17: Upload-Post API + MCP 81 (Per the 1 October check, not re-read on 4 November (docs host paused under the terms): OpenAPI 3.0.1 at docs.upload-post.com/openapi.json with 22 paths, fewer than the API's documented surface. The MCP source on 4 November registers 74 tools, each with zod input and output schemas (22). llms.txt indexing about 80 pages, plus llms-full.txt (10). Tool descriptions in source say which IDs each network needs, when to add a parameter rather than reach for another tool, and since 0.17.0 which calls need the user's approval (17). Enums, defaults and bounds such as limit 1 to 50 on comments, and get_history rounds to the page sizes the API accepts (14). The error guide covers 400, 401, 404, 429 and 500 with a success and message shape and per-platform results, but no machine-readable codes (10). No API changelog. The MCP repo cuts GitHub releases with generated notes from tags (8).); 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.)
- Agent ergonomics, Upload-Post API + MCP +9: Upload-Post API + MCP 72 (74 MCP tools in source on 4 November (59 on 1 October), with no toolsets or dynamic loading; 0.13.0 added one tool per comment and AutoDM operation beside the combined comment_action and manage_autodms (5). Upload history pages by page and limit, cached analytics by cursor up to 200 items, comments by cursor and limit (20). Each platform reports its own success flag, so one failed network doesn't stop the rest, and the 401 message says how to fix the header. No error codes (14). An Idempotency-Key is recommended for uploads, and every MCP tool carries readOnlyHint and destructiveHint, 23 of them marked destructive (18). Official Python and Node SDKs, and platform defaults to instagram on several tools (15).); 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.)