# Mostly Good Metrics vs RudderStack MCP (slim)

> RudderStack MCP scores 54.7 (C) 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-rudderstack-mcp.md (~4,200 tokens) · this version ~2,180 tokens · JSON https://www.anchorterminal.com/compare/mostly-good-metrics-vs-rudderstack-mcp.json · canonical https://www.anchorterminal.com/compare/mostly-good-metrics-vs-rudderstack-mcp
- 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)

RudderStack MCP scores 54.7 (C) on agent readiness against Mostly Good Metrics's 41.7 (E), and leads in 6 of 7 scored categories. Both do analytics queries.

- Mostly Good Metrics: E 41.7, rank #1295 of 1510 · https://www.anchorterminal.com/tools/mostly-good-metrics.min.md
- RudderStack MCP: C 54.7, rank #901 of 1510 · https://www.anchorterminal.com/tools/rudderstack-mcp.min.md
- Mostly Good Metrics, good for Indie and small-team apps that want simple funnels and retention an agent can query. Also Free to start without a card.
- RudderStack MCP, good for Data teams on RudderStack who want an agent to find why events, syncs or transformations failed and fix the configuration. Ahead on Reliability, 45 against 29; Schema & documentation, 66 against 49; Security & auth, 62 against 33; Maintenance & community, 85 against 74; Transparency & trust, 51 against 45.

| Category | Mostly Good Metrics | RudderStack MCP |
| --- | --- | --- |
| Reliability (16%) | 29 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 49 | 66 |
| Agent ergonomics (13%) | 49 | 52 |
| Security & auth (14%) | 33 | 62 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 74 | 85 |
| Transparency & trust (7%) | 45 | 51 |

| Fact (where they differ) | Mostly Good Metrics | RudderStack MCP |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Mostly Good Metrics | RudderStack, Inc. |
| Hosted endpoint | `https://app.mostlygoodmetrics.com/mcp` | `https://mcp.rudderstack.com/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth |
| Licence | none | Proprietary service. The repository's MIT licence covers docs and metadata only |
| Tools exposed | 53 | 62 |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| MCP registry | not listed | `io.github.rudderlabs/rudderstack-mcp` |
| Last release | 2026-10-16 | none |
| Terms last updated | 2025-12-01 | not read yet |
| Privacy policy last updated | 2025-12-01 | not read yet |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 81 npm/wk | none |

Why the edge:
- Security & auth, RudderStack MCP +29: 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.); RudderStack MCP 62 (OAuth with PKCE and dynamic registration, scopes not published (22 of 30). Access classes, a read-only surface and confirmation advice for writes (16 of 20). Selected sensitive fields in event payloads and errors are redacted or hashed before they reach the model, but event payloads are still untrusted text (8 of 15). No audit log of MCP calls found (0). SOC 2 Type 2, HIPAA with a BAA, and a SECURITY.md with a private reporting address; no security.txt (404) (16 of 20). 22 + 16 + 8 + 0 + 16 = 62.)
- Schema & documentation, RudderStack MCP +17: 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.); RudderStack MCP 66 (The public repository's docs/tools.md lists 62 tools with an access class for each; JSON Schemas not read without a session (15 of 25). llms.txt (10). Every tool has a one-line purpose and a Read, Sensitive execution or Write class (15 of 20). Inputs not verifiable (5 of 15). Example prompts and a documented 'workspace_id is required' error (6 of 15). Versioned in the registry (0.43.1, 6 November) and dated release notes (15). 15 + 10 + 15 + 5 + 6 + 15 = 66.)
- Reliability, RudderStack MCP +16: 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.); RudderStack MCP 45 (Statuspage at status.rudderstack.com with regional components and none for MCP (15). Since August the history shows an EU ingestion issue, increased US latency, a Python transformations issue, free-tier processing delays and scheduled maintenance (20, minor incidents). No MCP rate limits found (0). No retry guidance for the MCP server found (0). No SLA found in the pages read (0). Not labelled beta (10). 15 + 20 + 0 + 0 + 0 + 10 = 45.)
- Maintenance & community, RudderStack MCP +11: 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.); RudderStack MCP 85 (Release notes dated 4 November 2026 and a registry version on 6 November (30). Many dated releases in 90 days (20). Public issue templates on the MCP repository, issues not read, plus release notes (10 of 25). Official registry entry io.github.rudderlabs/rudderstack-mcp and current official SDKs (15). A repository workflow publishes to the registry (10). 30 + 20 + 10 + 15 + 10 = 85. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.)
- Transparency & trust, RudderStack MCP +6: 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.); RudderStack MCP 51 (The server's source is closed; the repository's MIT licence covers only its docs and metadata. Terms in a master service agreement naming RudderStack, Inc. (15). Privacy policy read, retention given by purpose, not as periods (12 of 30). No deprecation policy for the MCP server (5 of 20). Subprocessors not found in the pages read (5 of 20). The MCP docs say live events, schemas, profile artifacts, transformation code and audit data stay within the workspace view. 15 + 12 + 5 + 5 = 37.)