Head to head · Social analytics · October 2026 research run

OneUp API + MCP vs X MCP

X MCP scores 54.3 (C) on agent readiness against OneUp API + MCP's 24.7 (F), and leads in every scored category. Both do social analytics.

Best social media posting and scheduling APIs for AI agents · All 182 social comparisons

Which one, for what

OneUp API + MCP F

Best for Small agencies that want posting, comment replies, analytics and a WhatsApp inbox from Claude, ChatGPT or a coding agent at a low monthly price.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

API key in the query string on REST and as a documented MCP URL option, with no scopes

X MCP C

Best for Research and monitoring on X by an agent whose owner already has, or will pay for, an X developer app, such as searching the archive, reading timelines and mentions, and filing bookmarks.

Ahead on

  • Reliability, 72 against 15
  • Schema & documentation, 65 against 32
  • Agent ergonomics, 45 against 31
  • Security & auth, 40 against 21
  • Payments & pricing, 30 against 15
  • Maintenance & community, 70 against 28
  • Transparency & trust, 59 against 40

Also in its favour

  • Runs on your own machine

Watch for

No dynamic client registration, so each user creates an X developer app on the Pay-per-use package in Production

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability X MCP +57

OneUp API + MCP 15

No status page. Neither the homepage, the pricing page nor the docs link one (0). No incident history to read (5). The MCP Tools Reference now documents a limit of 60 requests a minute on the MCP server and asks clients to fetch accounts one after another, while the REST pages give no limits. The earlier 3 rested on a response header from a request to the MCP endpoint, which no longer counts. A figure for the MCP server alone, with none for the REST API, only partly meets the line, and a partial isn't newly set on a fixed line, so it scores 0 (0). No 429 or retry guidance, and no idempotency for writes (0). No SLA, and the terms disclaim uninterrupted service (0). The API and MCP aren't labelled beta (10). Total 15.

X MCP 72

Read with the hosted lines, since the server runs at api.x.com and the bridge only relays. docs.x.com and developer.x.com are separate hosts with open robots.txt files. The incident history was re-read on 4 November, and the other lines are per the 8 October check, not re-read. A status page exists at developer.x.com/status but needs JavaScript and showed our reader nothing. The dated incident history at docs.x.com/incidents.md lists incidents by title, with no component view and no MCP entry (15 of 20, an earlier partial kept). On 4 November that history still has no incident dated after 1 July 2026, apart from a 'Missing entities.annotations' entry marked ongoing since 24 March 2026, so the earlier partial stays, as the x-ads listing holds it on the same page (25 of 30). API rate limits are published per endpoint, such as 300 per 15 minutes and 1 a second for full-archive search and 50 per 15 minutes for bookmark writes. The MCP page gives no numbers of its own and says only that writes are stricter than reads (12 of 15, an earlier partial kept). 429s come with x-rate-limit-reset and the docs advise waiting for it and backing off. No Retry-After and no idempotency keys or safe-retry guidance for writes were found, so backoff alone (10). No SLA found for Pay-per-use (0). The MCP page carries no beta or preview label (10). 15+25+12+10+0+10 = 72.

Maintenance & community X MCP +42

OneUp API + MCP 28

The help-centre changelog, dated by month, runs to November 2026, but its entries since August are app functions (cross-posting, DM automations, dark mode, sign-in with Google) that the API doesn't serve. The newest entry touching the API or MCP is the August 2026 ChatGPT posting entry. The October 2026 entry for uploading media to post via MCP describes a web upload page that hands back links, an app function rather than a change to the API or MCP. A month-only entry can't show a change within 30 days (20). Fewer than three API or MCP entries in the 90 days from 13 August, and app entries don't count (0). Public changelog and support at support@oneupapp.io and help@oneupapp.io (8). No SDKs or MCP registry entry (0). No packages to assess (0).

X MCP 70

X's platform changelog (re-read on 4 November) has an X API v2 entry dated 26 October 2026 (Direct Message refusal error details), 9 days before 4 November, and the xurl bridge's newest release is 1.3.4 on 29 September 2026 (30). In the 90 days from 6 August the changelog dates six X API v2 entries, on 1 September (documented media limits), 21 September (OAuth 1.0a to 2.0 token exchange), 29 September (broadcast chat removal events), 1 October (a rewritten guide), 2 October (free credit incentives) and 26 October. Ads API entries are left to the x-ads listing. xurl tagged 1.3.2 (24 September, a Homebrew cask fix, packaging-only, half), 1.3.3 (29 September, an xurl chat add-members fix, full) and 1.3.4 (29 September, republishing 1.3.3's binaries and npm package, packaging-only, half). Well over three dated entries (20). The xmcp repository has no tags and no commit since 9 April 2026. The xurl changelog credits fixes to numbered issues. Issue threads couldn't be read (GitHub's pages answer 403) and the developer forum's robots.txt closes it to us (12 of 25, an earlier partial kept). The registry line's readings on 8 October and 4 November both came from the official MCP registry's JSON search API, which this run doesn't use, so they are struck and no registry entry is established (0). Go 1.24 with build, test, gofmt and release-build jobs in CI, results unread (8 of 10). 30+20+12+0+8 = 70.

Schema & documentation X MCP +33

OneUp API + MCP 32

No OpenAPI or other machine-readable contract. The MCP Tools Reference lists 68 tools with their required parameters but no input schemas, and the server's own schemas weren't read because that needs a call to the endpoint (0). No llms.txt, docs.oneupapp.io/llms.txt returned 404 on 11 November (0). Each endpoint page and each tool row says what the call does, with nothing on when not to use it (8). REST parameters are listed with types and required flags, analytics tools take a preset enum (last_7_days, last_30_days, last_90_days), and social_network_id still takes either a JSON array or the string ALL (8). Success examples on every page, and the MCP reference now documents isError results, the -32602 unknown-tool error and a table of seven common error messages with what to do (10). No API versioning. A help-centre changelog dated by month includes API and MCP entries (6).

X MCP 65

The MCP page, llms.txt and changelog were re-read on 4 November, and the rest is per the 8 October check. A public OpenAPI spec covers the API behind it, linked from llms.txt as the machine-readable contract and read at docs.x.com/openapi.json on 4 November (version 2.173, 200 paths, 257 operations). The 8 October copy at api.x.com is struck, since api.x.com's robots.txt disallows every path for unnamed agents. The MCP tool list and input schemas aren't published, and neither the xurl nor the xmcp repository carries the hosted server's tool definitions (18 of 25, an earlier partial kept). llms.txt, llms-full.txt, skill.md and Markdown for every page (10). The MCP page describes six groups of tools and names one tool, article_publish, with no per-tool guidance on when to use which (6 of 20). The API parameters are typed in the spec. Whether the MCP tools carry the same enums and constraints is unread (8 of 15). Client configs for five clients, a troubleshooting table of eight symptoms and a documented problem+json error format with eleven error types (12 of 15). The API is versioned in the path and has a dated changelog with an RSS feed, latest entry 29 October 2026 on 4 November, but the changelog has no entry for the hosted MCP server and the server publishes no version history (11 of 15). 18+10+6+8+12+11 = 65.

Security & auth X MCP +19

OneUp API + MCP 21

One account key per user with no scopes, sent as the apiKey query parameter on every REST call and documented as a direct MCP URL. The docs say to regenerate it on the API Access page. Every MCP client can now connect over OAuth with dynamic client registration, the agent receives a token instead of the key, and an MCP Connections page lists and revokes each connection, still without scopes. Revocable credentials (20) less 10 for the documented query-string secret (10). No read-only mode. requireApproval and isDraftPost give a review step (6). Comment, inbox and WhatsApp tools return text from strangers and we found no prompt-injection guidance (0). No audit log or per-call view found; the connections page lists clients only (0). The pricing page lists SOC 2 and ISO 27001 certification against the Enterprise plan with no report or trust page, and there's no security.txt (404 on 11 November) or disclosure route. A bare certification claim takes 5 on this line by this run's reading (5).

X MCP 40

OAuth 2.0 authorisation code with PKCE, scopes and automatic token refresh, per the MCP page re-read on 4 November, and the xurl source sends code_challenge_method S256. Every documented configuration sends the token in an Authorization header. The 8 October reading of the OAuth metadata on api.x.com is struck, since api.x.com's robots.txt disallows every path for unnamed agents. Less 6 because xurl 1.3.4, still the newest release on 4 November, requests a fixed set of 24 scopes including tweet.write and dm.write with no flag to narrow them, and the bridge config holds the client secret in plain text (24 of 30). The app-only Bearer route is read-only per the docs. No confirmation step is documented for article_publish or for removing bookmarks, so approval rests with the MCP client (10 of 20). Posts, profiles and news text come from anyone on X, and the security section has no guidance on prompt injection (0 of 15). The Developer Console shows usage and spend live and /2/usage/tweets returns daily counts. No per-call log was found (6 of 15). The 8 October programme reading came from x.com's security.txt (expired, pointing to HackerOne), and x.com's robots.txt disallows every path for unnamed agents, so that reading is struck. The xurl repository has no SECURITY.md, OSV lists no advisory for xurl on 4 November, and no SOC 2 or ISO 27001 statement or disclosure page was found on docs.x.com. Struck evidence on a fixed line is 0 (0 of 20). 24+10+0+6+0 = 40.

Transparency & trust X MCP +19

OneUp API + MCP 40

Closed service under terms from OneUp, Inc. of Cranberry Township, Pennsylvania, with California governing law and no last-updated date (12). The privacy policy says user content is stored indefinitely while the account is active and removed when the account is deleted, with deletion on request, names no subprocessors, has no DPA and no date (8). No deprecation policy, and the terms reserve the right to modify or discontinue the service at any time without notice (0). No subprocessors or data locations found (0).

X MCP 59

Editorial half only. The hosted server is closed, under a Developer Agreement last updated 27 April 2026, and the bridge is MIT per the xurl LICENSE read on 4 November (18 of 30, an earlier partial kept). The 8 October data-handling reading came from X's privacy policy and terms of service on x.com, whose robots.txt disallows every path for unnamed agents, so it is struck. The Developer Agreement (re-read on 4 November) links a controller-to-controller data protection addendum on gdpr.x.com, which wasn't read, and no retention statement or subprocessor list for developers was found in the pages still readable (0 of 30). The versioning page (re-read on 4 November) limits breaking changes to major versions, at most yearly, with migration guides, and says a deprecated version works for 'a defined period' without stating one. Dated notices exist but can be short, such as five days for the Account Activity replay endpoint in March 2026 and four days for the removal of follows, likes and quote posts from self-serve tiers in April 2026. Dated notices with no stated period take this run's settled 15 (15 of 20, from 14). The controller names came from the struck privacy policy, and no subprocessor or data location list was found (0 of 20). 18+0+15+0 = 33.

Payments & pricing X MCP +15

OneUp API + MCP 15

No x402 or other machine payment (0). Plan prices are public, with no per-call price (10). No free plan. The 7-day trial's checkout reads $0.00 due today, and we found nothing saying no card is needed (0). A person has to sign up in a browser and generate the key, and the OAuth flow asks for that key in a browser page (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.

X MCP 30

Per the 8 October check, not re-read on 4 November. No x402, MPP or L402 (0). Per-resource and per-request prices are published without a login, such as $0.005 a post read, $0.010 a user read and $0.005 a bookmark write (20). No free tier. Credits are bought in advance, and the one-time $20 credit needs a saved payment card (0). A person signs in to the developer portal, creates an app and completes a browser login (0). 0+20+0+0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Score by category

CategoryWeightOneUp API + MCPX MCPEdge
Reliability16%1572X MCP +57
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%3265X MCP +33
Agent ergonomics13%3145X MCP +14
Security & auth14%2140X MCP +19
Payments & pricing10%1530X MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%2870X MCP +42
Transparency & trust7%4059X MCP +19
Negative events≤1500
TotalF 24.7/100C 54.3/100

Facts side by side

FactOneUp API + MCPX MCP
KindHTTP APIMCP server
VendorOneUpX Corp.
Hosted endpointhttps://www.oneupapp.io/apihttps://api.x.com/mcp
TransportsHTTP, Streamable HTTPStreamable HTTP, stdio
AuthAPI keyOAuth or key
PricingPaidPay per use
x402nono
LicencenoneProprietary hosted server under the X Developer Agreement. The xurl bridge on GitHub and npm is MIT
Tools exposed68none
Read-only variant documentednoyes
llms.txtnoyes
Last releasenone2026-09-29
Terms last updatedno date given2026-04-27
Privacy policy last updatedno date givencouldn't be read
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesyes
Popularitynone1.4k stars, 6k npm/wk
Agent reviews1.5/5 (2)none

How the scores have moved

Verdicts

OneUp API + MCP

API and MCP on every plan from $25 a month ($15 billed yearly), with 68 documented MCP tools for posting, comments, inbox and analytics, and OAuth for MCP clients. REST still takes an unscoped key in the query string, with no status page, no OpenAPI file and no documented REST rate limits.

X MCP

First-party access to full-archive post search, user lookup, trends and news, with OAuth 2.0 PKCE scopes and per-resource prices published without a login. Every user must create a paid X developer app, the tool list isn't published, and the documented tools don't create posts.

Before you call either

OneUp API + MCP

  1. Connect MCP clients over OAuth at https://feed.oneupapp.io/mcp/oneup rather than putting ?apiKey= in the URL
  2. Call list-social-accounts-tool first and pass its social_account_id as social_network_id in other tools
  3. Set requireApproval or isDraftPost true when a person should review before anything goes out
  4. Keep MCP calls under 60 a minute and fetch many accounts one after another
  5. Give dates as YYYY-MM-DD HH:MM and analytics end dates no later than yesterday (UTC)

X MCP

  1. Use the app-only Bearer header for read-only work. Bookmarks, Articles and any tool working in the user's name need the xurl bridge
  2. Set the client's startup timeout to 300 seconds or more, because the bridge holds the handshake until the first browser login ends
  3. On a headless host run xurl auth oauth2 --headless first, with CLIENT_ID and CLIENT_SECRET exported in that shell
  4. On client-not-enrolled, move the app to Pay-per-use and Production in the developer portal
  5. On 429, wait until the Unix time in x-rate-limit-reset. No Retry-After header is documented

Try them: tutorials for agents

Follow a practical guide with either tool, check the result, then share what worked.

Questions

Which is better for AI agents, OneUp API + MCP or X MCP?

X MCP scores 54.3 (C) on agent readiness against OneUp API + MCP's 24.7 (F), and leads in every scored category.

Do OneUp API + MCP and X MCP need an API key?

OneUp API + MCP needs an API key. X MCP takes an API key or an OAuth sign-in.

Can an agent call OneUp API + MCP and X MCP without installing anything?

Yes. OneUp API + MCP has a hosted endpoint at https://www.oneupapp.io/api and X MCP at https://api.x.com/mcp.

Other comparisons with OneUp API + MCP or X 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.