# TwitterAPI.io MCP vs Upload-Post API + MCP (slim)

> Upload-Post scores 50.6 (D) to TwitterAPI.io MCP's 49.3 (D) for social analytics. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/twitterapi-io-mcp-vs-upload-post.md (~4,650 tokens) · this version ~2,580 tokens · JSON https://www.anchorterminal.com/compare/twitterapi-io-mcp-vs-upload-post.json · canonical https://www.anchorterminal.com/compare/twitterapi-io-mcp-vs-upload-post
- 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 TwitterAPI.io MCP's 49.3 (D), and leads in 4 of 7 scored categories. TwitterAPI.io MCP leads on agent ergonomics and payments & pricing. Both do social analytics.

- TwitterAPI.io MCP: D 49.3, rank #1101 of 1510 · https://www.anchorterminal.com/tools/twitterapi-io-mcp.min.md
- Upload-Post API + MCP: D 50.6, rank #1054 of 1510 · https://www.anchorterminal.com/tools/upload-post.min.md
- TwitterAPI.io MCP, good for Agents that need to read X posts, profiles and followers cheaply, where a third-party source is acceptable. Ahead on Agent ergonomics, 78 against 72; Payments & pricing, 40 against 30. Also No incidents deducted, where Upload-Post API + MCP loses 9 points for them.
- 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 40; Schema & documentation, 81 against 62; Maintenance & community, 79 against 40; Transparency & trust, 73 against 41. Also Runs on your own machine; Free to start without a card.

| Category | TwitterAPI.io MCP | Upload-Post API + MCP |
| --- | --- | --- |
| Reliability (16%) | 40 | 57 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 62 | 81 |
| Agent ergonomics (13%) | 78 | 72 |
| Security & auth (14%) | 37 | 36 |
| Payments & pricing (10%) | 40 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 40 | 79 |
| Transparency & trust (7%) | 41 | 73 |

| Fact (where they differ) | TwitterAPI.io MCP | Upload-Post API + MCP |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | Prism Digital, LLC | Upload-Post |
| Hosted endpoint | `https://mcp.twitterapi.io/mcp` | `https://api.upload-post.com/api` |
| Transports | Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Pricing | pay-per-use | Freemium |
| Licence | none | MIT |
| Tools exposed | 12 | 74 |
| Read-only variant documented | yes | no |
| MCP registry | `io.twitterapi/mcp-server` | `com.upload-post/mcp` |
| Last release | none | 2026-10-28 |
| Terms last updated | not read yet | 2026-10-02 |
| Privacy policy last updated | not read yet | 2026-09-04 |
| Customer content may train models | not read yet | yes, with an opt-out |
| Terms restrict automated access | not read yet | yes |
| Terms restrict benchmarking | not read yet | yes |
| Terms or service can change without notice | not read yet | yes |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | none | 8 stars, 1.9k npm/wk, 6.2k PyPI/wk |
| Agent reviews | none | 3/5 (2) |

Why the edge:
- Maintenance & community, Upload-Post API + MCP +39: TwitterAPI.io MCP 40 (Registry entry io.twitterapi/mcp-server updated 6 November 2026 (30). No dated changelog (0). Support channel not checked (0 of 15). Official registry entry under its own namespace (10 of 15, a second community entry also points at the same host). No package health read (0). 30 + 0 + 0 + 10 + 0 = 40. 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.); 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).)
- Transparency & trust, Upload-Post API + MCP +32: TwitterAPI.io MCP 41 (The MCP package is MIT on npm; the service is closed under terms from September 2025 that don't name the company, which appears in the footer as Prism Digital, LLC of Newark, Delaware (15). The privacy policy keeps account data while the account exists with no automatic deletion (15 of 30). No deprecation policy (0). Subprocessors not listed in the pages read (5 of 20). 15 + 15 + 0 + 5 = 35.); 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).)
- Schema & documentation, Upload-Post API + MCP +19: TwitterAPI.io MCP 62 (12 tools read from tools/list with JSON Schema inputs (25). llms.txt (10). Short descriptions of what each returns (10 of 20). Typed inputs with two enums (10 of 15). Examples on the docs page, errors described only as 429 (7 of 15). No changelog found (404); registry version 1.0.1 (0). 25 + 10 + 10 + 10 + 7 + 0 = 62.); 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).)
- Reliability, Upload-Post API + MCP +17: TwitterAPI.io MCP 40 (No status page found (0). No incident history (5). Per-account QPS limits documented by tier (15). 'Hitting the ceiling returns an HTTP 429 (no Retry-After header is sent). Wait about a second and retry with exponential backoff' (10 of 15, reads only). No SLA; the terms disclaim uninterrupted service (0). Not labelled beta (10). 0 + 5 + 15 + 10 + 0 + 10 = 40.); 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).)
- Payments & pricing, TwitterAPI.io MCP +10: TwitterAPI.io MCP 40 (No machine payment protocol (0). Per-result prices public (20). Up to $1 in free credits, no card (20). A Google sign-in in a browser gets the key (0). 0 + 20 + 20 + 0 = 40.); Upload-Post API + MCP 30 (Per the 1 October check, not re-read on 4 November (pricing page on a host paused under the terms). No x402 or other machine payment (0). Plan prices are public, with FFmpeg minutes and Shorts analyses per plan and a $19 a month X link add-on, but no per-call price (10). Free plan of 2 profiles and 10 uploads a month without TikTok, no card (20). A person has to sign up in a browser for the key, or approve OAuth in a client (0).)
- Agent ergonomics, TwitterAPI.io MCP +6: TwitterAPI.io MCP 78 (12 compact tools, about 12 KB (15). Cursor-based paging on followers and search (18 of 20). 429 handling documented (10 of 20). All 12 annotated read-only (20). Few required inputs; the package is on npm and the API has a documented REST surface (15). 15 + 18 + 10 + 20 + 15 = 78.); 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).)