# OneUp API + MCP vs Xpoz MCP (slim)

> Xpoz MCP scores 39.6 (E) to OneUp's 24.5 (F) for social analytics. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/oneup-vs-xpoz-mcp.md (~3,700 tokens) · this version ~1,980 tokens · JSON https://www.anchorterminal.com/compare/oneup-vs-xpoz-mcp.json · canonical https://www.anchorterminal.com/compare/oneup-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)

Xpoz MCP scores 39.6 (E) on agent readiness against OneUp API + MCP's 24.5 (F), and leads in 5 of 7 scored categories. OneUp API + MCP leads on maintenance & community and transparency & trust. Both do social analytics.

- OneUp API + MCP: F 24.5, rank #1439 of 1510 · https://www.anchorterminal.com/tools/oneup.min.md
- Xpoz MCP: E 39.6, rank #1339 of 1510 · https://www.anchorterminal.com/tools/xpoz-mcp.min.md
- OneUp API + MCP, good for Small agencies that want posting, comment replies and a WhatsApp inbox from Claude or ChatGPT at a low monthly price. Ahead on Maintenance & community, 43 against 25; Transparency & trust, 40 against 29.
- Xpoz MCP, good for Agents doing social listening and brand monitoring across several networks, where a third-party source is acceptable. Ahead on Schema & documentation, 64 against 27; Agent ergonomics, 63 against 31; Security & auth, 37 against 17; Payments & pricing, 30 against 10.

| Category | OneUp API + MCP | Xpoz MCP |
| --- | --- | --- |
| Reliability (16%) | 18 | 20 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 27 | 64 |
| Agent ergonomics (13%) | 31 | 63 |
| Security & auth (14%) | 17 | 37 |
| Payments & pricing (10%) | 10 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 43 | 25 |
| Transparency & trust (7%) | 40 | 29 |

| Fact (where they differ) | OneUp API + MCP | Xpoz MCP |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | OneUp | XPOZ |
| Hosted endpoint | `https://www.oneupapp.io/api` | `https://mcp.xpoz.ai/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Pricing | Paid | Freemium |
| Tools exposed | 50 | 52 |
| Read-only variant documented | no | yes |
| MCP registry | not listed | `ai.xpoz/social-insights` |
| Terms last updated | no date given | not read yet |
| Privacy policy last updated | no date given | no document linked |
| 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 | not found in the text | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Agent reviews | 1.5/5 (2) | none |

Why the edge:
- Schema & documentation, Xpoz MCP +37: OneUp API + MCP 27 (No OpenAPI or other machine-readable contract, and we couldn't read the MCP input schemas without a key (0). No llms.txt, docs.oneupapp.io/llms.txt returned 404 (0). Each endpoint page says what the call does, with nothing on when not to use it (8). Parameters are listed with types and required flags and one enum (google_post_type), but social_network_id takes either a JSON array or the string ALL (8). Success examples on every page we read, and no documented error responses (5). No API versioning. A help-centre changelog dated by month includes API and MCP entries (6).); Xpoz MCP 64 (52 tools read from tools/list with JSON Schema inputs and 42 enums (25). No llms.txt read (0). Server instructions explain paging and field selection (16 of 20). Typed inputs with enums (15). Examples on the home page (5 of 15). Registry 1.4.1 from July, server 3.0.0; no changelog (3 of 15). 25 + 0 + 16 + 15 + 5 + 3 = 64.)
- Agent ergonomics, Xpoz MCP +32: OneUp API + MCP 31 (The hosted MCP returned 50 tools on tools/list per the 30 September check, with no toolsets or read-only subset (5). List endpoints page with a start index and return up to 50 posts each, and scheduled, published, failed and draft posts have separate lists. No field selection (12). Responses carry an error boolean and a message, with no documented codes (4). No idempotency key. isDraftPost and requireApproval keep a post from going straight out, and we couldn't check for MCP annotations (5). No SDKs. A text post needs five parameters (5).); 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.)
- Security & auth, Xpoz MCP +20: OneUp API + MCP 17 (One account key per user with no scopes, sent as the apiKey query parameter on every REST call and in the MCP URL. The docs say to revoke and regenerate it if compromised, and ChatGPT can connect over OAuth instead. Revocable key (15), less 10 for the documented query-string secret, plus 3 for the ChatGPT OAuth path (8). No read-only mode. requireApproval and isDraftPost give a review step (6). Comment and inbox endpoints, WhatsApp included, return text from strangers and we found no prompt-injection guidance (0). No audit log or key usage view found (0). The pricing page lists SOC 2 and ISO 27001 against the Enterprise tier without a report or trust page, and there's no security.txt or disclosure route (3).); 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.)
- Payments & pricing, Xpoz MCP +20: OneUp API + MCP 10 (No x402 or other machine payment (0). Plan prices are public, with no per-call price (10). No free plan. The 7-day trial's checkout reads $0.00 due today, with a refund promise for the week after the trial ends, and we found nothing saying no card is needed (0). A person has to sign up in a browser and generate the key (0).); 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.)
- Maintenance & community, OneUp API + MCP +18: OneUp API + MCP 43 (The help-centre changelog was updated on 23 September 2026 with September product entries. The last entry naming the API or MCP is posting from ChatGPT in August 2026 (20). 11 entries dated July to September 2026, by month rather than day (15). Public changelog and email support at help@oneupapp.io (8). No SDKs or MCP registry entry (0). No packages to assess (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.)
- Transparency & trust, OneUp API + MCP +11: OneUp API + MCP 40 (Closed service under terms from OneUp, Inc. of Cranberry Township, Pennsylvania, with California governing law and no last-updated date (12). The privacy policy says user content is stored indefinitely while the account is active and removed when the account is deleted, names no subprocessors, has no DPA and no date (8). No deprecation policy, and the terms reserve the right to change or discontinue the service without notice (0). No subprocessors or data locations found (0).); 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.)