Ayrshare API + MCP vs Repostit

Ayrshare API + MCP 73

Instatus page at status.ayrshare.com with API, dashboard, link shortener and 13 per-network components (20). The history it shows runs from August, with two minor incidents, 45 minutes of latency on 11 August that errored a small number of posts and a 46-minute Pinterest partial outage on 14 August that Ayrshare put down to Pinterest (20). 300 requests per 5 minutes per user profile and 8 profile deletions a second (15). 429s come with x-ratelimit-max and x-ratelimit-count headers and advice to retry with backoff, but no Retry-After, no idempotency key for posts, and 1,000 429s in 24 hours suspends the profile (8). The pricing page claims 99.99 per cent API uptime, and we found no SLA terms behind it (0). REST is GA (10).

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.

Ayrshare API + MCP 74

Closed service with published terms (15). Privacy policy updated 20 August 2026 names Neverminds Solution LLC of Wilmington, deletes most data after account deletion and the rest within 30 days (90 if complex), references a DPA and names some processors such as Stripe, Cloudflare, Intercom and HubSpot, but gives no full list (20). Breaking changes and Meta metric retirements are dated in the changelog, with no stated notice period (14). Some subprocessors named, no data locations (8).

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.

Ayrshare API + MCP 69

27 MCP tools with no toolsets or read-only subset (15). Get Messages returns 100-message pages with a cursor, and analytics take quarters and daily parameters (15). Error codes say whether to retry, for example 479 non-retryable and 499 retryable, and explain_error decodes them (18). No idempotency key and no readOnlyHint or destructiveHint annotations. validate_post gives a dry run and retry_post resubmits a failed post (6). Official Node and Python SDKs, and a post needs little more than text and platforms (15).

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.

Ayrshare API + MCP 69

No OpenAPI spec. A GraphQL endpoint with a typed schema arrived on 29 September 2026, alongside a Postman collection, so partial credit (15). llms.txt indexes about 300 Markdown pages (10). The MCP tool catalogue gives each of the 27 tools one line and says nothing about when to use or avoid them (8). REST parameters are documented page by page, but the MCP server is closed and we didn't read its input schemas (8). Numbered error codes such as 101, 416, 419, 476 and 479, examples on endpoint pages, and an explain_error tool (13). Dated changelog with entries several times a week and breaking changes called out (15).

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.

Ayrshare API + MCP 77

Last API change on 29 September 2026, the GraphQL endpoint and error code 479 (30). Dozens of dated changelog entries since July (20). The changelog moves several times a week and support runs by email and chat (12). Official SDKs exist in Node and Python, both at 1.3.0 since May 2026 (10). The Node package is MIT with node 18 or later stated. We didn't see its CI (5).

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.

Ayrshare API + MCP 26

One account API key as a Bearer header, with a Profile-Key header to act for a sub-profile. No scopes, no OAuth on the hosted MCP and no documented rotation, so close to one all-powerful key (12). No read-only mode, no tool annotations and no approval step, though validate_post is a dry run (3). get_comments and get_messages hand comments and DMs from strangers to the agent, and we found no prompt-injection guidance (0). Dashboard 3.0 has post history search and a webhook events tab (7). A security help page claims AES encryption at rest and TLS 1.3 with a post-quantum key exchange, and a DPA exists. No security.txt, disclosure policy, bug bounty or certification found (4).

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.