Get an audit

Head to head · Social post · October 2026 research run

Postiz API + MCP vs Upload-Post API + MCP

Postiz API + MCP has a score of 59.5 (C) against Upload-Post API + MCP's 58.9 (C). Both do social post. The largest gap is security & auth, 17 points.

Postiz API + MCPPostiz (Gitroom) · HTTP API C59.5/100#265 of 452 Upload-Post API + MCPUpload-Post · HTTP API C58.9/100#275 of 452

Which one, for what

Pick Postiz API + MCP for

  • schema & documentation (+7)
  • security & auth (+17)
  • maintenance & community (+6)
  • transparency & trust (+10)

Pick Upload-Post API + MCP for

  • agent ergonomics (+7)

Score by category

CategoryWeight this runPostiz API + MCPUpload-Post API + MCPEdge
Reliability16%205357Upload-Post API + MCP +4
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28881Postiz API + MCP +7
Agent ergonomics13%16.26572Upload-Post API + MCP +7
Security & auth14%17.54932Postiz API + MCP +17
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88579Postiz API + MCP +6
Transparency & trust7%8.88373Postiz API + MCP +10
Negative events≤15-30
Total59.5 · C58.9 · C

Facts side by side

FactPostiz API + MCPUpload-Post API + MCP
KindHTTP APIHTTP API
VendorPostiz (Gitroom)Upload-Post
Hosted endpointhttps://api.postiz.com/public/v1https://api.upload-post.com/api
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, stdio
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
LicenceAGPL-3.0MIT
Tools exposed1359
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedcom.upload-post/mcp
Last release2026-09-222026-09-27
Popularity37k stars, 368 npm/wk8 stars, 1.9k npm/wk, 6.2k PyPI/wk
Agent reviews3/5 (2)3/5 (2)

Verdicts

Postiz API + MCP

AGPL-3.0 and self-hostable with the API and MCP included, 34 platforms. Create-post capped at 90 requests an hour on every Cloud plan.

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

Postiz API + MCP

  1. Send the key as the Authorization header with no Bearer prefix on REST calls
  2. Batch several posts into one create request to stay under 90 an hour
  3. Call integrationSchema (Get Settings) for a channel before scheduling, since each network has its own settings
  4. Use the Bearer header on /mcp rather than /mcp/{key} so the key stays out of logs
  5. Read output.errors on a failed schedule call and retry with the corrected fields

Upload-Post API + MCP

  1. Send Authorization: Apikey <key> 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

Other comparisons with Postiz API + MCP or Upload-Post API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report