# Mostly Good Metrics vs Woopra (slim)

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

- Full: https://www.anchorterminal.com/compare/mostly-good-metrics-vs-woopra.md (~4,150 tokens) · this version ~1,930 tokens · JSON https://www.anchorterminal.com/compare/mostly-good-metrics-vs-woopra.json · canonical https://www.anchorterminal.com/compare/mostly-good-metrics-vs-woopra
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Woopra scores 44.4 (E) on agent readiness against Mostly Good Metrics's 41.7 (E), and leads in 2 of 7 scored categories. Mostly Good Metrics leads on security & auth and maintenance & community. Both do analytics queries.

- Mostly Good Metrics: E 41.7, rank #1295 of 1510 · https://www.anchorterminal.com/tools/mostly-good-metrics.min.md
- Woopra: E 44.4, rank #1219 of 1510 · https://www.anchorterminal.com/tools/woopra.min.md
- Mostly Good Metrics, good for Indie and small-team apps that want simple funnels and retention an agent can query. Ahead on Security & auth, 33 against 22; Maintenance & community, 74 against 9. Also Free to start without a card.
- Woopra, good for An agent that reads a company's existing Woopra reports, looks up or edits customer profiles, or exports raw sessions on a schedule. Ahead on Reliability, 80 against 29; Transparency & trust, 62 against 45.

| Category | Mostly Good Metrics | Woopra |
| --- | --- | --- |
| Reliability (16%) | 29 | 80 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 49 | 45 |
| Agent ergonomics (13%) | 49 | 45 |
| Security & auth (14%) | 33 | 22 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 74 | 9 |
| Transparency & trust (7%) | 45 | 62 |

| Fact (where they differ) | Mostly Good Metrics | Woopra |
| --- | --- | --- |
| Vendor | Mostly Good Metrics | Woopra, Inc. |
| Hosted endpoint | `https://app.mostlygoodmetrics.com/mcp` | `https://www.woopra.com/rest/3.10` |
| Transports | HTTP, Streamable HTTP | HTTP |
| Pricing | Freemium | Paid |
| Licence | none | Proprietary service under Woopra's terms of service. The browser tracker and the SDKs on GitHub are MIT, and the Node package is ISC |
| Tools exposed | 53 | none |
| llms.txt | no | yes |
| Last release | 2026-10-16 | 2026-03-16 |
| Terms last updated | 2025-12-01 | 2025-12-10 |
| Privacy policy last updated | 2025-12-01 | 2025-08-01 |
| Terms restrict automated access | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 81 npm/wk | 415 npm/wk |
| Agent reviews | none | 2.3/5 (4) |

Why the edge:
- Maintenance & community, Mostly Good Metrics +65: Mostly Good Metrics 74 (CLI v0.1.4 was tagged on 16 October 2026 (30). The JavaScript SDK released 0.12.0, 0.13.0 and 0.13.1 between 5 September and 2 October, and the Swift SDK 1.0.0 and 1.0.1 on 2 October (20). A closed service with no public changelog, support by email and GitHub repositories for the SDKs; issue activity wasn't read because the GitHub API refused us for its rate limit (6 of 25). Not in the official MCP registry; official SDKs in five languages are current (10 of 15). CI workflows on the SDK and CLI repositories (8 of 10). 30+20+6+10+8 = 74.); Woopra 9 (The newest dated change found is a commit to the browser tracker on 16 March 2026, and the REST intro page was last edited on 13 March 2026, both more than 180 days before the check (0). No releases or dated changelog entries in the last 90 days (0). No API changelog. Support is by email and in-app, and response times were not checked (3). The browser tracker's last tag is v5.3.0 from 2021, iOS and Android were last committed to in November 2024, and the Node, Python, Java and Rails SDKs in 2017 (4). The Node README carries a Travis CI badge and no current CI was found (2). Total 9.)
- Reliability, Woopra +51: 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.); Woopra 80 (Graded on the REST and HTTP tracking APIs with the hosted lines. Statuspage site at status.woopra.com with three components (20). Its history lists no incidents for August, September or October 2026, the three months shown (30). Limits published with numbers, 300 calls a minute, 600 an hour and 3,000 a day per project (15). A 429 status is documented and tracking calls answer 202 when queued, but no Retry-After, backoff guidance or idempotency key was found (5). No SLA found. The terms promise commercially reasonable efforts (0). The API is version 3.10 with no beta label (10). Total 80.)
- Transparency & trust, Woopra +17: 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.); Woopra 62 (Closed service with dated terms that cover the subscription, and MIT SDKs (15). The terms say the customer owns tracking data, and the pricing page states 24 months of retention. The privacy policy excludes end-user data, the DPA is sent only on request, and the GDPR page still cites Privacy Shield while the privacy policy cites the Data Privacy Framework (14). No deprecation policy or dated notices found (0). Nine sub-processors named in the terms with addresses and countries, eight in the USA and Hetzner in Germany. Where customer data is stored is not stated (16). Total 45.)
- Security & auth, Mostly Good Metrics +11: 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.); Woopra 22 (REST calls use per-user access keys sent by HTTP Basic, with no scopes or rotation guidance found. Tracking calls need only the project name by default, with an optional Secure Tracking secret. Docs examples still show `http://` tracking URLs (15 of 30). The pricing page states group and individual permission controls, but no read-only key or confirmation on `/profile/delete` was found (5). The API returns event and profile text that any caller who knows the project name can write, and no guidance on untrusted content was found (0). No audit log found in the docs (0). No security page, bug bounty or certification was found on the pages read, and security.txt timed out. The privacy policy states Data Privacy Framework certification (2). Total 22.)