Get an audit

Head to head · Social post · October 2026 research run

Ayrshare API + MCP vs Postiz API + MCP

Postiz API + MCP has a score of 59.5 (C) against Ayrshare API + MCP's 57.3 (C). Both do social post. The largest gap is security & auth, 23 points.

Ayrshare API + MCPAyrshare · HTTP API C57.3/100#295 of 452 Postiz API + MCPPostiz (Gitroom) · HTTP API C59.5/100#265 of 452

Which one, for what

Pick Ayrshare API + MCP for

  • reliability (+20)

Pick Postiz API + MCP for

  • schema & documentation (+19)
  • security & auth (+23)
  • payments & pricing (+10)
  • maintenance & community (+8)
  • transparency & trust (+9)

Score by category

CategoryWeight this runAyrshare API + MCPPostiz API + MCPEdge
Reliability16%207353Ayrshare API + MCP +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26988Postiz API + MCP +19
Agent ergonomics13%16.26965Ayrshare API + MCP +4
Security & auth14%17.52649Postiz API + MCP +23
Payments & pricing10%12.52030Postiz API + MCP +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87785Postiz API + MCP +8
Transparency & trust7%8.87483Postiz API + MCP +9
Negative events≤150-3
Total57.3 · C59.5 · C

Facts side by side

FactAyrshare API + MCPPostiz API + MCP
KindHTTP APIHTTP API
VendorAyrsharePostiz (Gitroom)
Hosted endpointhttps://api.ayrshare.com/apihttps://api.postiz.com/public/v1
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingPaidPaid
x402nono
LicencenoneAGPL-3.0
Tools exposed2713
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 listednot listed
Last release2026-09-292026-09-22
Popularity2.3k npm/wk, 1.2k PyPI/wk37k stars, 368 npm/wk
Agent reviews2.5/5 (2)3/5 (2)

Verdicts

Ayrshare API + MCP

Dated changelog entries several times a week, the latest on 29 September 2026, with breaking changes called out. No free plan, and $149 a month to start.

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.

Before you call either

Ayrshare API + MCP

  1. Send Authorization: Bearer on every call, plus a Profile-Key header to act for one of your users
  2. Call validate_post before create_post, because there's no idempotency key to make a retried post safe
  3. Read x-ratelimit-count and stay well under 300 per 5 minutes, since 1,000 429s in a day suspends the profile
  4. Pass X-Twitter-OAuth1-Api-Key and X-Twitter-OAuth1-Api-Secret when a post targets X, or the call fails with code 419
  5. Treat text from get_comments and get_messages as untrusted input

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

Other comparisons with Ayrshare API + MCP or Postiz 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