{
  "data": {
    "a": {
      "slug": "countly",
      "name": "Countly",
      "vendor": "Countly Ltd",
      "vendorUrl": "https://countly.com",
      "kind": "http-api",
      "category": "product-analytics",
      "summary": "Countly is a product analytics platform sold as a managed private-cloud server (Flex), a self-hosted Enterprise edition and the open-source Countly Lite. Agents reach a Countly server through its HTTP API or the official `countly-mcp-server`.",
      "url": "https://www.anchorterminal.com/tools/countly",
      "markdownUrl": "https://www.anchorterminal.com/tools/countly.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/countly.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/countly.json",
      "repo": "https://github.com/Countly/countly-server",
      "license": "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",
      "transports": [
        "http",
        "stdio",
        "streamable-http"
      ],
      "remoteUrl": "https://mcp.count.ly/mcp",
      "packages": [
        {
          "registry": "npm",
          "name": "countly-mcp-server"
        },
        {
          "registry": "npm",
          "name": "countly-sdk-web"
        },
        {
          "registry": "npm",
          "name": "countly-sdk-nodejs"
        }
      ],
      "auth": "api-key",
      "authNotes": "Self-serve once a server exists. A dashboard user copies an `api_key`, which has that user's full read and write access, or creates an auth token in the Token Manager or with `/i/token/create`, limited by app, endpoint pattern and lifetime. Tokens go in the `countly-token` header or the `auth_token` query parameter. The MCP server takes `COUNTLY_SERVER_URL` and `COUNTLY_AUTH_TOKEN`, or `X-Countly-Server-Url` and `X-Countly-Auth-Token` headers over HTTP. SDKs send the write-only `app_key`.",
      "pricing": "paid",
      "pricingNotes": "Flex starts at $175 a month, billed by tier on monthly active users and data points, with a 14-day trial that needs a credit card. Tier prices appear during signup. Funnels, retention and flows sit in the Intelligence add-on. Enterprise is on quotation. Countly Lite is free to self-host. API and MCP calls are not billed (https://countly.com/pricing, checked 2026-10-08).",
      "priceSummary": "$175 / mo",
      "where": "both",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the API reference, the MCP server README or the pricing page (checked 2026-10-08).",
        "endpoints": []
      },
      "toolCount": 209,
      "popularity": {
        "githubStars": null,
        "npmWeekly": 27579,
        "pypiWeekly": null,
        "asOf": "2026-10-08"
      },
      "docsUrl": "https://api.count.ly/",
      "llmsTxt": "https://countly.com/llms.txt",
      "capabilities": [
        "analytics.query",
        "analytics.events",
        "analytics.funnels",
        "analytics.experiments",
        "analytics.flags",
        "observability.errors"
      ],
      "tags": [
        "official",
        "hosted",
        "self-hosted",
        "open-source",
        "mcp",
        "api-key",
        "llms-txt",
        "paid",
        "trial",
        "typescript"
      ],
      "lastRelease": "2026-10-07",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 54.8,
        "grade": "C",
        "agentReady": false,
        "rank": 607,
        "ranked": true,
        "rankOf": 842,
        "categoryRank": 9,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 66,
          "maintenance": 80,
          "payments": 17,
          "reliability": 28,
          "schema": 75,
          "security": 63,
          "transparency": 70
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-08"
        },
        "negative": 0,
        "verdict": "Countly suits an agent working against a server its owner already runs. The official MCP server filters its 209 tools by edition, plugin and permission and has per-category read-only settings. No status page, OpenAPI document or published API rate limit was found, and the Flex trial needs a credit card.",
        "bestFor": "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.",
        "strengths": [
          "Official MIT MCP server, `countly-mcp-server` 1.7.0 of 7 October 2026, with read-only, destructive and idempotent annotations on its tools",
          "`COUNTLY_TOOLS_ALL=R` makes every MCP tool read-only, and per-category settings take None, R, CR, CRU or CRUD",
          "Auth tokens can be limited to named apps and endpoint patterns, carry a lifetime in seconds and are revocable",
          "API reference at api.count.ly is versioned (24.05, 25.03, 26.01) with parameters, examples and error responses per endpoint",
          "Sub-processor list with locations and a public DPA, both updated 25 September 2026, with 30 days' notice of sub-processor changes"
        ],
        "weaknesses": [
          "No public status page or incident history was found for Flex servers or for mcp.count.ly",
          "No OpenAPI document was found, and the server's API rate limit is a setting that ships switched off with no published value for Flex",
          "The API accepts `api_key` and `auth_token` in the URL query string, and the `api_key` has its user's full read and write access",
          "Flex starts at $175 a month, its 14-day trial needs a credit card, and tier prices appear only during signup",
          "Funnels, retention, flows, cohorts and Drill need Enterprise or a paid Flex capability, and are absent from Countly Lite",
          "The MCP server reports usage to stats.count.ly by default until `ENABLE_ANALYTICS=false` is set"
        ],
        "agentNotes": [
          "Create a dedicated token in the Token Manager, limited to the apps and endpoints the task needs, and send it in the `countly-token` header, not the URL",
          "Set `COUNTLY_TOOLS_ALL=R` unless the task needs writes. The token's own permissions still apply and the stricter of the two wins",
          "Call `apps_list` first. Most tools need `app_id` or an exact `app_name`",
          "Check `get_version` for the detected edition before planning funnel, retention or cohort queries, which need Enterprise plugins",
          "Set `ENABLE_ANALYTICS=false` to stop usage reports to stats.count.ly, and prefer the stdio server to mcp.count.ly so the server URL and token stay local"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "C",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 54.8
          }
        ],
        "editorialScores": {
          "ergonomics": 66,
          "maintenance": 80,
          "payments": 17,
          "reliability": 28,
          "schema": 75,
          "security": 63,
          "transparency": 64
        },
        "provenanceScore": 76
      },
      "connect": {
        "install": "npx -y countly-mcp-server",
        "http": "curl -H \"countly-token: YOUR_TOKEN\" \"https://your-countly-url.com/o?app_id=APP_ID\u0026method=funneldata\u0026funnels=[%22FUNNEL_ID%22]\"",
        "claudeCode": "claude mcp add countly -e COUNTLY_SERVER_URL=https://your-countly-url.com -e COUNTLY_AUTH_TOKEN=YOUR_TOKEN -- npx -y --prefer-online countly-mcp-server@latest",
        "config": {
          "mcpServers": {
            "countly": {
              "args": [
                "-y",
                "--prefer-online",
                "countly-mcp-server@latest"
              ],
              "command": "npx",
              "env": {
                "COUNTLY_AUTH_TOKEN": "YOUR_TOKEN",
                "COUNTLY_SERVER_URL": "https://your-countly-url.com"
              }
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/analytics.query",
        "tool": "https://letme.dev/countly"
      },
      "area": "business",
      "unitPrices": [
        {
          "item": "Flex, lowest tier",
          "unit": "month",
          "usd": 175,
          "note": "starting price, by monthly active users and data points, add-ons extra"
        }
      ],
      "provenance": {
        "legalEntity": "Countly Ltd",
        "domain": "countly.com",
        "domainRegistered": "2011-09-05",
        "endpointOnVendorDomain": true,
        "terms": "https://countly.com/legal/terms-of-service",
        "privacy": "https://countly.com/legal/privacy-policy",
        "statusPage": "",
        "changelog": "https://github.com/Countly/countly-server/blob/master/CHANGELOG.md",
        "securityTxt": "none",
        "checked": "2026-10-08",
        "notes": [
          "The terms (last updated 25 September 2026) name Countly Ltd, incorporated in England and Wales with registered number 8568329, registered at 1 Bow Churchyard, London EC4M 9DQ. They cover Flex through supplemental terms and exclude Enterprise subscriptions, which have written agreements.",
          "The privacy policy (last updated 25 September 2026) covers Countly's websites, services and accounts and says it does not apply to data customers process with the Services. The DPA at countly.com/legal/dpa covers that data.",
          "The hosted MCP server answers at mcp.count.ly and the API reference at api.count.ly, a second domain of the vendor's. Each customer's API answers on that customer's own server address.",
          "countly.com/.well-known/security.txt returns 404. SECURITY.md in the repositories gives a disclosure address at count.ly.",
          "No status page was found. status.countly.com did not resolve.",
          "RDAP for countly.com gives a registration date of 2011-09-05."
        ],
        "score": 76
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/countly.json",
      "live": {
        "slug": "countly",
        "probe": {
          "target": "https://mcp.count.ly/mcp",
          "method": "get",
          "lastAt": "2026-10-09T10:42:40.400466188Z",
          "lastOk": false,
          "lastStatus": 500,
          "lastMs": 389,
          "lastNote": "server error",
          "authRequired": false,
          "uptime24h": 0,
          "uptime30d": 0,
          "p50ms24h": 0,
          "p95ms24h": 0,
          "samples24h": 33,
          "samples30d": 33,
          "days": [
            {
              "date": "2026-10-09",
              "probes": 33,
              "ok": 0
            }
          ],
          "outages": [
            {
              "start": "2026-10-09T07:40:23.474688008Z",
              "end": "0001-01-01T00:00:00Z",
              "note": "HTTP 500 server error"
            }
          ]
        },
        "updatedAt": "2026-10-09T10:42:40.400466188Z"
      }
    },
    "answer": "Countly scores 54.8 (C) on agent readiness against Woopra's 44.4 (E), and leads in 5 of 7 scored categories. Woopra leads on reliability and payments \u0026 pricing.",
    "b": {
      "slug": "woopra",
      "name": "Woopra",
      "vendor": "Woopra, Inc.",
      "vendorUrl": "https://www.woopra.com",
      "kind": "http-api",
      "category": "product-analytics",
      "summary": "Woopra is a hosted customer journey and product analytics service from Woopra, Inc., an Appier affiliate. Its HTTP tracking API records events and visitor properties, and its REST API returns saved reports, profiles and raw session logs.",
      "url": "https://www.anchorterminal.com/tools/woopra",
      "markdownUrl": "https://www.anchorterminal.com/tools/woopra.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/woopra.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/woopra.json",
      "repo": "https://github.com/Woopra/js-client-tracker",
      "license": "Proprietary service under Woopra's terms of service. The browser tracker and the SDKs on GitHub are MIT, and the Node package is ISC",
      "transports": [
        "http"
      ],
      "remoteUrl": "https://www.woopra.com/rest/3.10",
      "packages": [
        {
          "registry": "npm",
          "name": "woopra"
        },
        {
          "registry": "npm",
          "name": "@woopra/browser-tracker"
        }
      ],
      "auth": "mixed",
      "authNotes": "Self-serve. REST calls use HTTP Basic with an App ID and Secret Key that each user generates on the Access Keys tab of the members area. Tracking calls need only the project name unless the owner enables Secure Tracking, which adds a generated ID and secret sent by HTTP Basic. No OAuth, scopes or partner approval were found in the docs.",
      "pricing": "paid",
      "pricingNotes": "Pro starts at $999 a month for 5 million events, with a 30-day trial that an agent's owner can start without a contract. Overage fees apply past the event quota, at rates the pricing page does not state. Enterprise is quoted. Whether the trial signup asks for a card was not established (https://www.woopra.com/pricing, checked 2026-10-09).",
      "priceSummary": "$999 / mo",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the developer docs or on the pricing page (checked 2026-10-09).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": 415,
        "pypiWeekly": null,
        "asOf": "2026-10-09"
      },
      "docsUrl": "https://docs.woopra.com",
      "llmsTxt": "https://docs.woopra.com/llms.txt",
      "capabilities": [
        "analytics.query",
        "analytics.events",
        "analytics.funnels"
      ],
      "tags": [
        "hosted",
        "closed-source",
        "llms-txt",
        "basic-auth",
        "no-oauth",
        "free-trial",
        "status-page",
        "rate-limits",
        "export",
        "sales-led"
      ],
      "lastRelease": "2026-03-16",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 44.4,
        "grade": "E",
        "agentReady": false,
        "rank": 779,
        "ranked": true,
        "rankOf": 842,
        "categoryRank": 12,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 45,
          "maintenance": 9,
          "payments": 30,
          "reliability": 80,
          "schema": 45,
          "security": 22,
          "transparency": 61
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-09"
        },
        "negative": 0,
        "verdict": "Woopra's REST API returns saved Trends, Journeys, Retention and Attribution reports, profiles and raw session logs, with published limits of 300 calls a minute and 3,000 a day per project. A report must first be built in the web app, the tracking endpoints accept events without a secret by default, and no changelog or SLA was found.",
        "bestFor": "An agent that reads a company's existing Woopra reports, looks up or edits customer profiles, or exports raw sessions on a schedule.",
        "strengths": [
          "Rate limits are published per project at 300 calls a minute, 600 an hour and 3,000 a day, and limited calls return 429",
          "Report endpoints take `limit`, `offset`, a `snapshot` ID for consistent paging past 1,000 records, and `timeframe_from` and `timeframe_to` overrides",
          "status.woopra.com (Statuspage) lists no incidents for August, September or October 2026 across Data Processing, Data Collection and the front-end application",
          "`/logs/export` returns raw sessions as line-separated JSON, and `/logs/import` loads them in bulk and returns a batch ID to poll",
          "The terms of service (10 December 2025) name nine sub-processors with addresses and countries, and say the customer owns the tracking data"
        ],
        "weaknesses": [
          "Report endpoints run a report saved in the web app by `report_id`. No endpoint to define a query, funnel or segment was found in the reference",
          "`/track/ce` and `/track/identify` accept data with only the project name unless the owner turns on Secure Tracking",
          "No API changelog, deprecation policy or SLA was found. The terms promise commercially reasonable efforts on availability",
          "Server SDKs are old. The Node, Python, Java and Rails repositories were last committed to in 2017, and npm `woopra` is 1.0.2",
          "The terms of service forbid using any robot, spider, scraper or other automated means to access the Site, a term defined to include the Services",
          "Most REST operations document no response schema, and the `/profiles` page repeats the `/trends` description"
        ],
        "agentNotes": [
          "Ask the owner to build and save each report in the web app first, then pass the last path segment of its URL as `report_id`",
          "Authenticate REST calls with HTTP Basic, using the App ID and Secret Key from the Access Keys tab, against `https://www.woopra.com/rest/3.10/`",
          "Stay under 300 calls a minute, 600 an hour and 3,000 a day per project. A 429 carries no documented retry interval, so back off on your own schedule",
          "Reuse the `snapshot` ID from the first response when paging with `offset`, or pages past 1,000 records may not agree",
          "Send `cookie` or a `cv_` identifier such as `cv_email` on every track call. Without one the event lands on a random profile that can't be identified later",
          "When reading `/logs/export`, delete the profile named in each `type: \"delete\"` line. The following lines log its data again under `new_id`"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "E",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 44.4
          }
        ],
        "editorialScores": {
          "ergonomics": 45,
          "maintenance": 9,
          "payments": 30,
          "reliability": 80,
          "schema": 45,
          "security": 22,
          "transparency": 45
        },
        "provenanceScore": 77
      },
      "connect": {
        "http": "curl \\\n--user \u003cApp Id\u003e:\u003cSecret Key\u003e \\\n\"https://www.woopra.com/rest/3.10/trends?project=mybusiness.com\u0026start_day=2017-4-12\u0026end_day=2017-5-19\u0026report_id=83mYcoe6jX\""
      },
      "letme": {
        "capability": "https://letme.dev/analytics.query",
        "tool": "https://letme.dev/woopra"
      },
      "area": "business",
      "unitPrices": [
        {
          "item": "Pro, 5 million events a month",
          "unit": "month",
          "usd": 999,
          "note": "starting price, overage fees apply"
        }
      ],
      "provenance": {
        "legalEntity": "Woopra, Inc.",
        "domain": "woopra.com",
        "domainRegistered": "2007-02-23",
        "endpointOnVendorDomain": true,
        "terms": "https://www.woopra.com/tos",
        "privacy": "https://www.woopra.com/privacy",
        "statusPage": "https://status.woopra.com",
        "changelog": "",
        "securityTxt": "unknown",
        "checked": "2026-10-09",
        "notes": [
          "The terms of service (last updated 10 December 2025) are a contract with Woopra, Inc., its subsidiaries and affiliated companies including Appier, and cover the website and the subscription services in one document. They give 600 California St, Fl 11, San Francisco, CA 94108 as the legal address.",
          "The privacy policy (last updated 1 August 2025) covers customers and site visitors and says it does not apply to end-user data that Woopra processes for customers. It names Appier Netherlands B.V. as EU representative. No public DPA was found, and the GDPR page says a copy is sent on request.",
          "The REST and tracking endpoints answer under https://www.woopra.com/rest and https://www.woopra.com/track, on the vendor's own domain. robots.txt on that host disallows both paths, and we sent no request to either.",
          "www.woopra.com/.well-known/security.txt timed out twice with no bytes received, so its presence is unknown.",
          "status.woopra.com is an Atlassian Statuspage site. Its address was not linked from the pages we read and was tried directly.",
          "No changelog for the API was found. docs.woopra.com/changelog returns 404, and the browser tracker's CHANGELOG.md stops at v5.3.0 of 15 September 2021.",
          "RDAP for woopra.com gives a registration date of 2007-02-23 and Spaceship, Inc. as registrar."
        ],
        "score": 77
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/woopra.json",
      "live": {
        "slug": "woopra",
        "probe": {
          "target": "https://www.woopra.com/rest/3.10",
          "method": "get",
          "lastAt": "2026-10-09T10:43:02.137707325Z",
          "lastOk": false,
          "lastStatus": 500,
          "lastMs": 29,
          "lastNote": "server error",
          "authRequired": false,
          "uptime24h": 0,
          "uptime30d": 0,
          "p50ms24h": 0,
          "p95ms24h": 0,
          "samples24h": 33,
          "samples30d": 33,
          "days": [
            {
              "date": "2026-10-09",
              "probes": 33,
              "ok": 0
            }
          ],
          "outages": [
            {
              "start": "2026-10-09T07:40:43.906309049Z",
              "end": "0001-01-01T00:00:00Z",
              "note": "HTTP 500 server error"
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.woopra.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-10-09T10:42:09.985016293Z"
        },
        "updatedAt": "2026-10-09T10:43:02.137707325Z"
      }
    },
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Countly Ltd",
        "b": "Woopra, Inc.",
        "name": "Vendor"
      },
      {
        "a": "https://mcp.count.ly/mcp",
        "b": "https://www.woopra.com/rest/3.10",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP, stdio, Streamable HTTP",
        "b": "HTTP",
        "name": "Transports"
      },
      {
        "a": "API key",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Paid",
        "b": "Paid",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "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",
        "b": "Proprietary service under Woopra's terms of service. The browser tracker and the SDKs on GitHub are MIT, and the Node package is ISC",
        "name": "Licence"
      },
      {
        "a": "209",
        "b": "none",
        "name": "Tools exposed"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-10-07",
        "b": "2026-03-16",
        "name": "Last release"
      },
      {
        "a": "2026-09-25",
        "b": "2025-12-10",
        "name": "Terms last updated"
      },
      {
        "a": "2026-09-25",
        "b": "2025-08-01",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "yes",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not found in the text",
        "b": "yes",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "28k npm/wk",
        "b": "415 npm/wk",
        "name": "Popularity"
      }
    ],
    "faq": [
      {
        "answer": "Countly scores 54.8 (C) on agent readiness against Woopra's 44.4 (E), and leads in 5 of 7 scored categories. Woopra leads on reliability and payments \u0026 pricing.",
        "question": "Which is better for AI agents, Countly or Woopra?"
      },
      {
        "answer": "Countly needs an API key. Woopra takes an API key or an OAuth sign-in.",
        "question": "Do Countly and Woopra need an API key?"
      },
      {
        "answer": "Yes. Countly has a hosted endpoint at https://mcp.count.ly/mcp and Woopra at https://www.woopra.com/rest/3.10.",
        "question": "Can an agent call Countly and Woopra without installing anything?"
      },
      {
        "answer": "Countly is open source (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). No open-source release is listed for Woopra.",
        "question": "Are Countly and Woopra open source?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Schema \u0026 documentation, 75 against 45",
          "Agent ergonomics, 66 against 45",
          "Security \u0026 auth, 63 against 22",
          "Maintenance \u0026 community, 80 against 9",
          "Transparency \u0026 trust, 70 against 61"
        ],
        "also": [
          "Runs on your own machine",
          "Open source"
        ],
        "goodFor": "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.",
        "slug": "countly",
        "watchFor": "No public status page or incident history was found for Flex servers or for mcp.count.ly"
      },
      {
        "aheadOn": [
          "Reliability, 80 against 28",
          "Payments \u0026 pricing, 30 against 17"
        ],
        "also": null,
        "goodFor": "An agent that reads a company's existing Woopra reports, looks up or edits customer profiles, or exports raw sessions on a schedule.",
        "slug": "woopra",
        "watchFor": "Report endpoints run a report saved in the web app by `report_id`. No endpoint to define a query, funnel or segment was found in the reference"
      }
    ],
    "job": {
      "capability": "analytics.query",
      "name": "Analytics query"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/amplitude-vs-countly.json",
        "title": "Amplitude vs Countly",
        "url": "https://www.anchorterminal.com/compare/amplitude-vs-countly"
      },
      {
        "json": "https://www.anchorterminal.com/compare/amplitude-vs-woopra.json",
        "title": "Amplitude vs Woopra",
        "url": "https://www.anchorterminal.com/compare/amplitude-vs-woopra"
      },
      {
        "json": "https://www.anchorterminal.com/compare/countly-vs-fullstory.json",
        "title": "Countly vs Fullstory",
        "url": "https://www.anchorterminal.com/compare/countly-vs-fullstory"
      },
      {
        "json": "https://www.anchorterminal.com/compare/countly-vs-growthbook.json",
        "title": "Countly vs GrowthBook",
        "url": "https://www.anchorterminal.com/compare/countly-vs-growthbook"
      },
      {
        "json": "https://www.anchorterminal.com/compare/countly-vs-mixpanel.json",
        "title": "Countly vs Mixpanel",
        "url": "https://www.anchorterminal.com/compare/countly-vs-mixpanel"
      },
      {
        "json": "https://www.anchorterminal.com/compare/countly-vs-optimizely.json",
        "title": "Countly vs Optimizely Experimentation",
        "url": "https://www.anchorterminal.com/compare/countly-vs-optimizely"
      },
      {
        "json": "https://www.anchorterminal.com/compare/countly-vs-pendo.json",
        "title": "Countly vs Pendo",
        "url": "https://www.anchorterminal.com/compare/countly-vs-pendo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/countly-vs-posthog.json",
        "title": "Countly vs PostHog",
        "url": "https://www.anchorterminal.com/compare/countly-vs-posthog"
      },
      {
        "json": "https://www.anchorterminal.com/compare/countly-vs-statsig.json",
        "title": "Countly vs Statsig",
        "url": "https://www.anchorterminal.com/compare/countly-vs-statsig"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullstory-vs-woopra.json",
        "title": "Fullstory vs Woopra",
        "url": "https://www.anchorterminal.com/compare/fullstory-vs-woopra"
      },
      {
        "json": "https://www.anchorterminal.com/compare/growthbook-vs-woopra.json",
        "title": "GrowthBook vs Woopra",
        "url": "https://www.anchorterminal.com/compare/growthbook-vs-woopra"
      },
      {
        "json": "https://www.anchorterminal.com/compare/mixpanel-vs-woopra.json",
        "title": "Mixpanel vs Woopra",
        "url": "https://www.anchorterminal.com/compare/mixpanel-vs-woopra"
      },
      {
        "json": "https://www.anchorterminal.com/compare/optimizely-vs-woopra.json",
        "title": "Optimizely Experimentation vs Woopra",
        "url": "https://www.anchorterminal.com/compare/optimizely-vs-woopra"
      },
      {
        "json": "https://www.anchorterminal.com/compare/pendo-vs-woopra.json",
        "title": "Pendo vs Woopra",
        "url": "https://www.anchorterminal.com/compare/pendo-vs-woopra"
      },
      {
        "json": "https://www.anchorterminal.com/compare/posthog-vs-woopra.json",
        "title": "PostHog vs Woopra",
        "url": "https://www.anchorterminal.com/compare/posthog-vs-woopra"
      },
      {
        "json": "https://www.anchorterminal.com/compare/statsig-vs-woopra.json",
        "title": "Statsig vs Woopra",
        "url": "https://www.anchorterminal.com/compare/statsig-vs-woopra"
      },
      {
        "json": "https://www.anchorterminal.com/compare/countly-vs-heap.json",
        "title": "Countly vs Heap",
        "url": "https://www.anchorterminal.com/compare/countly-vs-heap"
      },
      {
        "json": "https://www.anchorterminal.com/compare/heap-vs-woopra.json",
        "title": "Heap vs Woopra",
        "url": "https://www.anchorterminal.com/compare/heap-vs-woopra"
      },
      {
        "json": "https://www.anchorterminal.com/compare/countly-vs-launchdarkly.json",
        "title": "Countly vs LaunchDarkly",
        "url": "https://www.anchorterminal.com/compare/countly-vs-launchdarkly"
      }
    ],
    "scores": [
      {
        "by": 52,
        "countly": 28,
        "edge": "woopra",
        "key": "reliability",
        "name": "Reliability",
        "weight": 16,
        "woopra": 80
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 30,
        "countly": 75,
        "edge": "countly",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "weight": 13,
        "woopra": 45
      },
      {
        "by": 21,
        "countly": 66,
        "edge": "countly",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "weight": 13,
        "woopra": 45
      },
      {
        "by": 41,
        "countly": 63,
        "edge": "countly",
        "key": "security",
        "name": "Security \u0026 auth",
        "weight": 14,
        "woopra": 22
      },
      {
        "by": 13,
        "countly": 17,
        "edge": "woopra",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "weight": 10,
        "woopra": 30
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 71,
        "countly": 80,
        "edge": "countly",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "weight": 7,
        "woopra": 9
      },
      {
        "by": 9,
        "countly": 70,
        "edge": "countly",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "weight": 7,
        "woopra": 61
      }
    ],
    "summary": "Countly scores 54.8 (C) on agent readiness against Woopra's 44.4 (E), and leads in 5 of 7 scored categories. Woopra leads on reliability and payments \u0026 pricing. Both do analytics query.",
    "verdicts": {
      "countly": "Countly suits an agent working against a server its owner already runs. The official MCP server filters its 209 tools by edition, plugin and permission and has per-category read-only settings. No status page, OpenAPI document or published API rate limit was found, and the Flex trial needs a credit card.",
      "woopra": "Woopra's REST API returns saved Trends, Journeys, Retention and Attribution reports, profiles and raw session logs, with published limits of 300 calls a minute and 3,000 a day per project. A report must first be built in the web app, the tracking endpoints accept events without a secret by default, and no changelog or SLA was found."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/countly-vs-woopra",
    "json": "https://www.anchorterminal.com/compare/countly-vs-woopra.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/countly-vs-woopra.md",
    "slim": "https://www.anchorterminal.com/compare/countly-vs-woopra.min.md"
  },
  "markdown": "Countly scores 54.8 (C) on agent readiness against Woopra's 44.4 (E), and leads in 5 of 7 scored categories. Woopra leads on reliability and payments \u0026 pricing. Both do analytics query.\n\n- Countly: grade C, 54.8/100, rank #607 of 842. Markdown https://www.anchorterminal.com/tools/countly.md · JSON https://www.anchorterminal.com/api/v1/tools/countly.json\n- Woopra: grade E, 44.4/100, rank #779 of 842. Markdown https://www.anchorterminal.com/tools/woopra.md · JSON https://www.anchorterminal.com/api/v1/tools/woopra.json\n\n## Which one, for what\n\n### Countly (C)\n\nGood 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.\n\nAhead on:\n- Schema \u0026 documentation, 75 against 45\n- Agent ergonomics, 66 against 45\n- Security \u0026 auth, 63 against 22\n- Maintenance \u0026 community, 80 against 9\n- Transparency \u0026 trust, 70 against 61\n\nAlso in its favour:\n- Runs on your own machine\n- Open source\n\nWatch for: No public status page or incident history was found for Flex servers or for mcp.count.ly\n\n### Woopra (E)\n\nGood for: An agent that reads a company's existing Woopra reports, looks up or edits customer profiles, or exports raw sessions on a schedule.\n\nAhead on:\n- Reliability, 80 against 28\n- Payments \u0026 pricing, 30 against 17\n\nWatch for: Report endpoints run a report saved in the web app by `report_id`. No endpoint to define a query, funnel or segment was found in the reference\n\n\n## Score by category\n\n| Category | Weight | Countly | Woopra | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 28 | 80 | Woopra +52 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 75 | 45 | Countly +30 |\n| Agent ergonomics | 13% (16.2 this run) | 66 | 45 | Countly +21 |\n| Security \u0026 auth | 14% (17.5 this run) | 63 | 22 | Countly +41 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 17 | 30 | Woopra +13 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 80 | 9 | Countly +71 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 70 | 61 | Countly +9 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **54.8 · C** | **44.4 · E** | |\n\n## Facts side by side\n\n| Fact | Countly | Woopra |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Countly Ltd | Woopra, Inc. |\n| Hosted endpoint | `https://mcp.count.ly/mcp` | `https://www.woopra.com/rest/3.10` |\n| Transports | HTTP, stdio, Streamable HTTP | HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| 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 | Proprietary service under Woopra's terms of service. The browser tracker and the SDKs on GitHub are MIT, and the Node package is ISC |\n| Tools exposed | 209 | none |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-07 | 2026-03-16 |\n| Terms last updated | 2026-09-25 | 2025-12-10 |\n| Privacy policy last updated | 2026-09-25 | 2025-08-01 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | yes |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | 28k npm/wk | 415 npm/wk |\n\n## Verdicts\n\n**Countly.** Countly suits an agent working against a server its owner already runs. The official MCP server filters its 209 tools by edition, plugin and permission and has per-category read-only settings. No status page, OpenAPI document or published API rate limit was found, and the Flex trial needs a credit card.\n\n**Woopra.** Woopra's REST API returns saved Trends, Journeys, Retention and Attribution reports, profiles and raw session logs, with published limits of 300 calls a minute and 3,000 a day per project. A report must first be built in the web app, the tracking endpoints accept events without a secret by default, and no changelog or SLA was found.\n\n## Before you call either\n\n### Countly\n\n1. Create a dedicated token in the Token Manager, limited to the apps and endpoints the task needs, and send it in the `countly-token` header, not the URL\n2. Set `COUNTLY_TOOLS_ALL=R` unless the task needs writes. The token's own permissions still apply and the stricter of the two wins\n3. Call `apps_list` first. Most tools need `app_id` or an exact `app_name`\n4. Check `get_version` for the detected edition before planning funnel, retention or cohort queries, which need Enterprise plugins\n5. Set `ENABLE_ANALYTICS=false` to stop usage reports to stats.count.ly, and prefer the stdio server to mcp.count.ly so the server URL and token stay local\n\n### Woopra\n\n1. Ask the owner to build and save each report in the web app first, then pass the last path segment of its URL as `report_id`\n2. Authenticate REST calls with HTTP Basic, using the App ID and Secret Key from the Access Keys tab, against `https://www.woopra.com/rest/3.10/`\n3. Stay under 300 calls a minute, 600 an hour and 3,000 a day per project. A 429 carries no documented retry interval, so back off on your own schedule\n4. Reuse the `snapshot` ID from the first response when paging with `offset`, or pages past 1,000 records may not agree\n5. Send `cookie` or a `cv_` identifier such as `cv_email` on every track call. Without one the event lands on a random profile that can't be identified later\n6. When reading `/logs/export`, delete the profile named in each `type: \"delete\"` line. The following lines log its data again under `new_id`\n\n## Questions\n\n### Which is better for AI agents, Countly or Woopra?\n\nCountly scores 54.8 (C) on agent readiness against Woopra's 44.4 (E), and leads in 5 of 7 scored categories. Woopra leads on reliability and payments \u0026 pricing.\n\n### Do Countly and Woopra need an API key?\n\nCountly needs an API key. Woopra takes an API key or an OAuth sign-in.\n\n### Can an agent call Countly and Woopra without installing anything?\n\nYes. Countly has a hosted endpoint at https://mcp.count.ly/mcp and Woopra at https://www.woopra.com/rest/3.10.\n\n### Are Countly and Woopra open source?\n\nCountly is open source (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). No open-source release is listed for Woopra.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/countly-vs-woopra.json, and with the fewest tokens: https://www.anchorterminal.com/compare/countly-vs-woopra.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"countly\", \"b\": \"woopra\"}`. From a terminal: `anchor compare countly woopra`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/countly.json and https://www.anchorterminal.com/api/v1/tools/woopra.json\n\n## Other comparisons with Countly or Woopra\n\n- [Amplitude vs Countly](https://www.anchorterminal.com/compare/amplitude-vs-countly.md)\n- [Amplitude vs Woopra](https://www.anchorterminal.com/compare/amplitude-vs-woopra.md)\n- [Countly vs Fullstory](https://www.anchorterminal.com/compare/countly-vs-fullstory.md)\n- [Countly vs GrowthBook](https://www.anchorterminal.com/compare/countly-vs-growthbook.md)\n- [Countly vs Mixpanel](https://www.anchorterminal.com/compare/countly-vs-mixpanel.md)\n- [Countly vs Optimizely Experimentation](https://www.anchorterminal.com/compare/countly-vs-optimizely.md)\n- [Countly vs Pendo](https://www.anchorterminal.com/compare/countly-vs-pendo.md)\n- [Countly vs PostHog](https://www.anchorterminal.com/compare/countly-vs-posthog.md)\n- [Countly vs Statsig](https://www.anchorterminal.com/compare/countly-vs-statsig.md)\n- [Fullstory vs Woopra](https://www.anchorterminal.com/compare/fullstory-vs-woopra.md)\n- [GrowthBook vs Woopra](https://www.anchorterminal.com/compare/growthbook-vs-woopra.md)\n- [Mixpanel vs Woopra](https://www.anchorterminal.com/compare/mixpanel-vs-woopra.md)\n- [Optimizely Experimentation vs Woopra](https://www.anchorterminal.com/compare/optimizely-vs-woopra.md)\n- [Pendo vs Woopra](https://www.anchorterminal.com/compare/pendo-vs-woopra.md)\n- [PostHog vs Woopra](https://www.anchorterminal.com/compare/posthog-vs-woopra.md)\n- [Statsig vs Woopra](https://www.anchorterminal.com/compare/statsig-vs-woopra.md)\n- [Countly vs Heap](https://www.anchorterminal.com/compare/countly-vs-heap.md)\n- [Heap vs Woopra](https://www.anchorterminal.com/compare/heap-vs-woopra.md)\n- [Countly vs LaunchDarkly](https://www.anchorterminal.com/compare/countly-vs-launchdarkly.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-10-09",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.4",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "Countly vs Woopra",
        "url": ""
      }
    ],
    "description": "Countly scores 54.8 (C) on agent readiness against Woopra's 44.4 (E), and leads in 5 of 7 scored categories. Woopra leads on reliability and payments \u0026 pricing. Both do analytics query. Category scores, facts, verdicts and agent notes side by side.",
    "facts": [
      "Countly C 54.8",
      "Woopra E 44.4",
      "scores"
    ],
    "h1": "Countly vs Woopra",
    "image": "https://www.anchorterminal.com/assets/og/compare-countly-vs-woopra.png",
    "path": "/compare/countly-vs-woopra",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Countly vs Woopra for AI agents, C 54.8 vs E 44.4 | Anchor Terminal",
    "toc": null,
    "updated": "2026-10-09",
    "url": "https://www.anchorterminal.com/compare/countly-vs-woopra"
  },
  "tokens": {
    "markdown": 2400,
    "slim": 730
  },
  "version": 1
}
