{
  "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": "Statsig scores 72.3 (BB) on agent readiness against Countly's 54.8 (C), and leads in every scored category.",
    "b": {
      "slug": "statsig",
      "name": "Statsig",
      "vendor": "Amplitude, Inc.",
      "vendorUrl": "https://www.statsig.com",
      "kind": "http-api",
      "category": "product-analytics",
      "summary": "Statsig is a hosted platform for feature flags, experiments and product analytics, run by Amplitude, Inc. since May 2026. Agents reach it through the Console API, which has a public OpenAPI spec, and an official hosted MCP server.",
      "url": "https://www.anchorterminal.com/tools/statsig",
      "markdownUrl": "https://www.anchorterminal.com/tools/statsig.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/statsig.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/statsig.json",
      "repo": "https://github.com/statsig-io/statsig-server-core",
      "license": "Proprietary hosted service under Statsig's self-service or enterprise terms. The SDKs and the agent skills repository on GitHub are ISC",
      "transports": [
        "http",
        "streamable-http"
      ],
      "remoteUrl": "https://api.statsig.com/v3/mcp",
      "packages": [
        {
          "registry": "npm",
          "name": "@statsig/statsig-node-core"
        },
        {
          "registry": "npm",
          "name": "@statsig/js-client"
        },
        {
          "registry": "pypi",
          "name": "statsig-python-core"
        },
        {
          "registry": "npm",
          "name": "@statsig/siggy"
        }
      ],
      "auth": "mixed",
      "authNotes": "Self-serve. The Console API takes a Console API key in the `STATSIG-API-KEY` header, created in project settings as read-only or read and write. The MCP server uses OAuth with PKCE and dynamic client registration, which issues a personal Console API key carrying the user's role, or takes a Console key in the `statsig-api-key` header. OAuth needs the organisation owner to allow personal keys for the role. Flag evaluation and event logging take a client or server SDK key.",
      "pricing": "freemium",
      "pricingNotes": "Free Developer plan with no card, covering 2 million events and 50,000 session replays a month. Pro is $150 a month with 5 million events, then $0.05 per 1,000 events. Enterprise is by contract. Flag and config checks are unlimited on every plan, and API and MCP calls are not billed. An agent can start on the free plan without a contract (https://www.statsig.com/pricing, checked 2026-10-08).",
      "priceSummary": "$150 / mo",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the docs corpus, the OpenAPI spec or the pricing page (checked 2026-10-08).",
        "endpoints": []
      },
      "toolCount": 18,
      "popularity": {
        "githubStars": null,
        "npmWeekly": 4157066,
        "pypiWeekly": 893619,
        "asOf": "2026-10-08"
      },
      "docsUrl": "https://docs.statsig.com/console-api/introduction",
      "llmsTxt": "https://docs.statsig.com/llms.txt",
      "openapi": "https://api.statsig.com/openapi/20240601.json",
      "registryName": "com.statsig/statsig-mcp-server",
      "capabilities": [
        "analytics.experiments",
        "analytics.flags",
        "analytics.query",
        "analytics.events"
      ],
      "tags": [
        "official",
        "hosted",
        "mcp",
        "oauth",
        "openapi",
        "llms-txt",
        "free-tier",
        "no-card",
        "status-page",
        "soc2",
        "eu-region"
      ],
      "lastRelease": "2026-09-28",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 72.3,
        "grade": "BB",
        "agentReady": true,
        "rank": 104,
        "ranked": true,
        "rankOf": 842,
        "categoryRank": 1,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 71,
          "maintenance": 81,
          "payments": 40,
          "reliability": 79,
          "schema": 82,
          "security": 74,
          "transparency": 75
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-08"
        },
        "negative": 0,
        "verdict": "Statsig suits agents that manage feature gates and experiments and read their results. Its MCP server has 18 default tools, OAuth, read-only access by project and role, and a confirmation on updates. Errors carry only a status and a message, no idempotency keys were found, and the privacy notice is Amplitude's and doesn't name Statsig.",
        "bestFor": "An agent that creates, updates and cleans up feature gates, dynamic configs and experiments, and reads experiment results and audit history.",
        "strengths": [
          "Hosted MCP server with 18 default tools and a discovery layer that replaced 93 tools on the V1 server",
          "MCP access set per project and per role as no access, read only or read and write, with a confirmation on updates",
          "Public OpenAPI 3.0 spec with 325 operations, plus llms.txt and a Markdown copy of every docs page",
          "Free Developer plan with no card and 2 million events a month, and a public overage price of $0.05 per 1,000 events on Pro",
          "Audit logs kept indefinitely and readable through the API and the `log_read` MCP tool"
        ],
        "weaknesses": [
          "Console API errors carry only `status` and `message`, and the spec documents no 429 response",
          "No idempotency keys were found, and most MCP update tools replace the whole resource",
          "The project Console API key reads and writes everything in a project unless created read-only",
          "The privacy notice is Amplitude's, last updated 31 August 2026, and doesn't name Statsig",
          "The 99.95 per cent SLA needs Enterprise premium support and covers the Console user interface"
        ],
        "agentNotes": [
          "Connect to https://api.statsig.com/v3/mcp. The official MCP registry entry still lists the V1 URL, which has 93 tools",
          "Call `get_context` first to learn the project, your permissions and the review settings",
          "Read the resource before `gate_update`, `experiment_update` or `dynamic_config_update`. They replace the whole resource, so resend every field you want kept",
          "Use `discover_tools` for partial edits, and fetch a fresh `operationHandle` when one expires",
          "On a 429 slow down and back off with jitter. Rejected attempts count towards the quota of about 1,800 mutations per 15 minutes"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "BB",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 72.3
          }
        ],
        "editorialScores": {
          "ergonomics": 71,
          "maintenance": 81,
          "payments": 40,
          "reliability": 79,
          "schema": 82,
          "security": 74,
          "transparency": 64
        },
        "provenanceScore": 85
      },
      "connect": {
        "claudeCode": "claude mcp add --transport http statsig https://api.statsig.com/v3/mcp",
        "config": {
          "mcpServers": {
            "statsig": {
              "url": "https://api.statsig.com/v3/mcp"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/analytics.experiments",
        "tool": "https://letme.dev/statsig"
      },
      "area": "business",
      "unitPrices": [
        {
          "item": "Pro plan",
          "unit": "month",
          "usd": 150,
          "note": "5 million events and 100,000 session replays included"
        },
        {
          "item": "Metered event",
          "unit": "tx",
          "usd": 0.00005,
          "note": "Pro plan, above 5 million a month"
        }
      ],
      "provenance": {
        "legalEntity": "Amplitude, Inc.",
        "domain": "statsig.com",
        "domainRegistered": "1998-12-29",
        "endpointOnVendorDomain": true,
        "terms": "https://www.statsig.com/terms",
        "privacy": "https://amplitude.com/privacy",
        "statusPage": "https://status.statsig.com",
        "changelog": "https://www.statsig.com/updates",
        "securityTxt": "none",
        "checked": "2026-10-08",
        "notes": [
          "The self-service subscription agreement at statsig.com/terms, effective 4 August 2025, names Amplitude, Inc. as the party called Statsig. The enterprise terms (effective 18 February 2026) and the DPA do the same.",
          "statsig.com/privacy redirects to amplitude.com/privacy, a notice last updated 31 August 2026 that covers Amplitude, Inc. and its affiliates and doesn't name Statsig. It says it does not apply to end-user data that customers send to the product.",
          "statsig.com/legal/subprocessors redirects to amplitude.com/subprocessor-list, last updated 13 May 2026, which marks the providers used for Statsig-branded services.",
          "The MCP server answers at api.statsig.com. The Console API answers at statsigapi.net, a second domain the vendor's docs name.",
          "www.statsig.com/.well-known/security.txt returns 404.",
          "RDAP for statsig.com gives a registration date of 1998-12-29."
        ],
        "score": 85
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/statsig.json",
      "live": {
        "slug": "statsig",
        "probe": {
          "target": "https://api.statsig.com/v3/mcp",
          "method": "get",
          "lastAt": "2026-10-09T10:42:57.764142246Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 59,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 41,
          "p95ms24h": 60,
          "samples24h": 184,
          "samples30d": 184,
          "days": [
            {
              "date": "2026-10-08",
              "probes": 70,
              "ok": 70
            },
            {
              "date": "2026-10-09",
              "probes": 114,
              "ok": 114
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.statsig.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-10-09T10:42:04.94127402Z"
        },
        "versions": [
          {
            "registry": "mcp-registry",
            "name": "com.statsig/statsig-mcp-server",
            "version": "1.0.0",
            "seenAt": "2026-10-09T02:57:46.004536428Z"
          }
        ],
        "pages": [
          {
            "url": "https://www.statsig.com/updates",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-10-08T18:30:46.247718302Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "3bba7a8e7236"
          },
          {
            "url": "https://www.statsig.com/pricing",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-10-08T18:30:41.954344318Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "d0e8593f7c0e"
          },
          {
            "url": "https://www.statsig.com/terms",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-10-08T18:30:44.722171717Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "dc465dc5a41d"
          }
        ],
        "updatedAt": "2026-10-09T10:42:57.764142246Z"
      }
    },
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Countly Ltd",
        "b": "Amplitude, Inc.",
        "name": "Vendor"
      },
      {
        "a": "https://mcp.count.ly/mcp",
        "b": "https://api.statsig.com/v3/mcp",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP, stdio, Streamable HTTP",
        "b": "HTTP, Streamable HTTP",
        "name": "Transports"
      },
      {
        "a": "API key",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Paid",
        "b": "Freemium",
        "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 hosted service under Statsig's self-service or enterprise terms. The SDKs and the agent skills repository on GitHub are ISC",
        "name": "Licence"
      },
      {
        "a": "209",
        "b": "18",
        "name": "Tools exposed"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "not listed",
        "b": "com.statsig/statsig-mcp-server",
        "name": "MCP registry"
      },
      {
        "a": "2026-10-07",
        "b": "2026-09-28",
        "name": "Last release"
      },
      {
        "a": "2026-09-25",
        "b": "2025-08-04",
        "name": "Terms last updated"
      },
      {
        "a": "2026-09-25",
        "b": "2026-08-31",
        "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": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not found in the text",
        "b": "yes",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "yes",
        "b": "yes",
        "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": "4.2M npm/wk, 894k PyPI/wk",
        "name": "Popularity"
      }
    ],
    "faq": [
      {
        "answer": "Statsig scores 72.3 (BB) on agent readiness against Countly's 54.8 (C), and leads in every scored category.",
        "question": "Which is better for AI agents, Countly or Statsig?"
      },
      {
        "answer": "Countly needs an API key. Statsig takes an API key or an OAuth sign-in.",
        "question": "Do Countly and Statsig need an API key?"
      },
      {
        "answer": "Yes. Countly has a hosted endpoint at https://mcp.count.ly/mcp and Statsig at https://api.statsig.com/v3/mcp.",
        "question": "Can an agent call Countly and Statsig 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 Statsig.",
        "question": "Are Countly and Statsig open source?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": null,
        "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, 79 against 28",
          "Schema \u0026 documentation, 82 against 75",
          "Agent ergonomics, 71 against 66",
          "Security \u0026 auth, 74 against 63",
          "Payments \u0026 pricing, 40 against 17",
          "Transparency \u0026 trust, 75 against 70"
        ],
        "also": [
          "Agent-ready, a grade of BB or better",
          "Free to start without a card"
        ],
        "goodFor": "An agent that creates, updates and cleans up feature gates, dynamic configs and experiments, and reads experiment results and audit history.",
        "slug": "statsig",
        "watchFor": "Console API errors carry only `status` and `message`, and the spec documents no 429 response"
      }
    ],
    "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-statsig.json",
        "title": "Amplitude vs Statsig",
        "url": "https://www.anchorterminal.com/compare/amplitude-vs-statsig"
      },
      {
        "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-woopra.json",
        "title": "Countly vs Woopra",
        "url": "https://www.anchorterminal.com/compare/countly-vs-woopra"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullstory-vs-statsig.json",
        "title": "Fullstory vs Statsig",
        "url": "https://www.anchorterminal.com/compare/fullstory-vs-statsig"
      },
      {
        "json": "https://www.anchorterminal.com/compare/mixpanel-vs-statsig.json",
        "title": "Mixpanel vs Statsig",
        "url": "https://www.anchorterminal.com/compare/mixpanel-vs-statsig"
      },
      {
        "json": "https://www.anchorterminal.com/compare/pendo-vs-statsig.json",
        "title": "Pendo vs Statsig",
        "url": "https://www.anchorterminal.com/compare/pendo-vs-statsig"
      },
      {
        "json": "https://www.anchorterminal.com/compare/posthog-vs-statsig.json",
        "title": "PostHog vs Statsig",
        "url": "https://www.anchorterminal.com/compare/posthog-vs-statsig"
      },
      {
        "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-statsig.json",
        "title": "Heap vs Statsig",
        "url": "https://www.anchorterminal.com/compare/heap-vs-statsig"
      },
      {
        "json": "https://www.anchorterminal.com/compare/growthbook-vs-statsig.json",
        "title": "GrowthBook vs Statsig",
        "url": "https://www.anchorterminal.com/compare/growthbook-vs-statsig"
      },
      {
        "json": "https://www.anchorterminal.com/compare/optimizely-vs-statsig.json",
        "title": "Optimizely Experimentation vs Statsig",
        "url": "https://www.anchorterminal.com/compare/optimizely-vs-statsig"
      },
      {
        "json": "https://www.anchorterminal.com/compare/countly-vs-launchdarkly.json",
        "title": "Countly vs LaunchDarkly",
        "url": "https://www.anchorterminal.com/compare/countly-vs-launchdarkly"
      },
      {
        "json": "https://www.anchorterminal.com/compare/launchdarkly-vs-statsig.json",
        "title": "LaunchDarkly vs Statsig",
        "url": "https://www.anchorterminal.com/compare/launchdarkly-vs-statsig"
      }
    ],
    "scores": [
      {
        "by": 51,
        "countly": 28,
        "edge": "statsig",
        "key": "reliability",
        "name": "Reliability",
        "statsig": 79,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 7,
        "countly": 75,
        "edge": "statsig",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "statsig": 82,
        "weight": 13
      },
      {
        "by": 5,
        "countly": 66,
        "edge": "statsig",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "statsig": 71,
        "weight": 13
      },
      {
        "by": 11,
        "countly": 63,
        "edge": "statsig",
        "key": "security",
        "name": "Security \u0026 auth",
        "statsig": 74,
        "weight": 14
      },
      {
        "by": 23,
        "countly": 17,
        "edge": "statsig",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "statsig": 40,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 1,
        "countly": 80,
        "edge": "statsig",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "statsig": 81,
        "weight": 7
      },
      {
        "by": 5,
        "countly": 70,
        "edge": "statsig",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "statsig": 75,
        "weight": 7
      }
    ],
    "summary": "Statsig scores 72.3 (BB) on agent readiness against Countly's 54.8 (C), and leads in every scored category. 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.",
      "statsig": "Statsig suits agents that manage feature gates and experiments and read their results. Its MCP server has 18 default tools, OAuth, read-only access by project and role, and a confirmation on updates. Errors carry only a status and a message, no idempotency keys were found, and the privacy notice is Amplitude's and doesn't name Statsig."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/countly-vs-statsig",
    "json": "https://www.anchorterminal.com/compare/countly-vs-statsig.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/countly-vs-statsig.md",
    "slim": "https://www.anchorterminal.com/compare/countly-vs-statsig.min.md"
  },
  "markdown": "Statsig scores 72.3 (BB) on agent readiness against Countly's 54.8 (C), and leads in every scored category. 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- Statsig: grade BB, 72.3/100, rank #104 of 842. Markdown https://www.anchorterminal.com/tools/statsig.md · JSON https://www.anchorterminal.com/api/v1/tools/statsig.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\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### Statsig (BB)\n\nGood for: An agent that creates, updates and cleans up feature gates, dynamic configs and experiments, and reads experiment results and audit history.\n\nAhead on:\n- Reliability, 79 against 28\n- Schema \u0026 documentation, 82 against 75\n- Agent ergonomics, 71 against 66\n- Security \u0026 auth, 74 against 63\n- Payments \u0026 pricing, 40 against 17\n- Transparency \u0026 trust, 75 against 70\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- Free to start without a card\n\nWatch for: Console API errors carry only `status` and `message`, and the spec documents no 429 response\n\n\n## Score by category\n\n| Category | Weight | Countly | Statsig | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 28 | 79 | Statsig +51 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 75 | 82 | Statsig +7 |\n| Agent ergonomics | 13% (16.2 this run) | 66 | 71 | Statsig +5 |\n| Security \u0026 auth | 14% (17.5 this run) | 63 | 74 | Statsig +11 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 17 | 40 | Statsig +23 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 80 | 81 | Statsig +1 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 70 | 75 | Statsig +5 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **54.8 · C** | **72.3 · BB** | |\n\n## Facts side by side\n\n| Fact | Countly | Statsig |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Countly Ltd | Amplitude, Inc. |\n| Hosted endpoint | `https://mcp.count.ly/mcp` | `https://api.statsig.com/v3/mcp` |\n| Transports | HTTP, stdio, Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Paid | Freemium |\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 hosted service under Statsig's self-service or enterprise terms. The SDKs and the agent skills repository on GitHub are ISC |\n| Tools exposed | 209 | 18 |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `com.statsig/statsig-mcp-server` |\n| Last release | 2026-10-07 | 2026-09-28 |\n| Terms last updated | 2026-09-25 | 2025-08-04 |\n| Privacy policy last updated | 2026-09-25 | 2026-08-31 |\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 | not found in the text |\n| Terms restrict benchmarking | not found in the text | yes |\n| Terms or service can change without notice | yes | yes |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | 28k npm/wk | 4.2M npm/wk, 894k PyPI/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**Statsig.** Statsig suits agents that manage feature gates and experiments and read their results. Its MCP server has 18 default tools, OAuth, read-only access by project and role, and a confirmation on updates. Errors carry only a status and a message, no idempotency keys were found, and the privacy notice is Amplitude's and doesn't name Statsig.\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### Statsig\n\n1. Connect to https://api.statsig.com/v3/mcp. The official MCP registry entry still lists the V1 URL, which has 93 tools\n2. Call `get_context` first to learn the project, your permissions and the review settings\n3. Read the resource before `gate_update`, `experiment_update` or `dynamic_config_update`. They replace the whole resource, so resend every field you want kept\n4. Use `discover_tools` for partial edits, and fetch a fresh `operationHandle` when one expires\n5. On a 429 slow down and back off with jitter. Rejected attempts count towards the quota of about 1,800 mutations per 15 minutes\n\n## Questions\n\n### Which is better for AI agents, Countly or Statsig?\n\nStatsig scores 72.3 (BB) on agent readiness against Countly's 54.8 (C), and leads in every scored category.\n\n### Do Countly and Statsig need an API key?\n\nCountly needs an API key. Statsig takes an API key or an OAuth sign-in.\n\n### Can an agent call Countly and Statsig without installing anything?\n\nYes. Countly has a hosted endpoint at https://mcp.count.ly/mcp and Statsig at https://api.statsig.com/v3/mcp.\n\n### Are Countly and Statsig 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 Statsig.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/countly-vs-statsig.json, and with the fewest tokens: https://www.anchorterminal.com/compare/countly-vs-statsig.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"countly\", \"b\": \"statsig\"}`. From a terminal: `anchor compare countly statsig`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/countly.json and https://www.anchorterminal.com/api/v1/tools/statsig.json\n\n## Other comparisons with Countly or Statsig\n\n- [Amplitude vs Countly](https://www.anchorterminal.com/compare/amplitude-vs-countly.md)\n- [Amplitude vs Statsig](https://www.anchorterminal.com/compare/amplitude-vs-statsig.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 Woopra](https://www.anchorterminal.com/compare/countly-vs-woopra.md)\n- [Fullstory vs Statsig](https://www.anchorterminal.com/compare/fullstory-vs-statsig.md)\n- [Mixpanel vs Statsig](https://www.anchorterminal.com/compare/mixpanel-vs-statsig.md)\n- [Pendo vs Statsig](https://www.anchorterminal.com/compare/pendo-vs-statsig.md)\n- [PostHog vs Statsig](https://www.anchorterminal.com/compare/posthog-vs-statsig.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 Statsig](https://www.anchorterminal.com/compare/heap-vs-statsig.md)\n- [GrowthBook vs Statsig](https://www.anchorterminal.com/compare/growthbook-vs-statsig.md)\n- [Optimizely Experimentation vs Statsig](https://www.anchorterminal.com/compare/optimizely-vs-statsig.md)\n- [Countly vs LaunchDarkly](https://www.anchorterminal.com/compare/countly-vs-launchdarkly.md)\n- [LaunchDarkly vs Statsig](https://www.anchorterminal.com/compare/launchdarkly-vs-statsig.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 Statsig",
        "url": ""
      }
    ],
    "description": "Statsig scores 72.3 (BB) on agent readiness against Countly's 54.8 (C), and leads in every scored category. Both do analytics query. Category scores, facts, verdicts and agent notes side by side.",
    "facts": [
      "Countly C 54.8",
      "Statsig BB 72.3",
      "scores"
    ],
    "h1": "Countly vs Statsig",
    "image": "https://www.anchorterminal.com/assets/og/compare-countly-vs-statsig.png",
    "path": "/compare/countly-vs-statsig",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Countly vs Statsig for AI agents, C 54.8 vs BB 72.3 | Anchor Terminal",
    "toc": null,
    "updated": "2026-10-09",
    "url": "https://www.anchorterminal.com/compare/countly-vs-statsig"
  },
  "tokens": {
    "markdown": 2350,
    "slim": 730
  },
  "version": 1
}