Zernio (formerly Late) API + MCP vs TwitterAPI.io MCP

Zernio (formerly Late) API + MCP 87

@zernio/node v0.2.1420 and zernio-sdk v1.4.1476 tagged on 1 November 2026 in their repositories, and changelog entries the same day (30). Hundreds of releases and 241 changelog entries dated 1 October or later (20). Public changelog and support. The SDK repositories are generated, so issue replies weren't a useful signal (12). Official registry entry com.zernio/zernio under its own domain, version 1.0.0 published 25 May 2026, still the latest on 1 November (15). The Node SDK runs ci, generate and publish workflows and regenerates from the OpenAPI spec several times a day (10). 30+20+12+15+10 = 87.

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.

Zernio (formerly Late) API + MCP 80

Better Stack page at zernio-status.com with components for the API, each network, schedulers, webhooks, inbox and analytics, read through its RSS feed (20). From 3 August to 1 November 2026 the feed lists many incidents, each partial by its own text. The longest touching the API, on 8 October from 14:44 to 15:52 UTC, had some customers see the dashboard and API slow or time out. On 19 October post creation failed for 21 minutes, and on 26 October many API requests failed for about 20 minutes. Reddit has been unavailable since 19 October because Reddit blocked third-party apps, and other items hit one network, the inbox or webhooks. No full outage of everything and nothing over an hour that wasn't partial, so minor only (20). Limits published by tier, 60, 600 or 1,200 requests a minute, a per-second analytics window and per-network posting caps (15). 429 carries Retry-After and X-RateLimit headers, and an Idempotency-Key covers posts and other writes (15). The terms state no SLA (0). GA (10). 20+20+15+15+0+10 = 80.

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.

Zernio (formerly Late) API + MCP 71

Closed API under published terms (last updated 9 October 2026), with the Node SDK under Apache-2.0 (15). The privacy policy, updated 26 October 2026, deletes data within 30 days of account deletion, keeps other data as long as needed, says content reached through the MCP or API isn't used to train models, and links a subprocessor list. A public DPA (19 October 2026, replacing a version dated 2 July 2026) is part of the terms with no signature needed, names ZERNIO SOFTWARE SL as processor, and deletes customer personal data within 10 business days of the end of the service, with backups within 30 days and logs within 90. The privacy policy also sets token lifetimes and deletion on disconnect for Google and Microsoft data. The statements agree, though general account data is kept as long as needed (26). No deprecation policy in practice. The changelog says a breaking change ships only as a new path version, yet breaking changes ship inside v1 on the day they're marked, and old getlate.dev URLs still redirect (6). The subprocessor list (9 October 2026) names 25 providers with purpose, data and transfer safeguard, and gives 14 days' notice of changes. Core hosting and the database are in London, and 18 entries say the location is provider-managed and not pinned to one region (15). 15+26+6+15 = 62.

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.

Zernio (formerly Late) API + MCP 65

API keys as Bearer tokens, restricted keys created through POST /v1/api-keys with any of ten resource groups switched off or limited to chosen profiles, and OAuth 2.1 with dynamic client registration on the MCP with eight scopes such as posts:read and analytics:read (30). Read-only keys and scopes are possible, members can be limited to profiles, and tools are annotated, but we found no approval guidance for publishing (14). The inbox, comments and DM tools return text from strangers and we found no prompt-injection guidance (0). A unified activity log endpoint (GET /v1/logs) covers publishing, connections, webhooks and messaging, webhook delivery logs are listed, X-Request-Id is on every response, and the security overview describes an append-only audit log of team-management actions for the owner. API calls aren't attributed to a key in a log we found (11). The DPA and pricing page say the SOC 2 Type II report and GDPR paperwork are available on request through the trust centre at trust.zernio.com. No security.txt (404 on 1 November) and no disclosure route, and the privacy contact is a named person's email (10). 30+14+0+11+10 = 65.

TwitterAPI.io MCP 37

OAuth or a single API key per account (20 of 30). All tools are reads (12 of 20). Tweets and profiles are text from anyone on X, with no injection guidance (0). No audit log (0). No security.txt or programme found (5 of 20). 20 + 12 + 0 + 0 + 5 = 37.

Zernio (formerly Late) API + MCP 83

OpenAPI 3.1 at zernio.com/openapi.yaml, API version 1.431.1 on 1 November with 761 paths (25). llms.txt and Markdown pages (10). The MCP has a docs_search tool and annotated tools. We didn't read tool descriptions in source (12). Inputs typed in the spec with resource groups and enums (12). A shared ErrorResponse with a machine code and message, X-Request-Id on responses, examples on operations (12). Dated public changelog with JSON and RSS feeds and a changelog API, but breaking changes ship inside v1, 15 of them marked breaking_change from 2 to 29 October (12). 25+10+12+12+12+12 = 83.

TwitterAPI.io MCP 62

12 tools read from tools/list with JSON Schema inputs (25). llms.txt (10). Short descriptions of what each returns (10 of 20). Typed inputs with two enums (10 of 15). Examples on the docs page, errors described only as 429 (7 of 15). No changelog found (404); registry version 1.0.1 (0). 25 + 10 + 10 + 10 + 7 + 0 = 62.

Zernio (formerly Late) API + MCP 88

The tools page lists 20 core tools and says tools/list returns about 50 everyday ones, with search_tools and call_tool loading the long tail on demand (5 plus 10). Page and cursor pagination on list endpoints (20). ErrorResponse codes such as idempotency_conflict, and the MCP returns the list of accounts when account_id is ambiguous (18). Idempotency-Key with 24-hour keys and an Idempotent-Replayed header, plus readOnlyHint, destructiveHint and openWorldHint on tools (20). The SDKs page lists official clients in eight languages, including Node and Python (15). 15+20+18+20+15 = 88.

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.