# Countly vs Userpilot (slim)

> Userpilot scores 64.4 (B) to Countly's 38.8 (E) for analytics queries. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/countly-vs-userpilot.md (~4,050 tokens) · this version ~2,130 tokens · JSON https://www.anchorterminal.com/compare/countly-vs-userpilot.json · canonical https://www.anchorterminal.com/compare/countly-vs-userpilot
- 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)

Userpilot scores 64.4 (B) on agent readiness against Countly's 38.8 (E), and leads in 2 of 7 scored categories. Countly leads on agent ergonomics and transparency & trust. Both do analytics queries.

- Countly: E 38.8, rank #1332 of 1486 · https://www.anchorterminal.com/tools/countly.min.md
- Userpilot: B 64.4, rank #471 of 1486 · https://www.anchorterminal.com/tools/userpilot.min.md
- Countly, good for An agent whose owner runs Countly on its own infrastructure or a dedicated Flex server and wants analytics, crash and remote-config data through MCP with per-category permissions. Ahead on Agent ergonomics, 66 against 60; Transparency & trust, 72 against 59. Also Runs on your own machine; Open source.
- Userpilot, good for SaaS teams already using Userpilot for onboarding who want an agent to answer analytics questions and draft segments and surveys. Ahead on Reliability, 82 against 23; Payments & pricing, 30 against 17. Also Free to start without a card; No incidents deducted, where Countly loses 15 points for them.

| Category | Countly | Userpilot |
| --- | --- | --- |
| Reliability (16%) | 23 | 82 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 75 | 71 |
| Agent ergonomics (13%) | 66 | 60 |
| Security & auth (14%) | 62 | 62 |
| Payments & pricing (10%) | 17 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 80 | 79 |
| Transparency & trust (7%) | 72 | 59 |

| Fact (where they differ) | Countly | Userpilot |
| --- | --- | --- |
| Vendor | Countly Ltd | Userpilot, Inc. |
| Hosted endpoint | `https://mcp.count.ly/mcp` | `https://mcp.userpilot.io/mcp` |
| Transports | HTTP, stdio, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Licence | Countly Lite is AGPL-3.0 with added branding terms under Section 7. Enterprise plugins are proprietary. Flex is a hosted service under Countly's terms. The MCP server is MIT | none |
| Tools exposed | 209 | none |
| Read-only variant documented | yes | no |
| MCP registry | not listed | `io.userpilot/mcp` |
| Last release | 2026-10-27 | 2026-10-11 |
| Terms last updated | not read yet | 2024-04-23 |
| Privacy policy last updated | not read yet | 2025-03-11 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | yes |
| Arbitration or class-action waiver | not read yet | yes |
| Popularity | 28k npm/wk | 236k npm/wk |

Why the edge:
- Reliability, Userpilot +59: Countly 23 (Graded on the hosted lines, for a Countly Flex server reached through its HTTP API and the official MCP server. No status page was found on countly.com, the Flex page, the docs or the legal pages, and status.countly.com did not resolve on 4 November (0). With no page there is no readable incident history (5). The MCP server's HTTP endpoint is limited to 120 requests a minute per IP, but the Countly server's own `api_rate_limit_requests` setting ships at 0 (off), and the Flex terms of 20 October 2026 reserve usage limits without numbers (8 of 15, the earlier partial kept). No 429 or retry guidance and no idempotency keys were found in the API reference source (0). The pricing page lists an SLA as optional on Flex and included in Enterprise, with no SLA document published, which this run scores 0 (0). The API and MCP server 1.7.0 are generally available (10).); Userpilot 82 (Graded on the hosted service with the hosted lines. Better Stack status page at status.userpilot.io with components for ingestion in three regions, the SDKs, the web application APIs and the website (20). From August to November 2026 the page shows only scheduled maintenance windows of two to four hours, with no incidents; the MCP server isn't a component (30). 600 requests a minute per token for the real-time APIs, but no numbers for MCP or export (12 of 15). 429 documented with exponential backoff guidance; no Retry-After or idempotency guidance (10 of 15). The SLA is a custom Enterprise contract term, not published (0). The MCP server is 1.0.0 in the registry with no beta label (10). 20+30+12+10+0+10 = 82.)
- Payments & pricing, Userpilot +13: Countly 17 (No x402, MPP or L402 (0). The pricing page gives only a starting price for Flex, $175 a month, priced on monthly active users and data points, with tier prices shown during signup and Enterprise on custom pricing (7 of 20, the earlier partial kept). The 14-day Flex trial needs a credit card, per the Flex page. Countly Lite is free to self-host with no card, without funnels, retention, cohorts or Drill, so half credit (10). A person signs up in a browser, creates a server and makes a token in the dashboard (0).); Userpilot 30 (No x402, MPP or L402 (0). Plan prices are public ($299 and from $849 a month), with no per-unit prices (10). 14-day free trial with no card required (20). Signup and OAuth approval happen in a browser (0). 0+10+20+0 = 30.)
- Transparency & trust, Countly +13: Countly 72 (Countly Lite is AGPL-3.0 with added branding terms under Section 7, the MCP server is MIT, and the Enterprise plugins that hold funnels, retention, cohorts and Drill are closed (20 of 30). Flex now has its own terms, privacy policy, DPA and sub-processor list, all dated 20 October 2026. The Flex privacy policy excludes data customers process and gives no retention periods, and the DPA covers that data (20). The MCP changelog deprecated auth tokens in URL parameters on 23 April 2026 (1.3.0), and the server warns on their use, with no notice period (15, the settled value for dated notices without a period). The Flex sub-processor list names locations, with 30 days' notice of changes in the DPA, and Flex customers choose a Google Cloud region. A Connected Services and Telemetry notice (20 October 2026) says server reports to stats.count.ly are on by default and which settings turn them off, and MCP usage reporting is disclosed with an opt-out (18).); Userpilot 59 (A closed service with terms dated 23 April 2024 (15 of 30). The privacy policy of 11 March 2025 names a DPO and two sub-processors (AWS and Cloudflare), while the security page names AWS, Google Cloud and Stripe. The DPA is on request and no customer-data retention period is stated (14 of 30). No deprecation policy or dated API notices found (3 of 20). Sub-processors are named with addresses but not data locations, though an EU ingestion endpoint exists (10 of 20). 15+14+3+10 = 42.)
- Agent ergonomics, Countly +6: Countly 66 (The MCP README counts 209 tools in 43 categories, far past 30 (5). Add back 8 because the server hides tools the edition, enabled plugins or user's permissions cannot run, and `COUNTLY_TOOLS_*` settings switch categories off (13). List endpoints take `iDisplayStart` and `iDisplayLength`, and MCP list tools take `skip`, `limit` and `search` (15). API errors are `{"result": "message"}` strings with HTTP status codes and no error codes. The MCP server returns failures as `isError` results that name the missing plugin or permission (12). MCP tools carry readOnlyHint, destructiveHint and idempotentHint since 1.7.0. No idempotency keys on API writes (14). MCP tools accept `app_name` in place of `app_id` and set defaults. The SDKs cover data collection, not the read API (12).); Userpilot 60 (The tool count isn't published; the docs say the assistant can search hundreds of extra read-only operations on demand, which reads as dynamic loading. Without the list we give the middle band (15 of 25). Export jobs filter by date range, users, events and segments, and job lists paginate (14 of 20). A documented error reference (13 of 20). No deletes or admin through MCP by design; annotations weren't readable and no idempotency keys were found (10 of 20). The HTTP APIs have no official server-side SDK; client SDKs for web and six mobile frameworks (8 of 15). 15+14+13+10+8 = 60.)