# Repostit vs Upload-Post API + MCP > Upload-Post scores 58.9 (C) to Repostit's 32.5 (F) for social posting. Prices, MCP, x402, uptime and agent notes side by side. - Canonical: https://www.anchorterminal.com/compare/repostit-vs-upload-post - Markdown: https://www.anchorterminal.com/compare/repostit-vs-upload-post.md (~5,650 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 .grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.. and .vs.. 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-03 Upload-Post API + MCP scores 58.9 (C) on agent readiness against Repostit's 32.5 (F), and leads in 5 of 7 scored categories. Repostit leads on security & auth. Both do social posting. - Repostit: grade F, 32.5/100, rank #1191 of 1272. Markdown https://www.anchorterminal.com/tools/repostit.md · JSON https://www.anchorterminal.com/api/v1/tools/repostit.json - Upload-Post API + MCP: grade C, 58.9/100, rank #629 of 1272. Markdown https://www.anchorterminal.com/tools/upload-post.md · JSON https://www.anchorterminal.com/api/v1/tools/upload-post.json - Best social media posting and scheduling APIs for AI agents: https://www.anchorterminal.com/best/social-media/index.md - All 132 social comparisons: https://www.anchorterminal.com/compare/social-media/index.md ## Which one, for what ### Repostit (F) Good for: Creators, small businesses and agencies who post short vertical video on one network and want an assistant in Claude or ChatGPT to copy it to others on a schedule, set up reposting workflows and confirm what went out, without writing code. Ahead on: - Security & auth, 44 against 32 Watch for: No tool names, input schemas, annotations, scopes or error shapes are published, and no public REST API, SDK or OpenAPI file exists ### Upload-Post API + MCP (C) 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 26 - Schema & documentation, 81 against 27 - Agent ergonomics, 72 against 25 - Maintenance & community, 79 against 56 - Transparency & trust, 73 against 29 Also in its favour: - Runs on your own machine Watch for: One account key with no scopes, and the MCP's OAuth grants a single mcp.full scope ## Why the edge ### Schema & documentation: Upload-Post API + MCP +54 - Repostit (27): MCP reading, since the connector is the only surface an outside agent reaches; no public REST API, developer page, OpenAPI file, SDK or package was found in the help centre, /whats-new/, the sitemap, llms.txt, GitHub, npm or the MCP registry. No tool names or input schemas are published anywhere, and no session was opened to read them (0 of 25). llms.txt exists, but it is a Rank Math index of site URLs that includes theme placeholder entries, and help articles are HTML only (5 of 10). The Claude connector page says what each step is for and when not to use it, list accounts before choosing a destination, a Brief saves a draft and neither publishes nor schedules, publishing applies to every destination in a Brief, Queued is not delivery, future-content workflows publish once active while existing-content ones import for review (8 of 20). Inputs are described in prose only, formats per destination, JPEG, PNG or WebP up to 20 MB, carousel caps of 4, 10 and 20 by network, media at a downloadable HTTPS URL and a timezone with every scheduled time (4 of 15). Plain-language example requests and per-network failure reasons written for people; no example tool call, response or error shape (5 of 15). The endpoint path carries v1.1 and the registry holds 2026.10.17 and 2026.10.23; /whats-new/ is undated and no changelog was found (5 of 15). 0+5+8+4+5+5 = 27. - Upload-Post API + MCP (81): OpenAPI 3.0.1 at docs.upload-post.com/openapi.json with 22 paths, fewer than the API's documented surface, and zod input and output schemas on all 59 MCP tools in source (22). llms.txt indexing about 80 pages, plus llms-full.txt (10). Tool descriptions in source say which IDs each network needs and when to add a parameter rather than reach for another tool (17). Enums, defaults and bounds such as limit 1 to 50 on comments (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 and PyPI shows dated versions (8). ### Agent ergonomics: Upload-Post API + MCP +47 - Repostit (25): MCP reading. The tool count is not published. The connector pages describe seven actions (list accounts, create, schedule and publish a Brief, check delivery, create a workflow, send a connection link), which suggests a small set, but the definitions were not read, so a middle reading rather than full marks (10 of 25). No pagination, filtering or output-size controls are documented (0 of 20). Delivery checks report a result per destination with public links when the network gives one, and the help centre lists failure reasons per network, but no error codes or connector error messages are documented (5 of 20). No idempotency key and no readOnlyHint or destructiveHint seen; Briefs start as drafts, queued Briefs are locked against a second send, Manual workflows hold posts for approval and the guidance says to check before retrying (6 of 20). Requests are made in plain language with few stated requirements (an HTTPS media URL, a timezone); no SDK in any language (4 of 15). 10+0+5+6+4 = 25. - Upload-Post API + MCP (72): 59 MCP tools with no toolsets or dynamic loading (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, 13 of them marked destructive (18). Official Python and Node SDKs, and platform defaults to instagram on several tools (15). ### Transparency & trust: Upload-Post API + MCP +44 - Repostit (29): Closed service. The terms of service (effective 7 March 2025, no revision since) name Repostit LLC of Newark, Delaware, with Delaware law and arbitration, take a non-exclusive licence to content only to run the service and say fees are non-refundable; every footer says Repostit, Inc., and the terms do not mention the connector (12 of 30). The privacy policy (29 July 2026) keeps data until the account is deleted or as needed, with no periods, deletes Pinterest credentials on disconnect but says nothing of other networks' tokens, names no DPA, and does not mention the connector or its 90-day offline access; the account deletion article gives no timeline and leaves network-side access to the user (10 of 30). No deprecation policy or dated notices; the terms promise notice of significant changes and the ChatGPT page names a pending version 1.1 without a date (3 of 20). Subprocessors are 'hosting providers, analytics services', unnamed, with transfers outside the user's country and no locations; the Tawk.to chat on the contact page and the Google Cloud Run host of the connector are not named in the policy (2 of 20). 12+10+3+2 = 27. - Upload-Post API + MCP (73): Closed API under clear terms from TONVI TECH SL (CIF B-19780394, Málaga), version 2.5 updated 29 August 2026, with the MCP server and both SDKs under MIT (20). 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 (30). The terms promise at least 30 days' notice of material changes. 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). ### Reliability: Upload-Post API + MCP +31 - Repostit (26): Hosted reading, for the connector and the service behind it. No status page was found. None is linked from the help centre, the contact page, the footer or the troubleshooting articles, and https://repostit.io/status/ did not load through our reader, which also fails on the home page (0). No readable incident history, so the floor (5). Repostit publishes posting quotas rather than request limits, 10 posts on the trial, 10 video posts a month on Basic, existing-content workflows up to 5 posts a day, plus per-network rules and 20 MB images through the connector; no request rate for the connector, and the terms only bar automated access faster than a human (6 of 15). No 429 or overload handling is documented. The Claude connector page says Queued means accepted, not delivered, and to check the existing result before retrying to avoid duplicate posts, and Brief locks queued posts against a second send; no idempotency key and no page says failed posts are retried (5 of 15). No SLA; the terms (7 March 2025) let Repostit modify or discontinue the service at any time and say nothing on uptime (0). The connector carries no beta label and its registry entry is active (10). 0+5+6+5+0+10 = 26. - Upload-Post API + MCP (57): An own status page at upload-post.com/status that describes per-platform availability and uptime history, but loads 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 per the 30 September check (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 disclaim uninterrupted service (0). GA (10). ### Maintenance & community: Upload-Post API + MCP +23 - Repostit (56): Closed service. The latest registry version is 2026.10.23, published 23 October 2026, and the connector article was updated 22 October 2026 (30). Dated changes in the last 90 days are the two registry versions of 17 and 23 October 2026; /whats-new/ is undated and the ChatGPT app's 1.1.0 (per the 3 November listing check) carries no date, so fewer than three dated releases (10 of 20). Support is email and weekday chat, 9am to 5pm Eastern, with replies within 24 hours; no public changelog with dates, forum or issue tracker (6 of 15). In the official MCP registry as io.github.hax98/repostit, a GitHub-verified namespace of a personal account; the entry links Repostit's own pages and its address matches the vendor's connector page, but no first-hand page ties the account to the company, so partial credit (10 of 15). No packages, public code or CI to judge (0 of 10). 30+10+6+10+0 = 56. - Upload-Post API + MCP (79): MCP tag v0.11.4 on 27 September 2026 and a 0.11.5 commit on 1 October, Python SDK 2.13.0 on 9 September (30). 16 MCP tags on commits since 9 July and four Python SDK releases since 20 July (20). The MCP repo has had 14 pull requests, and commits landed in 11 of the last 13 weeks. robots.txt kept us from the issue tracker, and there's no public API changelog (10). Official registry entry com.upload-post/mcp under its own domain, latest 0.10.0 on 3 September (15). A publish workflow with npm provenance but no test CI, and npm's latest tag read 0.11.1 while git tags run to v0.11.4 (4). ### Security & auth: Repostit +12 - Repostit (44): OAuth with dynamic client registration and no client secret, per Repostit's Claude connector page, with offline access that renews for up to 90 days from the first authorisation; social-network sign-ins stay in Repostit and provider tokens are not passed to the assistant. PKCE S256 is stated only in third-party metadata. No scopes are named; the page lists the permissions shown at sign-in (read accounts, create workflows and Briefs, schedule or publish, read delivery status). Revocation is by disconnecting in the client or asking support (18 of 30). A Brief is saved as a draft, Manual workflows wait for approval, and the help article says the assistant shows each step for confirmation before publishing (on ChatGPT 'may ask', depending on the client); no read-only mode, and an activated future-content workflow publishes on its own (8 of 20). Tools return the user's own accounts, Briefs and delivery results and read no comments or messages (10). Assistant-created posts appear under Post with a Comments & Activity log of each step, and Post History shows each network's response; no per-call log for the connector (8 of 15). security.txt did not load through our reader, and no disclosure policy, bug bounty or certification appears on any page read (0 of 20). 18+8+10+8+0 = 44. - Upload-Post API + MCP (32): One account API key sent as Apikey or Bearer in a header, no query-string option, no scopes, and the docs advise generating a new key periodically without describing revocation. The MCP's OAuth 2.1 (PKCE and dynamic registration) has a single mcp.full scope that resolves to the account key. JWT connect links let end users link accounts without seeing the key (18). No read-only key or scope, though the annotations mark the 13 destructive tools (6). get_post_comments, list_dm_conversations and get_google_business_reviews return text from strangers, and we found no prompt-injection guidance in the docs or tool descriptions (0). get_history and get_status show past uploads and request results, no audit log (5). No security.txt, disclosure route or certification. npm releases publish with provenance through OIDC (3). ## Score by category | Category | Weight | Repostit | Upload-Post API + MCP | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 26 | 57 | Upload-Post API + MCP +31 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 27 | 81 | Upload-Post API + MCP +54 | | Agent ergonomics | 13% (16.2 this run) | 25 | 72 | Upload-Post API + MCP +47 | | Security & auth | 14% (17.5 this run) | 44 | 32 | Repostit +12 | | 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) | 56 | 79 | Upload-Post API + MCP +23 | | Transparency & trust | 7% (8.8 this run) | 29 | 73 | Upload-Post API + MCP +44 | | Negative events | ≤15 | 0 | 0 | | | **Total** | | **32.5 · F** | **58.9 · C** | | ## Facts side by side | Fact | Repostit | Upload-Post API + MCP | | --- | --- | --- | | Kind | Platform | HTTP API | | Vendor | Repostit LLC | Upload-Post | | Hosted endpoint | `https://repostit-mcp-cfjcykgqda-uc.a.run.app/mcp/v1.1` | `https://api.upload-post.com/api` | | Transports | Streamable HTTP | HTTP, Streamable HTTP, stdio | | Auth | OAuth | OAuth or key | | Pricing | Paid | Freemium | | x402 | no | no | | Licence | Proprietary hosted service under Repostit's terms of service (effective 7 March 2025), which name Repostit LLC of Newark, Delaware. No source, SDK or package is published | MIT | | Tools exposed | none | 59 | | Read-only variant documented | no | no | | llms.txt | yes | yes | | MCP registry | `io.github.hax98/repostit` | `com.upload-post/mcp` | | Last release | 2026-10-23 | 2026-09-27 | | 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) | ## How the scores have moved ### Repostit No score change since it was listed. ### Upload-Post API + MCP - +0.2 on 3 November 2026: time - no change on 27 October 2026: checklist - -0.2 on 8 October 2026: checklist ## Verdicts **Repostit.** An OAuth connector lets an agent list accounts, draft and schedule posts, build reposting workflows and check delivery, with drafts saved before anything publishes and a 14-day trial without a card. Tool names, schemas, scopes and error shapes are unpublished, the endpoint sits on a Cloud Run host, and there is no status page, public API or named subprocessor. **Upload-Post API + MCP.** Free plan with 2 profiles and 10 uploads a month, no card. One account key with no scopes, and the MCP's OAuth grants a single mcp.full scope. ## Before you call either ### Repostit 1. List connected accounts first and confirm names and platforms with the user before choosing destinations; a missing account must be connected in Repostit Connections, not through the agent. 2. Pass media as a downloadable HTTPS URL, never a local filename, and give every scheduled time with an explicit timezone. 3. Treat Queued as accepted, not published; check delivery status and public links before reporting success, and check the existing result before any retry to avoid duplicate posts. 4. Creating a future-content workflow makes it publish on its own once active; prefer existing-content workflows or Manual mode when the user wants to review first. 5. On the trial, each destination counts as one of 10 posts and Basic allows 10 video posts a month; ask before fanning one Brief out to many networks. ### Upload-Post API + MCP 1. Send `Authorization: Apikey ` on REST. The MCP also takes Bearer 2. Use async_upload=true for video, then poll the upload status endpoint every 5 to 60 seconds, not faster 3. Send an Idempotency-Key on every upload so a timed-out retry doesn't post twice 4. Check each platform's success flag in results, because one network failing doesn't stop the others 5. Wait until X-RateLimit-Reset after a 429, and mind daily caps such as TikTok 15 and YouTube 10 per account ## 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, Repostit or Upload-Post API + MCP? Upload-Post API + MCP scores 58.9 (C) on agent readiness against Repostit's 32.5 (F), and leads in 5 of 7 scored categories. Repostit leads on security & auth. ### Can an agent call Repostit and Upload-Post API + MCP without installing anything? Yes. Repostit has a hosted endpoint at https://repostit-mcp-cfjcykgqda-uc.a.run.app/mcp/v1.1 and Upload-Post API + MCP at https://api.upload-post.com/api. ## For agents - This comparison as JSON: https://www.anchorterminal.com/compare/repostit-vs-upload-post.json, and with the fewest tokens: https://www.anchorterminal.com/compare/repostit-vs-upload-post.min.md - Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "repostit", "b": "upload-post"}`. From a terminal: `anchor compare repostit upload-post` - Each listing in full: https://www.anchorterminal.com/api/v1/tools/repostit.json and https://www.anchorterminal.com/api/v1/tools/upload-post.json ## Other comparisons with Repostit or Upload-Post API + MCP - [Ayrshare API + MCP vs Repostit](https://www.anchorterminal.com/compare/ayrshare-vs-repostit.md) - [Ayrshare API + MCP vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/ayrshare-vs-upload-post.md) - [Blotato vs Repostit](https://www.anchorterminal.com/compare/blotato-vs-repostit.md) - [Blotato vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/blotato-vs-upload-post.md) - [Buffer API + MCP vs Repostit](https://www.anchorterminal.com/compare/buffer-vs-repostit.md) - [Buffer API + MCP vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/buffer-vs-upload-post.md) - [bundle.social vs Repostit](https://www.anchorterminal.com/compare/bundle-social-vs-repostit.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 Repostit](https://www.anchorterminal.com/compare/late-vs-repostit.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 Repostit](https://www.anchorterminal.com/compare/metricool-vs-repostit.md) - [Metricool API + MCP vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/metricool-vs-upload-post.md) - [Mixpost API + MCP vs Repostit](https://www.anchorterminal.com/compare/mixpost-vs-repostit.md) - [Mixpost API + MCP vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/mixpost-vs-upload-post.md) - [OneUp API + MCP vs Repostit](https://www.anchorterminal.com/compare/oneup-vs-repostit.md) - [OneUp API + MCP vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/oneup-vs-upload-post.md) - [Post Bridge API + MCP vs Repostit](https://www.anchorterminal.com/compare/post-bridge-vs-repostit.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 Repostit](https://www.anchorterminal.com/compare/postiz-vs-repostit.md) - [Postiz API + MCP vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/postiz-vs-upload-post.md) - [Publer API + MCP vs Repostit](https://www.anchorterminal.com/compare/publer-vs-repostit.md) - [Publer API + MCP vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/publer-vs-upload-post.md) - [Repostit vs Typefully](https://www.anchorterminal.com/compare/repostit-vs-typefully.md) - [Typefully vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/typefully-vs-upload-post.md) - [Sprout Social API vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/sprout-social-vs-upload-post.md) - [Upload-Post API + MCP vs X MCP](https://www.anchorterminal.com/compare/upload-post-vs-x-mcp.md) - [Repostit vs SocialCannon](https://www.anchorterminal.com/compare/repostit-vs-socialcannon.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