# Upload-Post API + MCP vs Xpoz MCP

> 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.

- Canonical: https://www.anchorterminal.com/compare/upload-post-vs-xpoz-mcp
- Markdown: https://www.anchorterminal.com/compare/upload-post-vs-xpoz-mcp.md (~4,200 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 <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. 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

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: grade D, 50.6/100, rank #1054 of 1510. Markdown https://www.anchorterminal.com/tools/upload-post.md · JSON https://www.anchorterminal.com/api/v1/tools/upload-post.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

### Upload-Post API + MCP (D)

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 in its favour:
- Runs on your own machine
- Free to start without a card

Watch for: One account key with no scopes, and the MCP's OAuth grants a single mcp.full scope

### Xpoz MCP (E)

Good 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 Upload-Post API + MCP loses 9 points for them

Watch for: About 238 KB of tool definitions


## 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.

## Score by category

| Category | Weight | Upload-Post API + MCP | Xpoz MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 57 | 20 | Upload-Post API + MCP +37 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 81 | 64 | Upload-Post API + MCP +17 |
| Agent ergonomics | 13% (16.2 this run) | 72 | 63 | Upload-Post API + MCP +9 |
| Security & auth | 14% (17.5 this run) | 36 | 37 | Xpoz MCP +1 |
| Payments & pricing | 10% (12.5 this run) | 30 | 30 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 79 | 25 | Upload-Post API + MCP +54 |
| Transparency & trust | 7% (8.8 this run) | 73 | 29 | Upload-Post API + MCP +44 |
| Negative events | ≤15 | -9 | 0 | |
| **Total** | | **50.6 · D** | **39.6 · E** | |

## Facts side by side

| Fact | 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 |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| 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 |

## How the scores have moved

### Upload-Post API + MCP

- -8.3 on 4 November 2026 (C to D): security, product
- +0.2 on 3 November 2026: time
- no change on 27 October 2026: checklist

### Xpoz MCP

No score change since it was listed.

## Verdicts

**Upload-Post API + MCP.** Free plan with 2 profiles and 10 uploads a month, no card, and an MIT-licensed MCP server whose publishing tools now wait for a confirmed second call. One account key with no scopes, OAuth with a single mcp.full scope, and an October session-id flaw whose fix is in no release and off by default.

**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

### Upload-Post API + MCP

1. Send `Authorization: Apikey <key>` on REST. The MCP also takes Bearer; send the credential on every MCP request, since a session id alone isn't one
2. Call upload, DM and comment tools once for a preview, show it to the user, then repeat with confirmed: true
3. Use async_upload=true for video, then poll the upload status endpoint every 5 to 60 seconds, not faster
4. Send an Idempotency-Key on every upload so a timed-out retry doesn't post twice
5. Check each platform's success flag in results, because one network failing doesn't stop the others

### 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

## Tutorials

- [Schedule a LinkedIn announcement with Upload-Post](https://www.anchorterminal.com/tutorials/upload-post/), for Upload-Post API + MCP

## Questions

### Which is better for AI agents, Upload-Post API + MCP or Xpoz MCP?

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.

### Do Upload-Post API + MCP and Xpoz MCP need an API key?

Upload-Post API + MCP takes an API key or an OAuth sign-in. Xpoz MCP needs an API key.

### Can an agent call Upload-Post API + MCP and Xpoz MCP without installing anything?

Yes. Upload-Post API + MCP has a hosted endpoint at https://api.upload-post.com/api and Xpoz MCP at https://mcp.xpoz.ai/mcp.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/upload-post-vs-xpoz-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/upload-post-vs-xpoz-mcp.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "upload-post", "b": "xpoz-mcp"}`. From a terminal: `anchor compare upload-post xpoz-mcp`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/upload-post.json and https://www.anchorterminal.com/api/v1/tools/xpoz-mcp.json

## Other comparisons with Upload-Post API + MCP or Xpoz MCP

- [Ayrshare API + MCP vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/ayrshare-vs-upload-post.md)
- [Blotato vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/blotato-vs-upload-post.md)
- [Buffer API + MCP vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/buffer-vs-upload-post.md)
- [bundle.social vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/bundle-social-vs-upload-post.md)
- [Zernio (formerly Late) API + MCP vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/late-vs-upload-post.md)
- [Metricool API + MCP vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/metricool-vs-upload-post.md)
- [Mixpost API + MCP vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/mixpost-vs-upload-post.md)
- [OneUp API + MCP vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/oneup-vs-upload-post.md)
- [Post Bridge API + MCP vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/post-bridge-vs-upload-post.md)
- [Postiz API + MCP vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/postiz-vs-upload-post.md)
- [Publer API + MCP vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/publer-vs-upload-post.md)
- [Repostit vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/repostit-vs-upload-post.md)
- [Typefully vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/typefully-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 Xpoz MCP](https://www.anchorterminal.com/compare/post-bridge-vs-xpoz-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 Upload-Post API + MCP](https://www.anchorterminal.com/compare/sprout-social-vs-upload-post.md)
- [Sprout Social API vs Xpoz MCP](https://www.anchorterminal.com/compare/sprout-social-vs-xpoz-mcp.md)
- [TwitterAPI.io MCP vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/twitterapi-io-mcp-vs-upload-post.md)
- [TwitterAPI.io MCP vs Xpoz MCP](https://www.anchorterminal.com/compare/twitterapi-io-mcp-vs-xpoz-mcp.md)
- [Upload-Post API + MCP vs X MCP](https://www.anchorterminal.com/compare/upload-post-vs-x-mcp.md)
- [X MCP vs Xpoz MCP](https://www.anchorterminal.com/compare/x-mcp-vs-xpoz-mcp.md)
- [SocialCannon vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/socialcannon-vs-upload-post.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp