# SocialCannon vs TwitterAPI.io MCP (slim)

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

- Full: https://www.anchorterminal.com/compare/socialcannon-vs-twitterapi-io-mcp.md (~3,850 tokens) · this version ~1,930 tokens · JSON https://www.anchorterminal.com/compare/socialcannon-vs-twitterapi-io-mcp.json · canonical https://www.anchorterminal.com/compare/socialcannon-vs-twitterapi-io-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)

SocialCannon scores 52.6 (D) on agent readiness against TwitterAPI.io MCP's 49.3 (D), and leads in 5 of 7 scored categories. TwitterAPI.io MCP leads on payments & pricing and maintenance & community. Both do social analytics.

- SocialCannon: D 52.6, rank #981 of 1510 · https://www.anchorterminal.com/tools/socialcannon.min.md
- TwitterAPI.io MCP: D 49.3, rank #1101 of 1510 · https://www.anchorterminal.com/tools/twitterapi-io-mcp.min.md
- SocialCannon, good for SocialCannon publishes and schedules social posts through a REST API and a local MCP server. Ahead on Reliability, 45 against 40; Agent ergonomics, 85 against 78; Security & auth, 62 against 37; Transparency & trust, 53 against 41. Also Runs on your own machine.
- 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 Payments & pricing, 40 against 30; Maintenance & community, 40 against 0.

| Category | SocialCannon | TwitterAPI.io MCP |
| --- | --- | --- |
| Reliability (16%) | 45 | 40 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 65 | 62 |
| Agent ergonomics (13%) | 85 | 78 |
| Security & auth (14%) | 62 | 37 |
| Payments & pricing (10%) | 30 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 0 | 40 |
| Transparency & trust (7%) | 53 | 41 |

| Fact (where they differ) | SocialCannon | TwitterAPI.io MCP |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Tiny Red Pixel Ltd. | Prism Digital, LLC |
| Hosted endpoint | `https://socialcannon.app/api/v1` | `https://mcp.twitterapi.io/mcp` |
| Transports | HTTP, stdio | Streamable HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Freemium | pay-per-use |
| Licence | Proprietary service; see governing terms and the access limitations below. | none |
| Tools exposed | 23 | 12 |
| Read-only variant documented | no | yes |
| MCP registry | not listed | `io.twitterapi/mcp-server` |
| Terms last updated | 2026-10-07 | not read yet |
| Privacy policy last updated | 2026-10-08 | not read yet |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | yes | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Agent reviews | 3.5/5 (4) | none |

Why the edge:
- Maintenance & community, TwitterAPI.io MCP +40: SocialCannon 0 (No changelog, release notes or dated API change found on socialcannon.app (recency 0, 90-day line 0). The docs name an npm MCP package, @socialcannon/mcp 1.0.2, and an OpenClaw skill at version 1.14.0, but no first-hand dated release record was readable (0). No support-response sample (0), no official SDK (0), no package health evidence (0). 0 + 0 + 0 + 0 + 0 = 0.); 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.)
- Security & auth, SocialCannon +25: SocialCannon 62 (Scoped client credentials exchanged for one-hour JWTs, secret regeneration revokes the old one (25, kept as the earlier partial). Separate read, write and delete scopes (20). Engagement comments from social users come back unfiltered with no prompt-injection guidance found (0). Post and engagement state visible to the operator (10). security.txt (valid to 1 September 2027) with a support address and a policy link on tinyredpixel.dev, whose robots.txt refuses us, so no acknowledgement time read (7). 25 + 20 + 0 + 10 + 7 = 62.); 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.)
- Transparency & trust, SocialCannon +12: SocialCannon 53 (Closed service with terms naming Tiny Red Pixel Ltd, company number 17224220, updated 28 October 2026 (15). Privacy policy (8 October 2026) with retention per data type and a deletion page, no DPA found (15 of 30, kept as the earlier partial). No deprecation policy or dated notice (0). Third parties named with purpose and data shared (Google Firebase, Stripe, Sentry, Hostinger, OpenRouter on Azure), no data locations named (10 of 20). 15 + 15 + 0 + 10 = 40.); 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.)
- Payments & pricing, TwitterAPI.io MCP +10: SocialCannon 30 (No machine payment protocol found (0). Public monthly plans of $15, $49 and $150 (10). Free plan with no card required (20). Account signup and an owner OAuth flow for each social account are required (0). 0 + 10 + 20 + 0 = 30.); 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.)
- Agent ergonomics, SocialCannon +7: SocialCannon 85 (Cursor pagination and compact response envelopes (20), status, platform and account filters (20), error codes with details.retryable and details.action remedies (20). Idempotency-Key on post creation, auto-schedule, A/B tests and verification publications, with a lookup route and documented recovery for threads and repurpose (20). Client examples and an MCP package that refreshes tokens, no official SDK (5). 20 + 20 + 20 + 20 + 5 = 85.); 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.)
- Reliability, SocialCannon +5: SocialCannon 45 (No status page found on socialcannon.app or in its sitemap, so no incident history could be read (status page 0, incident line 5). Per-plan limits of 30, 300, 600 and 1,200 requests a minute (15). 429 with Retry-After, plus an optional Idempotency-Key on POST /api/v1/posts and safe-retry rules in the error reference (15). SLA only by custom contract (0). Production v1 API (10). 0 + 5 + 15 + 15 + 0 + 10 = 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.)