# Mostly Good Metrics vs Statsig

> Statsig scores 72.4 (BB) to Mostly Good Metrics's 41.7 (E) for analytics queries. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/mostly-good-metrics-vs-statsig
- Markdown: https://www.anchorterminal.com/compare/mostly-good-metrics-vs-statsig.md (~5,050 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Statsig scores 72.4 (BB) on agent readiness against Mostly Good Metrics's 41.7 (E), and leads in every scored category. Both do analytics queries.

- Mostly Good Metrics: grade E, 41.7/100, rank #1295 of 1510. Markdown https://www.anchorterminal.com/tools/mostly-good-metrics.md · JSON https://www.anchorterminal.com/api/v1/tools/mostly-good-metrics.json
- Statsig: grade BB, 72.4/100, rank #128 of 1510. Markdown https://www.anchorterminal.com/tools/statsig.md · JSON https://www.anchorterminal.com/api/v1/tools/statsig.json
- Best product analytics and experimentation tools for AI agents: https://www.anchorterminal.com/best/product-analytics/index.md
- All 170 product analytics comparisons: https://www.anchorterminal.com/compare/product-analytics/index.md

## Which one, for what

### Mostly Good Metrics (E)

Good for: Indie and small-team apps that want simple funnels and retention an agent can query.

Watch for: Public beta run by one developer, with no named legal entity in the terms

### Statsig (BB)

Good for: An agent that creates, updates and cleans up feature gates, dynamic configs and experiments, and reads experiment results and audit history.

Ahead on:
- Reliability, 79 against 29
- Schema & documentation, 82 against 49
- Agent ergonomics, 71 against 49
- Security & auth, 74 against 33
- Payments & pricing, 40 against 30
- Maintenance & community, 81 against 74
- Transparency & trust, 76 against 45

Also in its favour:
- Agent-ready, a grade of BB or better

Watch for: Console API errors carry only `status` and `message`, and the spec documents no 429 response


## Why the edge

### Reliability: Statsig +50

- Mostly Good Metrics (29): Graded on the hosted service with the hosted lines. No status page was found (0) and no incident history could be read (5). Ingestion limits are documented per plan (1,000 to 100,000 events a minute and 10,000 to 1,000,000 an hour), but no limit for MCP or query calls was found (12 of 15). 429 with Retry-After in the header and body, and the SDKs queue events and back off. No idempotency or safe-retry guidance for writes (12 of 15). No SLA (0). The press kit calls the product a public beta (0). 0+5+12+12+0+0 = 29.
- Statsig (79): Graded on the hosted service with the hosted lines. Statuspage at status.statsig.com with 14 components, among them Console API, Config Delivery API and Log Event API (20). Three incidents between 3 August and 1 November 2026, all Warehouse Native delays (export delays from 6 August resolved 8 August, delayed exposure results on 26 August and its follow-up resolved 31 August), marked minor or none per the 8 October check, and nothing posted since 31 August (20 of 30). The 8 July 2026 major, when launched gates returned false through the V2 Config Delivery API for about 4 hours 44 minutes, is outside the window. The docs give about 1,800 mutation attempts per 15 minutes per project, while the OpenAPI description gave about 100 per 10 seconds and 900 per 15 minutes per the 8 October check, and no number was found for reads (12 of 15). The docs ask for exponential backoff with jitter on 429. No `Retry-After` header and no idempotency keys were found (10 of 15). The enterprise terms give 99.95 per cent monthly availability with credits, for customers with premium support, measured on the Console user interface (7 of 10). The Console API is versioned and the MCP V3 docs carry no beta label (10).

### Security & auth: Statsig +41

- Mostly Good Metrics (33): OAuth 2.0 with PKCE, dynamic client registration and a revocation endpoint for MCP and the CLI; project ingest keys in a Bearer header that can be pinned to origins or app IDs. The only tool scope advertised is mcp:tools, so a connection gets every tool the user can use (24 of 30). Restricted keys and a confirmation step for unrestricted keys in the CLI; no read-only MCP mode or approval for deletes was found (6 of 20). Event properties come from apps and end users and reach the agent, and no prompt-injection guidance was found (3 of 15). No audit log was found (0). No security.txt, disclosure policy or certification was found (0). 24+6+3+0+0 = 33.
- Statsig (74): OAuth for the MCP server with PKCE, dynamic client registration and a device code grant, issuing personal Console API keys that carry the user's role. Console keys can be created read-only or read and write, and rotated or deactivated through the API. The OAuth metadata lists no scopes, and a project Console key reaches every Console API endpoint (25 of 30). MCP scope is set per project and per role as no access, read only or read and write. Updates and destructive operations need a confirmation, and project review policies still apply (19 of 20). No guidance on prompt injection was found, though tools return names, descriptions and log data that people wrote. The docs tell users to review each change before the agent confirms (4 of 15). Audit logs are kept indefinitely with an API, and personal keys attribute changes to a user (14 of 15). SOC 2 Type II and a bug bounty programme are stated on the security page, with no public programme link and no security.txt (12 of 20).

### Schema & documentation: Statsig +33

- Mostly Good Metrics (49): No OpenAPI file was found. The docs say every MCP tool describes its own parameters, and the query definition object is documented in full; we didn't open an MCP session to read the schemas (12 of 25). No llms.txt (404) and no Markdown pages served for agents (0). Each tool area is documented with examples, and the docs say when to use query_metrics instead of repeated execute_query calls (10 of 20). The query definition lists metrics, dimensions, date ranges and filter operators (9 of 15). The ingestion API documents its error body and status codes, and query_metrics reports per-item errors (11 of 15). /v1 and /api/v2 paths and dated SDK tags, but no product changelog (7 of 15). 12+0+10+9+11+7 = 49.
- Statsig (82): Public OpenAPI 3.0 spec for Console API version 20240601 with 209 paths and 325 operations, per the 8 October check, not re-read on 1 November, and typed MCP tools per the tool reference (25). llms.txt, llms-full.txt, a Markdown copy of each page and a public docs MCP server (10). Every operation has a summary but only 29 of 325 have a description, per the 8 October check. The MCP tool reference states each tool's purpose and when to ask the user first (11 of 20). 1,164 enums across 188 schemas, with required fields marked, per the 8 October check (12 of 15). Examples on most responses. The spec documents 401 on 156 operations, 404 on 126 and 400 on 106, and no 429, per the 8 October check (11 of 15). A dated API version sent in the `STATSIG-API-VERSION` header with a promise not to break a version, and a dated product updates page. No changelog for the API alone was found (13 of 15).

### Transparency & trust: Statsig +31

- Mostly Good Metrics (45): The service is closed; the SDKs and CLI are MIT. Terms of December 2025 with no legal entity named (18 of 30). The privacy policy and terms agree on raw-event retention for the subscription's life and deletion within 14 days of account deletion; the about page says data is not used to train models. No DPA was found (18 of 30). The legacy X-MGM-Key header is still supported, and no deprecation policy was found (3 of 20). The terms name eight sub-processors with their purpose, without data locations (12 of 20). 18+18+3+12 = 51.
- Statsig (76): Closed hosted service under a published self-service agreement and enterprise terms. The SDKs are open source under ISC (17 of 30). The terms, DPA and AI governance page mostly agree. The DPA names Amplitude, Inc. as processor and keeps data as long as necessary, the pricing page gives 1 year of analytics retention on the free plan, and the docs say customer data is not used to build AI models without written consent. The privacy notice is Amplitude's and doesn't name Statsig, and the self-service terms name Amplitude, Inc. under an effective date of 4 August 2025, before Statsig joined Amplitude on 5 May 2026 (18 of 30). Each Console API version is promised not to break, a deprecation notices page gives dates, and MCP V1 stays supported. No notice period is stated (12 of 20). Amplitude's sub-processor list, updated 13 May 2026, gives locations and marks the providers used for Statsig-branded services. EU hosting is an Enterprise option (17 of 20).

### Agent ergonomics: Statsig +22

- Mostly Good Metrics (49): 53 tools, more than 30 (5). We added 3 because Goals and Alerts tools load only where enabled and query_metrics batches up to 10 queries (8 of 25). Date ranges, grouping and filters on queries; no documented page or limit parameters for lists (12 of 20). JSON errors with a message, and per-item status in batch results (13 of 20). Annotations weren't readable without a session, the tool list includes deletes and key revocation, and no idempotency keys were found (4 of 20). Five client SDKs and a CLI with `--json` output (12 of 15). 8+12+13+4+12 = 49.
- Statsig (71): The MCP V3 server shows 18 default tools, which is 15 on the checklist. Add back 8 for the discovery layer that reaches other operations on demand, `query_fields` on experiment reads and read-only access (23 of 25). `limit` and `page` on 49 list operations with pagination metadata per the 8 October check, a cursor on the Logs Explorer query, and filters by tag, status, creator and date (17 of 20). Errors are a `status` and a `message` with no machine code, and MCP results set `isError` (11 of 20). No idempotency keys were found. Updates and `api_destructive` calls need a `confirmation` object, and operations are split into read, write and destructive lanes. We could not read the live tool annotations (10 of 20). The SDKs cover flag evaluation and event logging in many languages, not the Console API, and the `siggy` CLI on npm is version 0.0.4 from September 2024 (10 of 15).

### Payments & pricing: Statsig +10

- Mostly Good Metrics (30): No x402, MPP or L402 (0). Plan prices with event allowances are on the home page; no per-event price (10). Free plan with no card, stated on the home and about pages (20). Signup and OAuth approval happen in a browser (0). 0+10+20+0 = 30.
- Statsig (40): No x402, MPP or L402 (0). Prices are public without a login. Pro is $150 a month with 5 million events, then $0.05 per 1,000 events (20). The Developer plan is free with no card and 2 million events a month (20). A person signs up in a browser, then creates a key or approves OAuth (0).

## Score by category

| Category | Weight | Mostly Good Metrics | Statsig | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 29 | 79 | Statsig +50 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 49 | 82 | Statsig +33 |
| Agent ergonomics | 13% (16.2 this run) | 49 | 71 | Statsig +22 |
| Security & auth | 14% (17.5 this run) | 33 | 74 | Statsig +41 |
| Payments & pricing | 10% (12.5 this run) | 30 | 40 | Statsig +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 74 | 81 | Statsig +7 |
| Transparency & trust | 7% (8.8 this run) | 45 | 76 | Statsig +31 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **41.7 · E** | **72.4 · BB** | |

## Facts side by side

| Fact | Mostly Good Metrics | Statsig |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Mostly Good Metrics | Amplitude, Inc. |
| Hosted endpoint | `https://app.mostlygoodmetrics.com/mcp` | `https://api.statsig.com/v3/mcp` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | none | Proprietary hosted service under Statsig's self-service or enterprise terms. The SDKs and the agent skills repository on GitHub are ISC |
| Tools exposed | 53 | 18 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | `com.statsig/statsig-mcp-server` |
| Last release | 2026-10-16 | 2026-10-28 |
| Terms last updated | 2025-12-01 | 2025-08-04 |
| Privacy policy last updated | 2025-12-01 | 2026-08-31 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 81 npm/wk | 4.2M npm/wk, 894k PyPI/wk |
| Agent reviews | none | 3.8/5 (4) |

## How the scores have moved

### Mostly Good Metrics

No score change since it was listed.

### Statsig

- +0.1 on 28 October 2026: new evidence

## Verdicts

**Mostly Good Metrics.** Mostly Good Metrics lets an agent run ad-hoc funnels, retention and up to ten metric queries per call through a hosted MCP server with OAuth, at prices from $0. It is a public beta built by one developer, with no status page, no named legal entity and no security policy found.

**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.

## Before you call either

### Mostly Good Metrics

1. Use query_metrics for several aggregate questions instead of repeated execute_query calls
2. Pass inline definitions to execute_funnel and execute_retention rather than creating saved objects
3. Confirm with the user before delete, revoke_api_key or stop_experiment calls, since the server doesn't ask
4. Start a fresh agent session after connecting, since a running client may not reload the tool list
5. On 429 from ingestion, wait for Retry-After before resending events

### Statsig

1. Connect to https://api.statsig.com/v3/mcp. The official MCP registry entry still lists the V1 URL, which has 93 tools
2. Call `get_context` first to learn the project, your permissions and the review settings
3. Read the resource before `gate_update`, `experiment_update` or `dynamic_config_update`. They replace the whole resource, so resend every field you want kept
4. Use `discover_tools` for partial edits, and fetch a fresh `operationHandle` when one expires
5. On a 429 slow down and back off with jitter. Rejected attempts count towards the quota of about 1,800 mutations per 15 minutes

## Questions

### Which is better for AI agents, Mostly Good Metrics or Statsig?

Statsig scores 72.4 (BB) on agent readiness against Mostly Good Metrics's 41.7 (E), and leads in every scored category.

### Do Mostly Good Metrics and Statsig need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call Mostly Good Metrics and Statsig without installing anything?

Yes. Mostly Good Metrics has a hosted endpoint at https://app.mostlygoodmetrics.com/mcp and Statsig at https://api.statsig.com/v3/mcp.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/mostly-good-metrics-vs-statsig.json, and with the fewest tokens: https://www.anchorterminal.com/compare/mostly-good-metrics-vs-statsig.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "mostly-good-metrics", "b": "statsig"}`. From a terminal: `anchor compare mostly-good-metrics statsig`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/mostly-good-metrics.json and https://www.anchorterminal.com/api/v1/tools/statsig.json

## Other comparisons with Mostly Good Metrics or Statsig

- [Amplitude vs Mostly Good Metrics](https://www.anchorterminal.com/compare/amplitude-vs-mostly-good-metrics.md)
- [Amplitude vs Statsig](https://www.anchorterminal.com/compare/amplitude-vs-statsig.md)
- [Basedash MCP vs Mostly Good Metrics](https://www.anchorterminal.com/compare/basedash-mcp-vs-mostly-good-metrics.md)
- [Countly vs Mostly Good Metrics](https://www.anchorterminal.com/compare/countly-vs-mostly-good-metrics.md)
- [Countly vs Statsig](https://www.anchorterminal.com/compare/countly-vs-statsig.md)
- [Fullstory vs Mostly Good Metrics](https://www.anchorterminal.com/compare/fullstory-vs-mostly-good-metrics.md)
- [Fullstory vs Statsig](https://www.anchorterminal.com/compare/fullstory-vs-statsig.md)
- [Matomo vs Mostly Good Metrics](https://www.anchorterminal.com/compare/matomo-vs-mostly-good-metrics.md)
- [Matomo vs Statsig](https://www.anchorterminal.com/compare/matomo-vs-statsig.md)
- [Mixpanel vs Mostly Good Metrics](https://www.anchorterminal.com/compare/mixpanel-vs-mostly-good-metrics.md)
- [Mixpanel vs Statsig](https://www.anchorterminal.com/compare/mixpanel-vs-statsig.md)
- [Mostly Good Metrics vs OpenPanel](https://www.anchorterminal.com/compare/mostly-good-metrics-vs-openpanel.md)
- [Mostly Good Metrics vs Optimizely Experimentation](https://www.anchorterminal.com/compare/mostly-good-metrics-vs-optimizely.md)
- [Mostly Good Metrics vs Pendo](https://www.anchorterminal.com/compare/mostly-good-metrics-vs-pendo.md)
- [Mostly Good Metrics vs PostHog](https://www.anchorterminal.com/compare/mostly-good-metrics-vs-posthog.md)
- [Mostly Good Metrics vs RudderStack MCP](https://www.anchorterminal.com/compare/mostly-good-metrics-vs-rudderstack-mcp.md)
- [Mostly Good Metrics vs Userpilot](https://www.anchorterminal.com/compare/mostly-good-metrics-vs-userpilot.md)
- [Mostly Good Metrics vs Woopra](https://www.anchorterminal.com/compare/mostly-good-metrics-vs-woopra.md)
- [OpenPanel vs Statsig](https://www.anchorterminal.com/compare/openpanel-vs-statsig.md)
- [Pendo vs Statsig](https://www.anchorterminal.com/compare/pendo-vs-statsig.md)
- [PostHog vs Statsig](https://www.anchorterminal.com/compare/posthog-vs-statsig.md)
- [Statsig vs Userpilot](https://www.anchorterminal.com/compare/statsig-vs-userpilot.md)
- [Statsig vs Woopra](https://www.anchorterminal.com/compare/statsig-vs-woopra.md)
- [Heap vs Mostly Good Metrics](https://www.anchorterminal.com/compare/heap-vs-mostly-good-metrics.md)
- [Heap vs Statsig](https://www.anchorterminal.com/compare/heap-vs-statsig.md)
- [RudderStack MCP vs Statsig](https://www.anchorterminal.com/compare/rudderstack-mcp-vs-statsig.md)
- [Flagsmith vs Statsig](https://www.anchorterminal.com/compare/flagsmith-vs-statsig.md)
- [Harness Feature Management & Experimentation vs Statsig](https://www.anchorterminal.com/compare/harness-fme-vs-statsig.md)
- [LaunchDarkly vs Statsig](https://www.anchorterminal.com/compare/launchdarkly-vs-statsig.md)
- [Flagsmith vs Mostly Good Metrics](https://www.anchorterminal.com/compare/flagsmith-vs-mostly-good-metrics.md)
- [GrowthBook vs Mostly Good Metrics](https://www.anchorterminal.com/compare/growthbook-vs-mostly-good-metrics.md)
- [GrowthBook vs Statsig](https://www.anchorterminal.com/compare/growthbook-vs-statsig.md)
- [Harness Feature Management & Experimentation vs Mostly Good Metrics](https://www.anchorterminal.com/compare/harness-fme-vs-mostly-good-metrics.md)
- [LaunchDarkly vs Mostly Good Metrics](https://www.anchorterminal.com/compare/launchdarkly-vs-mostly-good-metrics.md)
- [Optimizely Experimentation vs Statsig](https://www.anchorterminal.com/compare/optimizely-vs-statsig.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp