{ "data": { "a": { "slug": "harness-fme", "name": "Harness Feature Management \u0026 Experimentation", "vendor": "Harness Inc.", "vendorUrl": "https://www.harness.io", "kind": "http-api", "category": "product-analytics", "summary": "Harness Feature Management \u0026 Experimentation (FME), formerly Split, manages feature flags, targeting, metrics and experiments. Agents reach it through the Admin API at api.split.io and the FME toolset of the Harness MCP server.", "url": "https://www.anchorterminal.com/tools/harness-fme", "markdownUrl": "https://www.anchorterminal.com/tools/harness-fme.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/harness-fme.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/harness-fme.json", "dns": "harness-fme.grade.anchorterminal.com", "repo": "https://github.com/harness/mcp-server", "transports": [ "http", "stdio", "streamable-http" ], "remoteUrl": "https://mcp.harness.io/mcp", "packages": [ { "registry": "npm", "name": "harness-mcp-v2" } ], "auth": "mixed", "authNotes": "The Admin API takes an Admin API key as a Bearer token, or a Harness personal access token (PAT) or service account token (SAT) in `x-api-key`. Admin keys carry fixed roles that can be combined and cannot be edited after creation, and a key cannot create another with more roles. The local MCP server reads HARNESS_API_KEY. The hosted MCP endpoint uses Harness Platform OAuth and must be enabled per account by Harness Support.", "pricing": "freemium", "pricingNotes": "An FME Free Plan is enabled from inside a Harness account; its limits are not published. The Enterprise plan and FME pricing are by quotation through sales. No FME prices appear on harness.io/pricing.", "priceSummary": "Freemium", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the FME docs, the Split API reference or harness.io/pricing (checked 2026-11-06).", "endpoints": [] }, "toolCount": 11, "popularity": { "githubStars": null, "npmWeekly": 8800, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://developer.harness.io/feature-management-experimentation/feature-management-and-experimentation-documentation", "llmsTxt": "https://developer.harness.io/llms.txt", "capabilities": [ "analytics.flags", "analytics.experiments", "analytics.events" ], "tags": [ "official", "hosted", "mcp", "remote-mcp", "oauth", "llms-txt", "free-tier", "sales-led", "status-page", "soc2", "iso27001", "typescript", "python", "cli", "closed-source" ], "lastRelease": "2026-11-04", "graded": true, "anchor": { "graded": true, "score": 69.2, "grade": "B", "agentReady": false, "rank": 257, "ranked": true, "rankOf": 1486, "categoryRank": 4, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 83, "maintenance": 81, "payments": 15, "reliability": 80, "schema": 71, "security": 79, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "Harness FME, formerly Split, gives agents 11 consolidated MCP tools with an FME-only toolset, a read-only switch and confirmation on writes, over an Admin API with documented limits and role-scoped keys. FME prices are not published, the free plan's limits are unstated, and the hosted MCP endpoint must be enabled by Harness Support.", "bestFor": "Teams already on Harness, or Split customers, who want agents to inspect and change flags and segments with guard rails.", "strengths": [ "11 generic MCP tools with `--toolsets=fme`, readOnlyHint on reads and elicitation before writes", "HARNESS_READ_ONLY blocks every create, update, delete and execute call", "Admin API keys with fixed, combinable roles, plus Harness PATs and SATs", "Documented rate limit with remaining and reset headers, and automatic backoff in the MCP server", "SOC 2 Type II, ISO 27001 and FedRAMP 20x, with FME audit logs and MCP audit sinks" ], "weaknesses": [ "No FME prices are published; Enterprise is by quotation and free plan limits are unstated", "The hosted MCP endpoint must be enabled per account by Harness Support", "The FME MCP docs page still describes building a Go binary, unlike the current npm package", "About 20 Admin API requests per 10 seconds per organisation, which large lists can hit", "No public OpenAPI file for the Admin API was found" ], "agentNotes": [ "Start the MCP server with `--toolsets=fme` so only FME resource types load", "Call `harness_describe(resource_type='fme_feature_flag')` before a create or update to see the fields", "Filter fme_feature_flag lists by name, tags or rollout status rather than listing every flag", "Set HARNESS_READ_ONLY for analysis tasks; leave confirmation on for kill, restore and delete", "On 429, wait at least the larger X-RateLimit-Reset-Seconds value before retrying" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 69.2 } ], "editorialScores": { "ergonomics": 83, "maintenance": 81, "payments": 15, "reliability": 80, "schema": 71, "security": 79, "transparency": 60 }, "provenanceScore": 61, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npx harness-mcp-v2@latest", "config": { "mcpServers": { "harness": { "args": [ "harness-mcp-v2@latest", "--toolsets=fme" ], "command": "npx", "env": { "HARNESS_API_KEY": "pat.xxx" } } } } }, "letme": { "capability": "https://letme.dev/analytics.flags", "tool": "https://letme.dev/harness-fme" }, "area": "business", "provenance": { "legalEntity": "Harness Inc.", "domain": "harness.io", "domainRegistered": "", "endpointOnVendorDomain": false, "terms": "https://www.harness.io/legal/subscription-terms", "privacy": "https://www.harness.io/legal/privacy", "statusPage": "https://status.harness.io", "changelog": "https://github.com/harness/mcp-server/releases", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The Admin API is on api.split.io, the former Split domain, and the hosted MCP endpoint on mcp.harness.io.", "The privacy statement names Harness Inc. as controller and Harness France SAS as EU representative. Its header says last updated 23 October 2026 and its body says version of 14 October 2026.", "developer.harness.io/robots.txt allows all and carries Content-Signal ai-train=yes, search=yes, ai-input=yes. docs.split.io allows all but edit and login paths.", "www.harness.io/.well-known/security.txt answered with an invalid-request page. The security page gives security@harness.io and a private bug bounty on request.", "RDAP gave no registration date for harness.io." ], "score": 61 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/harness-fme.json", "live": { "slug": "harness-fme", "probe": { "target": "https://mcp.harness.io/mcp", "method": "get", "lastAt": "2026-11-07T18:20:29.454967067Z", "lastOk": true, "lastStatus": 401, "lastMs": 211, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 195, "p95ms24h": 280, "samples24h": 200, "samples30d": 200, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://status.harness.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T18:21:14.597545686Z" }, "versions": [ { "registry": "github", "name": "harness/mcp-server", "version": "v3.2.40", "released": "2026-11-05", "seenAt": "2026-11-06T23:32:13.419387707Z" }, { "registry": "npm", "name": "harness-mcp-v2", "version": "3.2.40", "seenAt": "2026-11-06T23:32:12.430886041Z" } ], "githubStars": 112, "npmWeekly": 8800, "securityTxt": { "url": "https://harness.io/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:19.957252225Z" }, "llmsTxt": { "url": "https://developer.harness.io/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:41.749004752Z" }, "pages": [ { "url": "https://www.harness.io/legal/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:29:30.551687912Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "b15935b42065" }, { "url": "https://www.harness.io/legal/subscription-terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:29:35.70684084Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "871b29e12dd4" } ], "updatedAt": "2026-11-07T18:21:14.597545686Z" } }, "answer": "Harness Feature Management \u0026 Experimentation scores 69.2 (B) on agent readiness against Mostly Good Metrics's 41.7 (E), and leads in 6 of 7 scored categories. Mostly Good Metrics leads on payments \u0026 pricing.", "b": { "slug": "mostly-good-metrics", "name": "Mostly Good Metrics", "vendor": "Mostly Good Metrics", "vendorUrl": "https://mostlygoodmetrics.com", "kind": "http-api", "category": "product-analytics", "summary": "Mostly Good Metrics is a product analytics service in public beta for indie developers and small teams. Apps send events through five SDKs or an HTTP API, and agents query funnels, retention and experiments through a hosted MCP server.", "url": "https://www.anchorterminal.com/tools/mostly-good-metrics", "markdownUrl": "https://www.anchorterminal.com/tools/mostly-good-metrics.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/mostly-good-metrics.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/mostly-good-metrics.json", "dns": "mostly-good-metrics.grade.anchorterminal.com", "repo": "https://github.com/Mostly-Good-Metrics", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://app.mostlygoodmetrics.com/mcp", "packages": [ { "registry": "npm", "name": "@mostly-good-metrics/javascript" }, { "registry": "npm", "name": "@mostly-good-metrics/react-native" } ], "auth": "mixed", "authNotes": "The MCP server and the `mgm` CLI use browser OAuth 2.0 with PKCE (S256) and dynamic client registration; the advertised scopes are mcp:tools plus support and newsletter scopes. Event ingestion uses a project API key as a Bearer token, which can be pinned to web origins, Apple bundle IDs or Android package names. Keys are created in the dashboard, the CLI or through MCP tools.", "pricing": "freemium", "pricingNotes": "Free plan at $0 with 50,000 to 100,000 events a month and no card. Starter $9 a month ($90 a year) for 500,000 events and Pro $29 a month ($290 a year) for 5,000,000, both quoted as lifetime beta prices against $12 and $49. Enterprise has unlimited ingestion.", "priceSummary": "$9 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs or on the pricing section of the home page (checked 2026-11-06).", "endpoints": [] }, "toolCount": 53, "popularity": { "githubStars": null, "npmWeekly": 81, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.mostlygoodmetrics.com", "capabilities": [ "analytics.query", "analytics.funnels", "analytics.events", "analytics.experiments" ], "tags": [ "hosted", "mcp", "remote-mcp", "oauth", "free-tier", "no-card", "beta", "closed-source", "typescript", "cli" ], "lastRelease": "2026-10-16", "graded": true, "anchor": { "graded": true, "score": 41.7, "grade": "E", "agentReady": false, "rank": 1277, "ranked": true, "rankOf": 1486, "categoryRank": 17, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 49, "maintenance": 74, "payments": 30, "reliability": 29, "schema": 49, "security": 33, "transparency": 45 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-06" }, "negative": 0, "verdict": "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.", "bestFor": "Indie and small-team apps that want simple funnels and retention an agent can query.", "strengths": [ "Hosted MCP server with OAuth, PKCE and dynamic client registration; no API key to copy", "execute_funnel, execute_retention and execute_query accept inline definitions without saving anything", "query_metrics runs 1 to 10 aggregate queries in one call with per-item results", "Free plan with no card, and paid plans from $9 a month", "Ingestion keys can be pinned to web origins and app bundle IDs" ], "weaknesses": [ "Public beta run by one developer, with no named legal entity in the terms", "No status page, SLA, security.txt or disclosure policy found", "53 MCP tools load at once and one scope grants all of them, including deletes and key revocation", "No OpenAPI file or llms.txt", "The CLI is installed from source because it isn't on npm yet" ], "agentNotes": [ "Use query_metrics for several aggregate questions instead of repeated execute_query calls", "Pass inline definitions to execute_funnel and execute_retention rather than creating saved objects", "Confirm with the user before delete, revoke_api_key or stop_experiment calls, since the server doesn't ask", "Start a fresh agent session after connecting, since a running client may not reload the tool list", "On 429 from ingestion, wait for Retry-After before resending events" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 41.7 } ], "editorialScores": { "ergonomics": 49, "maintenance": 74, "payments": 30, "reliability": 29, "schema": 49, "security": 33, "transparency": 51 }, "provenanceScore": 39, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "claudeCode": "claude mcp add --transport http mgm https://app.mostlygoodmetrics.com/mcp", "config": { "mcpServers": { "mgm": { "url": "https://app.mostlygoodmetrics.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/analytics.query", "tool": "https://letme.dev/mostly-good-metrics" }, "area": "business", "unitPrices": [ { "item": "Starter plan", "unit": "month", "usd": 9, "note": "500,000 events a month, lifetime beta price" }, { "item": "Pro plan", "unit": "month", "usd": 29, "note": "5,000,000 events a month, lifetime beta price" } ], "provenance": { "legalEntity": "", "domain": "mostlygoodmetrics.com", "domainRegistered": "2025-12-05", "endpointOnVendorDomain": true, "terms": "https://mostlygoodmetrics.com/terms", "privacy": "https://mostlygoodmetrics.com/privacy", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The terms and privacy policy, both last updated December 2025, name only Mostly Good Metrics and give no legal entity, address or governing law.", "mostlygoodmetrics.com/robots.txt has every rule commented out; docs.mostlygoodmetrics.com has no robots.txt.", "/.well-known/security.txt returned 404 and no status page was found.", "RDAP gives mostlygoodmetrics.com a registration date of 5 December 2025." ], "score": 39 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/mostly-good-metrics.json", "live": { "slug": "mostly-good-metrics", "probe": { "target": "https://app.mostlygoodmetrics.com/mcp", "method": "get", "lastAt": "2026-11-07T18:20:40.455487214Z", "lastOk": true, "lastStatus": 401, "lastMs": 220, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 167, "p95ms24h": 298, "samples24h": 200, "samples30d": 200, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "versions": [ { "registry": "npm", "name": "@mostly-good-metrics/javascript", "version": "0.13.1", "seenAt": "2026-11-06T23:47:33.682933227Z" }, { "registry": "npm", "name": "@mostly-good-metrics/react-native", "version": "0.9.1", "seenAt": "2026-11-06T23:47:34.884784704Z" } ], "npmWeekly": 81, "securityTxt": { "url": "https://mostlygoodmetrics.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T15:59:38.90553607Z" }, "pages": [ { "url": "https://mostlygoodmetrics.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:14:39.017388202Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "f43e747ad9a3" }, { "url": "https://mostlygoodmetrics.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:14:41.227658165Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "99ed64144abf" } ], "mcpTools": { "url": "https://app.mostlygoodmetrics.com/mcp", "checkedAt": "2026-11-07T01:46:16.716952564Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:46:16.716952564Z" }, "updatedAt": "2026-11-07T18:20:40.455487214Z" } }, "edges": [ { "by": 51, "category": "reliability", "leads": "harness-fme", "name": "Reliability", "reasons": { "a": "Graded on the hosted FME Admin API with the hosted lines. Statuspage at status.harness.io with an FME component among 196 (20). In the 90 days from 8 August, two FME incidents: API write operations returned 499 errors for 30 minutes on 20 August (minor) and the FME user interface was unavailable for 15 minutes on 23 August (major, interface only; flag evaluation was unaffected per the post). No API outage of an hour or more (20 of 30). About 20 Admin API requests per 10 seconds per organisation and per IP, documented on the MCP page (15). 429 responses carry remaining and reset headers with guidance to wait for the larger reset, and the MCP server backs off and retries three times (15). No SLA was found on harness.io/pricing or the FME docs (0). FME is generally available and the MCP server is at 3.2.40 (10). 20+20+15+15+0+10 = 80.", "b": "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." }, "scores": { "a": 80, "b": 29 } }, { "by": 46, "category": "security", "leads": "harness-fme", "name": "Security \u0026 auth", "reasons": { "a": "Admin API keys with combinable roles that can't be widened after creation, Harness PATs and SATs for central management, and Harness Platform OAuth on the hosted MCP endpoint. Credentials travel in headers (28 of 30). HARNESS_READ_ONLY removes every write, writes go through elicitation with a risk threshold for auto-approval, and FME change requests add approval for flag changes (19 of 20). No prompt-injection guidance; the tools return flag names, descriptions and rule data written by people (3 of 15). FME admin, environment and object audit logs, plus structured MCP audit events to file, webhook or OpenTelemetry sinks (13 of 15). SOC 1 and SOC 2 Type II, ISO 27001, 27017 and 27018, FedRAMP 20x, a security@harness.io disclosure route with a 24-hour response, a private bug bounty on request and annual external penetration tests. No security.txt (16 of 20). 28+19+3+13+16 = 79.", "b": "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." }, "scores": { "a": 79, "b": 33 } }, { "by": 34, "category": "ergonomics", "leads": "harness-fme", "name": "Agent ergonomics", "reasons": { "a": "11 consolidated tools, and `--toolsets=fme` narrows the server to FME (25). Flag lists filter server-side by name, tag and rollout status, and the Admin API paginates with markerLimit (17 of 20). Documented status codes, 429 headers, and a harness_diagnose tool. Error bodies aren't documented per endpoint (14 of 20). harness_list and harness_get carry readOnlyHint, write tools ask for confirmation by elicitation, and harness_delete is marked destructive. No idempotency keys (15 of 20). Two required settings (API key, optional org and project, account ID read from the token); a Python Admin API wrapper and CLI, and SDKs in more than a dozen languages for evaluation (12 of 15). 25+17+14+15+12 = 83.", "b": "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." }, "scores": { "a": 83, "b": 49 } }, { "by": 22, "category": "schema", "leads": "harness-fme", "name": "Schema \u0026 documentation", "reasons": { "a": "No public OpenAPI file for the Admin API was found; the reference is a ReadMe site with a Postman collection. The MCP server's 11 tools have typed inputs, and harness_describe returns each FME resource's fields (18 of 25). llms.txt on both developer.harness.io and docs.split.io, and every page as Markdown with `.md` (10). The README describes each tool and when writes ask for confirmation; resource details sit behind harness_describe rather than in the tool text (13 of 20). The generic tools take a resource_type string and a body, so per-resource constraints aren't in the schema (8 of 15). An error-code page lists 400, 401, 402, 403, 404, 409 and 429 with causes, and docs carry curl examples (10 of 15). Tagged MCP releases and dated SDK versioning policy; the Admin API has v1 and v2 paths and deprecation notices for Split-era endpoints (12 of 15). 18+10+13+8+10+12 = 71.", "b": "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." }, "scores": { "a": 71, "b": 49 } }, { "by": 16, "category": "transparency", "leads": "harness-fme", "name": "Transparency \u0026 trust", "reasons": { "a": "A closed service under Harness's subscription terms; the MCP server is MIT (18 of 30). The privacy statement covers website and sales data and defers customer data to the customer agreement and a published DPA; retention periods for customer data weren't found (18 of 30). A versioning policy for SDKs with support windows, and Split-era API endpoints marked deprecated with migration guides (14 of 20). Sub-processors are on the trust centre, which we didn't read, and the security page doesn't name data locations (10 of 20). 18+18+14+10 = 60.", "b": "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." }, "scores": { "a": 61, "b": 45 } }, { "by": 15, "category": "payments", "leads": "mostly-good-metrics", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). No FME prices are published; harness.io/pricing lists FME only under Enterprise, priced by quotation (0). The docs describe a Start FME Free Plan step inside a Harness account; its limits and whether a card is needed aren't stated (15 of 20). A person signs up for Harness in a browser and creates a key or token (0). 0+0+15+0 = 15.", "b": "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." }, "scores": { "a": 15, "b": 30 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Harness Inc.", "b": "Mostly Good Metrics", "name": "Vendor" }, { "a": "https://mcp.harness.io/mcp", "b": "https://app.mostlygoodmetrics.com/mcp", "name": "Hosted endpoint" }, { "a": "HTTP, stdio, Streamable HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "11", "b": "53", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-11-04", "b": "2026-10-16", "name": "Last release" }, { "a": "no date given", "b": "2025-12-01", "name": "Terms last updated" }, { "a": "no date given", "b": "2025-12-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": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "8.8k npm/wk", "b": "81 npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Harness Feature Management \u0026 Experimentation scores 69.2 (B) on agent readiness against Mostly Good Metrics's 41.7 (E), and leads in 6 of 7 scored categories. Mostly Good Metrics leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Harness Feature Management \u0026 Experimentation or Mostly Good Metrics?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Harness Feature Management \u0026 Experimentation and Mostly Good Metrics need an API key?" }, { "answer": "Yes. Harness Feature Management \u0026 Experimentation has a hosted endpoint at https://mcp.harness.io/mcp and Mostly Good Metrics at https://app.mostlygoodmetrics.com/mcp.", "question": "Can an agent call Harness Feature Management \u0026 Experimentation and Mostly Good Metrics without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 80 against 29", "Schema \u0026 documentation, 71 against 49", "Agent ergonomics, 83 against 49", "Security \u0026 auth, 79 against 33", "Maintenance \u0026 community, 81 against 74", "Transparency \u0026 trust, 61 against 45" ], "also": [ "Runs on your own machine" ], "goodFor": "Teams already on Harness, or Split customers, who want agents to inspect and change flags and segments with guard rails.", "slug": "harness-fme", "watchFor": "No FME prices are published; Enterprise is by quotation and free plan limits are unstated" }, { "aheadOn": [ "Payments \u0026 pricing, 30 against 15" ], "also": [ "Free to start without a card" ], "goodFor": "Indie and small-team apps that want simple funnels and retention an agent can query.", "slug": "mostly-good-metrics", "watchFor": "Public beta run by one developer, with no named legal entity in the terms" } ], "history": null, "job": { "capability": "analytics.experiments", "name": "Feature flags and experiments" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amplitude-vs-mostly-good-metrics.json", "title": "Amplitude vs Mostly Good Metrics", "url": "https://www.anchorterminal.com/compare/amplitude-vs-mostly-good-metrics" }, { "json": "https://www.anchorterminal.com/compare/basedash-mcp-vs-mostly-good-metrics.json", "title": "Basedash MCP vs Mostly Good Metrics", "url": "https://www.anchorterminal.com/compare/basedash-mcp-vs-mostly-good-metrics" }, { "json": "https://www.anchorterminal.com/compare/countly-vs-mostly-good-metrics.json", "title": "Countly vs Mostly Good Metrics", "url": "https://www.anchorterminal.com/compare/countly-vs-mostly-good-metrics" }, { "json": "https://www.anchorterminal.com/compare/fullstory-vs-mostly-good-metrics.json", "title": "Fullstory vs Mostly Good Metrics", "url": "https://www.anchorterminal.com/compare/fullstory-vs-mostly-good-metrics" }, { "json": "https://www.anchorterminal.com/compare/matomo-vs-mostly-good-metrics.json", "title": "Matomo vs Mostly Good Metrics", "url": "https://www.anchorterminal.com/compare/matomo-vs-mostly-good-metrics" }, { "json": "https://www.anchorterminal.com/compare/mixpanel-vs-mostly-good-metrics.json", "title": "Mixpanel vs Mostly Good Metrics", "url": "https://www.anchorterminal.com/compare/mixpanel-vs-mostly-good-metrics" }, { "json": "https://www.anchorterminal.com/compare/mostly-good-metrics-vs-openpanel.json", "title": "Mostly Good Metrics vs OpenPanel", "url": "https://www.anchorterminal.com/compare/mostly-good-metrics-vs-openpanel" }, { "json": "https://www.anchorterminal.com/compare/mostly-good-metrics-vs-optimizely.json", "title": "Mostly Good Metrics vs Optimizely Experimentation", "url": "https://www.anchorterminal.com/compare/mostly-good-metrics-vs-optimizely" }, { "json": "https://www.anchorterminal.com/compare/mostly-good-metrics-vs-pendo.json", "title": "Mostly Good Metrics vs Pendo", "url": "https://www.anchorterminal.com/compare/mostly-good-metrics-vs-pendo" }, { "json": "https://www.anchorterminal.com/compare/mostly-good-metrics-vs-posthog.json", "title": "Mostly Good Metrics vs PostHog", "url": "https://www.anchorterminal.com/compare/mostly-good-metrics-vs-posthog" }, { "json": "https://www.anchorterminal.com/compare/mostly-good-metrics-vs-statsig.json", "title": "Mostly Good Metrics vs Statsig", "url": "https://www.anchorterminal.com/compare/mostly-good-metrics-vs-statsig" }, { "json": "https://www.anchorterminal.com/compare/mostly-good-metrics-vs-userpilot.json", "title": "Mostly Good Metrics vs Userpilot", "url": "https://www.anchorterminal.com/compare/mostly-good-metrics-vs-userpilot" }, { "json": "https://www.anchorterminal.com/compare/mostly-good-metrics-vs-woopra.json", "title": "Mostly Good Metrics vs Woopra", "url": "https://www.anchorterminal.com/compare/mostly-good-metrics-vs-woopra" }, { "json": "https://www.anchorterminal.com/compare/amplitude-vs-harness-fme.json", "title": "Amplitude vs Harness Feature Management \u0026 Experimentation", "url": "https://www.anchorterminal.com/compare/amplitude-vs-harness-fme" }, { "json": "https://www.anchorterminal.com/compare/countly-vs-harness-fme.json", "title": "Countly vs Harness Feature Management \u0026 Experimentation", "url": "https://www.anchorterminal.com/compare/countly-vs-harness-fme" }, { "json": "https://www.anchorterminal.com/compare/flagsmith-vs-harness-fme.json", "title": "Flagsmith vs Harness Feature Management \u0026 Experimentation", "url": "https://www.anchorterminal.com/compare/flagsmith-vs-harness-fme" }, { "json": "https://www.anchorterminal.com/compare/harness-fme-vs-launchdarkly.json", "title": "Harness Feature Management \u0026 Experimentation vs LaunchDarkly", "url": "https://www.anchorterminal.com/compare/harness-fme-vs-launchdarkly" }, { "json": "https://www.anchorterminal.com/compare/harness-fme-vs-mixpanel.json", "title": "Harness Feature Management \u0026 Experimentation vs Mixpanel", "url": "https://www.anchorterminal.com/compare/harness-fme-vs-mixpanel" }, { "json": "https://www.anchorterminal.com/compare/harness-fme-vs-optimizely.json", "title": "Harness Feature Management \u0026 Experimentation vs Optimizely Experimentation", "url": "https://www.anchorterminal.com/compare/harness-fme-vs-optimizely" }, { "json": "https://www.anchorterminal.com/compare/harness-fme-vs-posthog.json", "title": "Harness Feature Management \u0026 Experimentation vs PostHog", "url": "https://www.anchorterminal.com/compare/harness-fme-vs-posthog" }, { "json": "https://www.anchorterminal.com/compare/harness-fme-vs-statsig.json", "title": "Harness Feature Management \u0026 Experimentation vs Statsig", "url": "https://www.anchorterminal.com/compare/harness-fme-vs-statsig" }, { "json": "https://www.anchorterminal.com/compare/fullstory-vs-harness-fme.json", "title": "Fullstory vs Harness Feature Management \u0026 Experimentation", "url": "https://www.anchorterminal.com/compare/fullstory-vs-harness-fme" }, { "json": "https://www.anchorterminal.com/compare/harness-fme-vs-heap.json", "title": "Harness Feature Management \u0026 Experimentation vs Heap", "url": "https://www.anchorterminal.com/compare/harness-fme-vs-heap" }, { "json": "https://www.anchorterminal.com/compare/harness-fme-vs-openpanel.json", "title": "Harness Feature Management \u0026 Experimentation vs OpenPanel", "url": "https://www.anchorterminal.com/compare/harness-fme-vs-openpanel" }, { "json": "https://www.anchorterminal.com/compare/harness-fme-vs-woopra.json", "title": "Harness Feature Management \u0026 Experimentation vs Woopra", "url": "https://www.anchorterminal.com/compare/harness-fme-vs-woopra" }, { "json": "https://www.anchorterminal.com/compare/heap-vs-mostly-good-metrics.json", "title": "Heap vs Mostly Good Metrics", "url": "https://www.anchorterminal.com/compare/heap-vs-mostly-good-metrics" }, { "json": "https://www.anchorterminal.com/compare/flagsmith-vs-mostly-good-metrics.json", "title": "Flagsmith vs Mostly Good Metrics", "url": "https://www.anchorterminal.com/compare/flagsmith-vs-mostly-good-metrics" }, { "json": "https://www.anchorterminal.com/compare/growthbook-vs-harness-fme.json", "title": "GrowthBook vs Harness Feature Management \u0026 Experimentation", "url": "https://www.anchorterminal.com/compare/growthbook-vs-harness-fme" }, { "json": "https://www.anchorterminal.com/compare/growthbook-vs-mostly-good-metrics.json", "title": "GrowthBook vs Mostly Good Metrics", "url": "https://www.anchorterminal.com/compare/growthbook-vs-mostly-good-metrics" }, { "json": "https://www.anchorterminal.com/compare/harness-fme-vs-matomo.json", "title": "Harness Feature Management \u0026 Experimentation vs Matomo", "url": "https://www.anchorterminal.com/compare/harness-fme-vs-matomo" }, { "json": "https://www.anchorterminal.com/compare/launchdarkly-vs-mostly-good-metrics.json", "title": "LaunchDarkly vs Mostly Good Metrics", "url": "https://www.anchorterminal.com/compare/launchdarkly-vs-mostly-good-metrics" } ], "panel": null, "scores": [ { "by": 51, "edge": "harness-fme", "harness-fme": 80, "key": "reliability", "mostly-good-metrics": 29, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 22, "edge": "harness-fme", "harness-fme": 71, "key": "schema", "mostly-good-metrics": 49, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 34, "edge": "harness-fme", "harness-fme": 83, "key": "ergonomics", "mostly-good-metrics": 49, "name": "Agent ergonomics", "weight": 13 }, { "by": 46, "edge": "harness-fme", "harness-fme": 79, "key": "security", "mostly-good-metrics": 33, "name": "Security \u0026 auth", "weight": 14 }, { "by": 15, "edge": "mostly-good-metrics", "harness-fme": 15, "key": "payments", "mostly-good-metrics": 30, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 7, "edge": "harness-fme", "harness-fme": 81, "key": "maintenance", "mostly-good-metrics": 74, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 16, "edge": "harness-fme", "harness-fme": 61, "key": "transparency", "mostly-good-metrics": 45, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Harness Feature Management \u0026 Experimentation scores 69.2 (B) on agent readiness against Mostly Good Metrics's 41.7 (E), and leads in 6 of 7 scored categories. Mostly Good Metrics leads on payments \u0026 pricing. Both do feature flags and experiments.", "tasks": null, "tutorials": [], "verdicts": { "harness-fme": "Harness FME, formerly Split, gives agents 11 consolidated MCP tools with an FME-only toolset, a read-only switch and confirmation on writes, over an Admin API with documented limits and role-scoped keys. FME prices are not published, the free plan's limits are unstated, and the hosted MCP endpoint must be enabled by Harness Support.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/harness-fme-vs-mostly-good-metrics", "json": "https://www.anchorterminal.com/compare/harness-fme-vs-mostly-good-metrics.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/harness-fme-vs-mostly-good-metrics.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/harness-fme-vs-mostly-good-metrics.min.md" }, "markdown": "Harness Feature Management \u0026 Experimentation scores 69.2 (B) on agent readiness against Mostly Good Metrics's 41.7 (E), and leads in 6 of 7 scored categories. Mostly Good Metrics leads on payments \u0026 pricing. Both do feature flags and experiments.\n\n- Harness Feature Management \u0026 Experimentation: grade B, 69.2/100, rank #257 of 1486. Markdown https://www.anchorterminal.com/tools/harness-fme.md · JSON https://www.anchorterminal.com/api/v1/tools/harness-fme.json\n- Mostly Good Metrics: grade E, 41.7/100, rank #1277 of 1486. Markdown https://www.anchorterminal.com/tools/mostly-good-metrics.md · JSON https://www.anchorterminal.com/api/v1/tools/mostly-good-metrics.json\n- Best product analytics and experimentation tools for AI agents: https://www.anchorterminal.com/best/product-analytics/index.md\n- All 153 product analytics comparisons: https://www.anchorterminal.com/compare/product-analytics/index.md\n\n## Which one, for what\n\n### Harness Feature Management \u0026 Experimentation (B)\n\nGood for: Teams already on Harness, or Split customers, who want agents to inspect and change flags and segments with guard rails.\n\nAhead on:\n- Reliability, 80 against 29\n- Schema \u0026 documentation, 71 against 49\n- Agent ergonomics, 83 against 49\n- Security \u0026 auth, 79 against 33\n- Maintenance \u0026 community, 81 against 74\n- Transparency \u0026 trust, 61 against 45\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: No FME prices are published; Enterprise is by quotation and free plan limits are unstated\n\n### Mostly Good Metrics (E)\n\nGood for: Indie and small-team apps that want simple funnels and retention an agent can query.\n\nAhead on:\n- Payments \u0026 pricing, 30 against 15\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: Public beta run by one developer, with no named legal entity in the terms\n\n\n## Why the edge\n\n### Reliability: Harness Feature Management \u0026 Experimentation +51\n\n- Harness Feature Management \u0026 Experimentation (80): Graded on the hosted FME Admin API with the hosted lines. Statuspage at status.harness.io with an FME component among 196 (20). In the 90 days from 8 August, two FME incidents: API write operations returned 499 errors for 30 minutes on 20 August (minor) and the FME user interface was unavailable for 15 minutes on 23 August (major, interface only; flag evaluation was unaffected per the post). No API outage of an hour or more (20 of 30). About 20 Admin API requests per 10 seconds per organisation and per IP, documented on the MCP page (15). 429 responses carry remaining and reset headers with guidance to wait for the larger reset, and the MCP server backs off and retries three times (15). No SLA was found on harness.io/pricing or the FME docs (0). FME is generally available and the MCP server is at 3.2.40 (10). 20+20+15+15+0+10 = 80.\n- 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.\n\n### Security \u0026 auth: Harness Feature Management \u0026 Experimentation +46\n\n- Harness Feature Management \u0026 Experimentation (79): Admin API keys with combinable roles that can't be widened after creation, Harness PATs and SATs for central management, and Harness Platform OAuth on the hosted MCP endpoint. Credentials travel in headers (28 of 30). HARNESS_READ_ONLY removes every write, writes go through elicitation with a risk threshold for auto-approval, and FME change requests add approval for flag changes (19 of 20). No prompt-injection guidance; the tools return flag names, descriptions and rule data written by people (3 of 15). FME admin, environment and object audit logs, plus structured MCP audit events to file, webhook or OpenTelemetry sinks (13 of 15). SOC 1 and SOC 2 Type II, ISO 27001, 27017 and 27018, FedRAMP 20x, a security@harness.io disclosure route with a 24-hour response, a private bug bounty on request and annual external penetration tests. No security.txt (16 of 20). 28+19+3+13+16 = 79.\n- 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.\n\n### Agent ergonomics: Harness Feature Management \u0026 Experimentation +34\n\n- Harness Feature Management \u0026 Experimentation (83): 11 consolidated tools, and `--toolsets=fme` narrows the server to FME (25). Flag lists filter server-side by name, tag and rollout status, and the Admin API paginates with markerLimit (17 of 20). Documented status codes, 429 headers, and a harness_diagnose tool. Error bodies aren't documented per endpoint (14 of 20). harness_list and harness_get carry readOnlyHint, write tools ask for confirmation by elicitation, and harness_delete is marked destructive. No idempotency keys (15 of 20). Two required settings (API key, optional org and project, account ID read from the token); a Python Admin API wrapper and CLI, and SDKs in more than a dozen languages for evaluation (12 of 15). 25+17+14+15+12 = 83.\n- 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.\n\n### Schema \u0026 documentation: Harness Feature Management \u0026 Experimentation +22\n\n- Harness Feature Management \u0026 Experimentation (71): No public OpenAPI file for the Admin API was found; the reference is a ReadMe site with a Postman collection. The MCP server's 11 tools have typed inputs, and harness_describe returns each FME resource's fields (18 of 25). llms.txt on both developer.harness.io and docs.split.io, and every page as Markdown with `.md` (10). The README describes each tool and when writes ask for confirmation; resource details sit behind harness_describe rather than in the tool text (13 of 20). The generic tools take a resource_type string and a body, so per-resource constraints aren't in the schema (8 of 15). An error-code page lists 400, 401, 402, 403, 404, 409 and 429 with causes, and docs carry curl examples (10 of 15). Tagged MCP releases and dated SDK versioning policy; the Admin API has v1 and v2 paths and deprecation notices for Split-era endpoints (12 of 15). 18+10+13+8+10+12 = 71.\n- 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.\n\n### Transparency \u0026 trust: Harness Feature Management \u0026 Experimentation +16\n\n- Harness Feature Management \u0026 Experimentation (61): A closed service under Harness's subscription terms; the MCP server is MIT (18 of 30). The privacy statement covers website and sales data and defers customer data to the customer agreement and a published DPA; retention periods for customer data weren't found (18 of 30). A versioning policy for SDKs with support windows, and Split-era API endpoints marked deprecated with migration guides (14 of 20). Sub-processors are on the trust centre, which we didn't read, and the security page doesn't name data locations (10 of 20). 18+18+14+10 = 60.\n- 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.\n\n### Payments \u0026 pricing: Mostly Good Metrics +15\n\n- Harness Feature Management \u0026 Experimentation (15): No x402, MPP or L402 (0). No FME prices are published; harness.io/pricing lists FME only under Enterprise, priced by quotation (0). The docs describe a Start FME Free Plan step inside a Harness account; its limits and whether a card is needed aren't stated (15 of 20). A person signs up for Harness in a browser and creates a key or token (0). 0+0+15+0 = 15.\n- 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.\n\n## Score by category\n\n| Category | Weight | Harness Feature Management \u0026 Experimentation | Mostly Good Metrics | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 80 | 29 | Harness Feature Management \u0026 Experimentation +51 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 71 | 49 | Harness Feature Management \u0026 Experimentation +22 |\n| Agent ergonomics | 13% (16.2 this run) | 83 | 49 | Harness Feature Management \u0026 Experimentation +34 |\n| Security \u0026 auth | 14% (17.5 this run) | 79 | 33 | Harness Feature Management \u0026 Experimentation +46 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 15 | 30 | Mostly Good Metrics +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 81 | 74 | Harness Feature Management \u0026 Experimentation +7 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 61 | 45 | Harness Feature Management \u0026 Experimentation +16 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **69.2 · B** | **41.7 · E** | |\n\n## Facts side by side\n\n| Fact | Harness Feature Management \u0026 Experimentation | Mostly Good Metrics |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Harness Inc. | Mostly Good Metrics |\n| Hosted endpoint | `https://mcp.harness.io/mcp` | `https://app.mostlygoodmetrics.com/mcp` |\n| Transports | HTTP, stdio, Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Tools exposed | 11 | 53 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2026-11-04 | 2026-10-16 |\n| Terms last updated | no date given | 2025-12-01 |\n| Privacy policy last updated | no date given | 2025-12-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 | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 8.8k npm/wk | 81 npm/wk |\n\n## Verdicts\n\n**Harness Feature Management \u0026 Experimentation.** Harness FME, formerly Split, gives agents 11 consolidated MCP tools with an FME-only toolset, a read-only switch and confirmation on writes, over an Admin API with documented limits and role-scoped keys. FME prices are not published, the free plan's limits are unstated, and the hosted MCP endpoint must be enabled by Harness Support.\n\n**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.\n\n## Before you call either\n\n### Harness Feature Management \u0026 Experimentation\n\n1. Start the MCP server with `--toolsets=fme` so only FME resource types load\n2. Call `harness_describe(resource_type='fme_feature_flag')` before a create or update to see the fields\n3. Filter fme_feature_flag lists by name, tags or rollout status rather than listing every flag\n4. Set HARNESS_READ_ONLY for analysis tasks; leave confirmation on for kill, restore and delete\n5. On 429, wait at least the larger X-RateLimit-Reset-Seconds value before retrying\n\n### Mostly Good Metrics\n\n1. Use query_metrics for several aggregate questions instead of repeated execute_query calls\n2. Pass inline definitions to execute_funnel and execute_retention rather than creating saved objects\n3. Confirm with the user before delete, revoke_api_key or stop_experiment calls, since the server doesn't ask\n4. Start a fresh agent session after connecting, since a running client may not reload the tool list\n5. On 429 from ingestion, wait for Retry-After before resending events\n\n## Questions\n\n### Which is better for AI agents, Harness Feature Management \u0026 Experimentation or Mostly Good Metrics?\n\nHarness Feature Management \u0026 Experimentation scores 69.2 (B) on agent readiness against Mostly Good Metrics's 41.7 (E), and leads in 6 of 7 scored categories. Mostly Good Metrics leads on payments \u0026 pricing.\n\n### Do Harness Feature Management \u0026 Experimentation and Mostly Good Metrics need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Harness Feature Management \u0026 Experimentation and Mostly Good Metrics without installing anything?\n\nYes. Harness Feature Management \u0026 Experimentation has a hosted endpoint at https://mcp.harness.io/mcp and Mostly Good Metrics at https://app.mostlygoodmetrics.com/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/harness-fme-vs-mostly-good-metrics.json, and with the fewest tokens: https://www.anchorterminal.com/compare/harness-fme-vs-mostly-good-metrics.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"harness-fme\", \"b\": \"mostly-good-metrics\"}`. From a terminal: `anchor compare harness-fme mostly-good-metrics`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/harness-fme.json and https://www.anchorterminal.com/api/v1/tools/mostly-good-metrics.json\n\n## Other comparisons with Harness Feature Management \u0026 Experimentation or Mostly Good Metrics\n\n- [Amplitude vs Mostly Good Metrics](https://www.anchorterminal.com/compare/amplitude-vs-mostly-good-metrics.md)\n- [Basedash MCP vs Mostly Good Metrics](https://www.anchorterminal.com/compare/basedash-mcp-vs-mostly-good-metrics.md)\n- [Countly vs Mostly Good Metrics](https://www.anchorterminal.com/compare/countly-vs-mostly-good-metrics.md)\n- [Fullstory vs Mostly Good Metrics](https://www.anchorterminal.com/compare/fullstory-vs-mostly-good-metrics.md)\n- [Matomo vs Mostly Good Metrics](https://www.anchorterminal.com/compare/matomo-vs-mostly-good-metrics.md)\n- [Mixpanel vs Mostly Good Metrics](https://www.anchorterminal.com/compare/mixpanel-vs-mostly-good-metrics.md)\n- [Mostly Good Metrics vs OpenPanel](https://www.anchorterminal.com/compare/mostly-good-metrics-vs-openpanel.md)\n- [Mostly Good Metrics vs Optimizely Experimentation](https://www.anchorterminal.com/compare/mostly-good-metrics-vs-optimizely.md)\n- [Mostly Good Metrics vs Pendo](https://www.anchorterminal.com/compare/mostly-good-metrics-vs-pendo.md)\n- [Mostly Good Metrics vs PostHog](https://www.anchorterminal.com/compare/mostly-good-metrics-vs-posthog.md)\n- [Mostly Good Metrics vs Statsig](https://www.anchorterminal.com/compare/mostly-good-metrics-vs-statsig.md)\n- [Mostly Good Metrics vs Userpilot](https://www.anchorterminal.com/compare/mostly-good-metrics-vs-userpilot.md)\n- [Mostly Good Metrics vs Woopra](https://www.anchorterminal.com/compare/mostly-good-metrics-vs-woopra.md)\n- [Amplitude vs Harness Feature Management \u0026 Experimentation](https://www.anchorterminal.com/compare/amplitude-vs-harness-fme.md)\n- [Countly vs Harness Feature Management \u0026 Experimentation](https://www.anchorterminal.com/compare/countly-vs-harness-fme.md)\n- [Flagsmith vs Harness Feature Management \u0026 Experimentation](https://www.anchorterminal.com/compare/flagsmith-vs-harness-fme.md)\n- [Harness Feature Management \u0026 Experimentation vs LaunchDarkly](https://www.anchorterminal.com/compare/harness-fme-vs-launchdarkly.md)\n- [Harness Feature Management \u0026 Experimentation vs Mixpanel](https://www.anchorterminal.com/compare/harness-fme-vs-mixpanel.md)\n- [Harness Feature Management \u0026 Experimentation vs Optimizely Experimentation](https://www.anchorterminal.com/compare/harness-fme-vs-optimizely.md)\n- [Harness Feature Management \u0026 Experimentation vs PostHog](https://www.anchorterminal.com/compare/harness-fme-vs-posthog.md)\n- [Harness Feature Management \u0026 Experimentation vs Statsig](https://www.anchorterminal.com/compare/harness-fme-vs-statsig.md)\n- [Fullstory vs Harness Feature Management \u0026 Experimentation](https://www.anchorterminal.com/compare/fullstory-vs-harness-fme.md)\n- [Harness Feature Management \u0026 Experimentation vs Heap](https://www.anchorterminal.com/compare/harness-fme-vs-heap.md)\n- [Harness Feature Management \u0026 Experimentation vs OpenPanel](https://www.anchorterminal.com/compare/harness-fme-vs-openpanel.md)\n- [Harness Feature Management \u0026 Experimentation vs Woopra](https://www.anchorterminal.com/compare/harness-fme-vs-woopra.md)\n- [Heap vs Mostly Good Metrics](https://www.anchorterminal.com/compare/heap-vs-mostly-good-metrics.md)\n- [Flagsmith vs Mostly Good Metrics](https://www.anchorterminal.com/compare/flagsmith-vs-mostly-good-metrics.md)\n- [GrowthBook vs Harness Feature Management \u0026 Experimentation](https://www.anchorterminal.com/compare/growthbook-vs-harness-fme.md)\n- [GrowthBook vs Mostly Good Metrics](https://www.anchorterminal.com/compare/growthbook-vs-mostly-good-metrics.md)\n- [Harness Feature Management \u0026 Experimentation vs Matomo](https://www.anchorterminal.com/compare/harness-fme-vs-matomo.md)\n- [LaunchDarkly vs Mostly Good Metrics](https://www.anchorterminal.com/compare/launchdarkly-vs-mostly-good-metrics.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Harness Feature Management \u0026 Experimentation vs Mostly Good Metrics", "url": "" } ], "description": "Harness Feature Management \u0026 Experimentation scores 69.2 (B) to Mostly Good Metrics's 41.7 (E) for feature flags and experiments. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Harness Feature Management \u0026 Experimentation B 69.2", "Mostly Good Metrics E 41.7", "scores" ], "h1": "Harness Feature Management \u0026 Experimentation vs Mostly Good Metrics", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/harness-fme-vs-mostly-good-metrics", "published": "2026-10-01", "section": "tools", "title": "Harness Feature Management \u0026 Experimentation vs Mostly Good Metrics", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/harness-fme-vs-mostly-good-metrics" }, "tokens": { "markdown": 5000, "slim": 2730 }, "version": 1 }