# TwitterAPI.io MCP vs Xpoz MCP (slim)

> TwitterAPI.io MCP scores 49.3 (D) to Xpoz MCP's 39.6 (E) for social analytics. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/twitterapi-io-mcp-vs-xpoz-mcp.md (~3,100 tokens) · this version ~1,380 tokens · JSON https://www.anchorterminal.com/compare/twitterapi-io-mcp-vs-xpoz-mcp.json · canonical https://www.anchorterminal.com/compare/twitterapi-io-mcp-vs-xpoz-mcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

TwitterAPI.io MCP scores 49.3 (D) on agent readiness against Xpoz MCP's 39.6 (E), and leads in 5 of 7 scored categories. Both do social analytics.

- TwitterAPI.io MCP: D 49.3, rank #1101 of 1510 · https://www.anchorterminal.com/tools/twitterapi-io-mcp.min.md
- Xpoz MCP: E 39.6, rank #1339 of 1510 · https://www.anchorterminal.com/tools/xpoz-mcp.min.md
- TwitterAPI.io MCP, good for Agents that need to read X posts, profiles and followers cheaply, where a third-party source is acceptable. Ahead on Reliability, 40 against 20; Agent ergonomics, 78 against 63; Payments & pricing, 40 against 30; Maintenance & community, 40 against 25; Transparency & trust, 41 against 29.
- Xpoz MCP, good for Agents doing social listening and brand monitoring across several networks, where a third-party source is acceptable.

| Category | TwitterAPI.io MCP | Xpoz MCP |
| --- | --- | --- |
| Reliability (16%) | 40 | 20 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 62 | 64 |
| Agent ergonomics (13%) | 78 | 63 |
| Security & auth (14%) | 37 | 37 |
| Payments & pricing (10%) | 40 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 40 | 25 |
| Transparency & trust (7%) | 41 | 29 |

| Fact (where they differ) | TwitterAPI.io MCP | Xpoz MCP |
| --- | --- | --- |
| Vendor | Prism Digital, LLC | XPOZ |
| Hosted endpoint | `https://mcp.twitterapi.io/mcp` | `https://mcp.xpoz.ai/mcp` |
| Auth | OAuth or key | API key |
| Pricing | pay-per-use | Freemium |
| Tools exposed | 12 | 52 |
| llms.txt | yes | no |
| MCP registry | `io.twitterapi/mcp-server` | `ai.xpoz/social-insights` |
| Privacy policy last updated | not read yet | no document linked |

Why the edge:
- Reliability, TwitterAPI.io MCP +20: 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.); Xpoz MCP 20 (No status page found (0). No history (5). Credit allowances, no rate limits found (5 of 15). No retry guidance (0). No SLA (0). Not labelled beta (10). 0 + 5 + 5 + 0 + 0 + 10 = 20.)
- Agent ergonomics, TwitterAPI.io MCP +15: 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.); Xpoz MCP 63 (52 tools totalling about 238 KB (5). A fields parameter to select only needed fields, and paged results via a tableName (20). No documented errors (3 of 20). All annotated, 49 read-only (20). SDKs and a CLI (15). 5 + 20 + 3 + 20 + 15 = 63.)
- Maintenance & community, TwitterAPI.io MCP +15: 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.); Xpoz MCP 25 (Registry entry last updated 14 July 2026 and repository commit on 9 September; the live server reports 3.0.0 (10). No dated releases in 90 days (0). Issues not read (0). Official registry entry ai.xpoz/social-insights (15). Docker packaging only (0). 10 + 0 + 0 + 15 + 0 = 25. 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.)
- Transparency & trust, TwitterAPI.io MCP +12: 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.); Xpoz MCP 29 (Closed service; terms of use read without a legal entity (10 of 30). Data handling not read (5 of 30). No deprecation policy (0). Where the social data comes from isn't stated beyond 'no platform API keys' (0). 10 + 5 + 0 + 0 = 15.)
- Payments & pricing, TwitterAPI.io MCP +10: 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.); Xpoz MCP 30 (No machine payment protocol (0). Plan prices public (10). Free 500 credits (20). A person signs in for a key (0). 0 + 10 + 20 + 0 = 30.)