SocialCannon vs Xpoz MCP

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.

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.

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.

Xpoz MCP 37

One API key (20 of 30). 49 of 52 tools read-only (15 of 20). Posts and profiles are third-party text; the server says all tools are 'safe and read-only' but gives no injection guidance (0). No audit log (0). No security programme found (2 of 20). 20 + 15 + 0 + 0 + 2 = 37.

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.

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.

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.

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.

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.

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.