TwitterAPI.io MCP vs X MCP

TwitterAPI.io MCP 78

12 compact tools, about 12 KB (15). Cursor-based paging on followers and search (18 of 20). 429 handling documented (10 of 20). All 12 annotated read-only (20). Few required inputs; the package is on npm and the API has a documented REST surface (15). 15 + 18 + 10 + 20 + 15 = 78.

X MCP 45

Per the 8 October check, not re-read on 4 November, apart from the xurl clone and the MCP page. The number of tools isn't published. One docs page lists six groups and another says XMCP exposes 200+ endpoints as tools, so context cost is not established (5 of 25). The API has max_results, pagination_token, field selection and expansions. Whether each MCP tool passes them through is unread (12 of 20). Errors are problem+json with a type URI, title and detail, and the xurl CHANGELOG (1.2.0) says the bridge turns transport and token failures into JSON-RPC errors keyed to the request (15 of 20). No idempotency keys, and no readOnlyHint or destructiveHint documented. The bridge refreshes the token and retries after a 401 (4 of 20). One npx line starts the bridge and the URL has a default, but each user first creates an app, registers a redirect URI and sets a 300-second startup timeout. Official XDKs exist for Python and TypeScript (9 of 15). 5+12+15+4+9 = 45.

TwitterAPI.io MCP 40

No status page found (0). No incident history (5). Per-account QPS limits documented by tier (15). 'Hitting the ceiling returns an HTTP 429 (no Retry-After header is sent). Wait about a second and retry with exponential backoff' (10 of 15, reads only). No SLA; the terms disclaim uninterrupted service (0). Not labelled beta (10). 0 + 5 + 15 + 10 + 0 + 10 = 40.

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.

TwitterAPI.io MCP 40

Registry entry io.twitterapi/mcp-server updated 6 November 2026 (30). No dated changelog (0). Support channel not checked (0 of 15). Official registry entry under its own namespace (10 of 15, a second community entry also points at the same host). No package health read (0). 30 + 0 + 0 + 10 + 0 = 40. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.

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.

TwitterAPI.io MCP 40

No machine payment protocol (0). Per-result prices public (20). Up to $1 in free credits, no card (20). A Google sign-in in a browser gets the key (0). 0 + 20 + 20 + 0 = 40.

X MCP 20

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.

TwitterAPI.io MCP 41

The MCP package is MIT on npm; the service is closed under terms from September 2025 that don't name the company, which appears in the footer as Prism Digital, LLC of Newark, Delaware (15). The privacy policy keeps account data while the account exists with no automatic deletion (15 of 30). No deprecation policy (0). Subprocessors not listed in the pages read (5 of 20). 15 + 15 + 0 + 5 = 35.

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.