{ "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": 258, "ranked": true, "rankOf": 1510, "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-07T19:22:10.85947707Z", "lastOk": true, "lastStatus": 401, "lastMs": 308, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 195, "p95ms24h": 285, "samples24h": 210, "samples30d": 210, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "vendorStatus": { "page": "https://status.harness.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T19:22:14.403533029Z" }, "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-07T19:22:10.85947707Z" } }, "answer": "LaunchDarkly scores 71.3 (BB) on agent readiness against Harness Feature Management \u0026 Experimentation's 69.2 (B), and leads in 4 of 7 scored categories. Harness Feature Management \u0026 Experimentation leads on reliability, agent ergonomics and security \u0026 auth.", "b": { "slug": "launchdarkly", "name": "LaunchDarkly", "vendor": "Catamorphic, Co. (dba LaunchDarkly)", "vendorUrl": "https://launchdarkly.com", "kind": "http-api", "category": "product-analytics", "summary": "LaunchDarkly is a hosted feature flag and experimentation platform from Catamorphic, Co., with observability and AI configuration products. Agents reach it through an official hosted MCP server with OAuth and a REST API with a public OpenAPI spec.", "url": "https://www.anchorterminal.com/tools/launchdarkly", "markdownUrl": "https://www.anchorterminal.com/tools/launchdarkly.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/launchdarkly.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/launchdarkly.json", "dns": "launchdarkly.grade.anchorterminal.com", "repo": "https://github.com/launchdarkly/mcp-server", "license": "Proprietary service under LaunchDarkly's terms. The local MCP server is MIT and the ldcli CLI is Apache-2.0", "transports": [ "http", "streamable-http", "stdio" ], "remoteUrl": "https://mcp.launchdarkly.com/mcp/launchdarkly", "packages": [ { "registry": "npm", "name": "@launchdarkly/mcp-server" }, { "registry": "npm", "name": "launchdarkly-api" }, { "registry": "pypi", "name": "launchdarkly-api" }, { "registry": "npm", "name": "@launchdarkly/node-server-sdk" }, { "registry": "pypi", "name": "launchdarkly-server-sdk" } ], "auth": "mixed", "authNotes": "Self-serve. The hosted MCP server uses OAuth with PKCE and dynamic client registration, with reader, writer and observability scopes, and acts with the role of the member who approves it. The REST API, the CLI and the local MCP server take an access token in the `Authorization` header. A signed-in member creates the token with a Reader, Writer, Admin or Owner role, and it is shown once. Custom roles and inline policies need a plan with custom roles, and service tokens need Enterprise. SDK keys cannot call the REST API.", "pricing": "freemium", "pricingNotes": "The Developer plan is free with no card and no seat charge, with 5 service connections, 1,000 client-side MAU, 100,000 experimentation MAU and 5,000 AI runs a month. Foundation has a 14-day trial, then bills by usage with no platform fee. Enterprise is custom. API and MCP calls are not billed (https://launchdarkly.com/pricing/, checked 2026-10-08).", "priceSummary": "$10 / mo", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs, the OpenAPI spec or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": 141, "popularity": { "githubStars": null, "npmWeekly": 3291956, "pypiWeekly": 2207524, "asOf": "2026-10-08" }, "docsUrl": "https://launchdarkly.com/docs/home/getting-started/mcp", "llmsTxt": "https://launchdarkly.com/docs/llms.txt", "openapi": "https://app.launchdarkly.com/api/v2/openapi.json", "capabilities": [ "analytics.flags", "analytics.experiments", "observability.logs", "observability.errors" ], "tags": [ "official", "hosted", "mcp", "oauth", "openapi", "llms-txt", "free-tier", "no-card", "eu-region", "status-page", "soc2", "cli", "typescript", "python" ], "lastRelease": "2026-10-27", "graded": true, "anchor": { "graded": true, "score": 71.3, "grade": "BB", "agentReady": true, "rank": 163, "ranked": true, "rankOf": 1510, "categoryRank": 2, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 69, "maintenance": 82, "payments": 40, "reliability": 74, "schema": 89, "security": 66, "transparency": 81 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": 0, "verdict": "LaunchDarkly suits agents that manage feature flags, rollouts and experiments. The hosted MCP server uses OAuth with dynamic client registration and marks its tools read-only or destructive, and the Developer plan is free without a card. The server lists 141 tools, numeric rate limits are unpublished, and every REST API version except 20240415 stops working on 31 December 2026.", "bestFor": "An agent that creates and targets feature flags, runs rollouts and experiments, reads experiment results and cleans up stale flags.", "strengths": [ "Public OpenAPI 3.0.3 spec with 401 operations, 399 of them described, with 1,853 examples and 429 documented on 287 operations", "Hosted MCP server with OAuth, PKCE, dynamic client registration, a revocation endpoint and reader, writer and observability scopes", "MCP tools cover experiment creation, iteration control and results, flag targeting, approval requests and flag removal readiness", "Developer plan is free with no card, unlimited seats, unlimited flags and 100,000 experimentation MAU a month", "Dated API versions set by header, with a written policy of 12 months' support after a new version" ], "weaknesses": [ "The hosted MCP server lists 141 tools, and no tool filter for it was found in the reviewed documentation", "The API docs say the numeric rate limits are not published and may change", "132 of 401 API operations are beta, need `LD-API-Version: beta` and may change without notice", "Every REST API version except 20240415 stops answering on 31 December 2026, announced on the status page on 25 August 2025", "Custom roles, inline token policies, service tokens and approvals need an Enterprise plan, and the hosted MCP server is absent from the EU and federal instances" ], "agentNotes": [ "Connect to https://mcp.launchdarkly.com/mcp/launchdarkly over streamable HTTP with OAuth. On the EU or federal instance run the local `@launchdarkly/mcp-server` with `--server-url`", "Authorise with a Reader role or the `reader` scope unless the task writes. A 403 after consent means the member's role lacks access", "Send `LD-API-Version: 20240415` on every REST call, and `LD-API-Version: beta` for beta resources, which answer 403 without it", "Read `X-Ratelimit-Global-Remaining`, `X-Ratelimit-Route-Remaining` and `X-Ratelimit-Reset` on each response, and wait `Retry-After` seconds on an IP limit", "Send `Content-Type: application/json; domain-model=launchdarkly.semanticpatch` for semantic patches, or the body is read as JSON patch and answers 400" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 71.3 } ], "editorialScores": { "ergonomics": 69, "maintenance": 82, "payments": 40, "reliability": 74, "schema": 89, "security": 66, "transparency": 74 }, "provenanceScore": 88, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npx -y --package @launchdarkly/mcp-server -- mcp start --api-key api-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "claudeCode": "claude mcp add --transport http \"launchdarkly\" \"https://mcp.launchdarkly.com/mcp/launchdarkly\"", "config": { "mcpServers": { "launchdarkly": { "type": "http", "url": "https://mcp.launchdarkly.com/mcp/launchdarkly" } } } }, "letme": { "capability": "https://letme.dev/analytics.flags", "tool": "https://letme.dev/launchdarkly" }, "area": "business", "unitPrices": [ { "item": "Foundation, service connection", "unit": "month", "usd": 10, "note": "per connection, billed yearly, first 5 included" }, { "item": "Foundation, client-side MAU", "unit": "user-month", "usd": 0.00833, "note": "$8.33 per 1,000, billed yearly" }, { "item": "Additional AI run", "unit": "tx", "usd": 0.005, "note": "$5 per 1,000 above 5,000 a month" } ], "provenance": { "legalEntity": "Catamorphic, Co. (dba LaunchDarkly)", "domain": "launchdarkly.com", "domainRegistered": "2014-07-15", "endpointOnVendorDomain": true, "terms": "https://launchdarkly.com/policies/subscription-terms/", "privacy": "https://launchdarkly.com/policies/privacy/", "statusPage": "https://status.launchdarkly.com", "changelog": "https://launchdarkly.com/docs/home/changelog", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The terms of service for Developer and Foundation self-service customers (effective 8 September 2025) name Catamorphic, Co., a Delaware corporation doing business as LaunchDarkly. Enterprise customers have separate terms at https://launchdarkly.com/policies/subscription-terms-enterprise/.", "The privacy policy (effective 8 April 2025) says it does not apply to data LaunchDarkly processes for customers. The data processing addendum at https://launchdarkly.com/policies/data-processing-addendum/ covers that data.", "launchdarkly.com/.well-known/security.txt and app.launchdarkly.com/.well-known/security.txt return 404.", "The MCP server answers on mcp.launchdarkly.com and the API on app.launchdarkly.com. The MCP endpoint's headers name Gram, from Speakeasy, which is on the sub-processor list.", "RDAP for launchdarkly.com gives a registration date of 2014-07-15." ], "score": 88 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/launchdarkly.json", "live": { "slug": "launchdarkly", "probe": { "target": "https://mcp.launchdarkly.com/mcp/launchdarkly", "method": "get", "lastAt": "2026-11-07T19:22:15.974832878Z", "lastOk": true, "lastStatus": 401, "lastMs": 320, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 99.97, "p50ms24h": 271, "p95ms24h": 348, "samples24h": 238, "samples30d": 7450, "days": [ { "date": "2026-10-08", "probes": 70, "ok": 70 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 251 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 251 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "vendorStatus": { "page": "https://status.launchdarkly.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T19:22:19.442397133Z" }, "versions": [ { "registry": "github", "name": "launchdarkly/mcp-server", "version": "v0.7.2", "released": "2026-10-27", "seenAt": "2026-11-06T23:39:08.463151071Z" }, { "registry": "npm", "name": "@launchdarkly/mcp-server", "version": "0.7.2", "seenAt": "2026-11-06T23:39:01.769693206Z" }, { "registry": "npm", "name": "@launchdarkly/node-server-sdk", "version": "9.16.4", "seenAt": "2026-11-06T23:39:06.503221385Z" }, { "registry": "npm", "name": "launchdarkly-api", "version": "20.0.0", "seenAt": "2026-11-06T23:39:06.089281348Z" }, { "registry": "pypi", "name": "launchdarkly-api", "version": "25.1.1", "released": "2026-10-30", "seenAt": "2026-11-06T23:39:06.265421062Z" }, { "registry": "pypi", "name": "launchdarkly-server-sdk", "version": "9.20.0", "released": "2026-11-05", "seenAt": "2026-11-06T23:39:08.379675336Z" } ], "githubStars": 27, "npmWeekly": 74871, "pypiWeekly": 158016, "securityTxt": { "url": "https://launchdarkly.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:12.480495142Z" }, "llmsTxt": { "url": "https://launchdarkly.com/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:52.221951252Z" }, "domain": { "domain": "launchdarkly.com", "registered": "2014-07-15", "source": "https://rdap.verisign.com/com/v1/domain/launchdarkly.com", "checkedAt": "2026-11-01T14:15:37.540687608Z" }, "pages": [ { "url": "https://launchdarkly.com/docs/home/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:12:30.58917002Z", "changedAt": "2026-11-07T14:12:30.58917002Z", "fingerprint": "0a011833453c" }, { "url": "https://launchdarkly.com/pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:12:36.764332808Z", "changedAt": "2026-11-05T12:36:00.509827916Z", "fingerprint": "b79702f6a1ef" }, { "url": "https://launchdarkly.com/policies/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:12:32.788411037Z", "changedAt": "2026-11-05T12:35:56.273486473Z", "fingerprint": "07bd39fb47af" }, { "url": "https://launchdarkly.com/policies/subscription-terms/", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:12:35.303934026Z", "changedAt": "2026-11-05T12:35:58.580019987Z", "fingerprint": "b1228f73ebac" } ], "mcpTools": { "url": "https://mcp.launchdarkly.com/mcp/launchdarkly", "checkedAt": "2026-11-07T01:45:41.609636672Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:45:41.609636672Z" }, "github": { "repo": "launchdarkly/mcp-server", "checkedAt": "2026-11-02T09:00:03.111676849Z", "stars": 27, "archived": false, "issuesEnabled": true, "pushedAt": "2026-11-02T00:12:35Z", "openIssues": 11, "openPRs": 11, "issuesOpened90d": 7, "issuesClosed90d": 3, "prsMerged90d": 5, "ci": { "branch": "main", "runs": 27, "success": 13, "failure": 14, "other": 0, "latest": "success", "latestAt": "2026-10-27T21:32:58Z" }, "replies": { "sampled": 18, "unanswered": 10, "medianDays": 3.6 } }, "updatedAt": "2026-11-07T19:22:15.974832878Z" } }, "edges": [ { "by": 25, "category": "payments", "leads": "launchdarkly", "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). Per-unit prices are public without a login, at $10 a service connection a month, $8.33 per 1,000 client-side MAU a month billed yearly and $5 per 1,000 additional AI runs. Enterprise is custom (20). The Developer plan is free with no card (20). A person signs up in a browser and approves OAuth or creates a token (0)." }, "scores": { "a": 15, "b": 40 } }, { "by": 20, "category": "transparency", "leads": "launchdarkly", "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": "Closed hosted service under published terms. The SDKs and `ldcli` are Apache-2.0 and the local MCP server is MIT (17 of 30). The privacy policy (8 April 2025) excludes data processed for customers, which the DPA (1 May 2024) covers, with deletion on written request after termination. The privacy policy gives no retention periods. The terms allow use of anonymised and aggregated data, and no clause on model training was found (20 of 30). The end-of-life policy gives API and SDK versions 12 months after a new release, and the version table lists end-of-life dates. Beta resources may change without notice (17 of 20). The sub-processor list (15 May 2026) gives locations, with Anthropic, OpenAI and Speakeasy under AI services, the DPA gives 30 days' notice of new sub-processors, and EU and federal instances exist (20)." }, "scores": { "a": 61, "b": 81 } }, { "by": 18, "category": "schema", "leads": "launchdarkly", "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": "OpenAPI 3.0.3 served without a login at app.launchdarkly.com/api/v2/openapi.json, with 253 paths and 401 operations (25). The hosted MCP input schemas need a sign-in and were not read. A docs index for agents at launchdarkly.com/docs/llms.txt, and docs pages answer as Markdown with .md (10). 399 of 401 operations have a description. The MCP tool descriptions on the server page average about 740 characters and state pagination, sorting, plan limits and which tool to call next (17). 169 enums across 746 schemas. JSON patch bodies and semantic patch instructions are loosely typed objects (9). 1,853 examples in the spec, 429 documented on 287 operations and 403 on 355, and an error table with a suggested fix for each status (13). Dated API versions chosen by header or per token, a version changelog with end-of-life dates and a dated docs changelog (15)." }, "scores": { "a": 71, "b": 89 } }, { "by": 14, "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": "The hosted MCP server lists 141 tools, far past 30 (5). The OAuth metadata names reader, writer and observability scopes, but no tool filter for the hosted server was found. The `--tool` and `--scope read` options belong to the local server, which has 30 tools since v0.7.2 (27 October 2026), so 3 of 10 added back (8). The API has `limit` and `offset` on 61 operations, filters and sorting, summary and detailed representations and an `expand` parameter on 40 (18). Errors carry `code`, `message` and `id`, with a table of statuses and fixes (15). The server page marks 73 tools read-only, 35 destructive and 89 idempotent. There are no idempotency keys on REST writes, and JSON patch can test a version before applying (15). Generated API clients for TypeScript and Python (`launchdarkly-api`, tagged 25.1.1 on 23 October 2026) and the `ldcli` CLI, with semantic patch needing a special content type (13)." }, "scores": { "a": 83, "b": 69 } }, { "by": 13, "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": "The hosted MCP server uses OAuth with PKCE (S256), dynamic client registration, a revocation endpoint and three scopes, and an authorised app can never do more than the member who approved it. API access tokens are revocable and resettable with a Reader, Writer, Admin or Owner role. Custom roles and inline policies need a plan with custom roles, and service tokens need Enterprise. No secret in a URL query string is documented (26 of 30). Reader role and reader scope, `--scope read` and `--tool` on the local server, and approval requests for changes on Enterprise. No confirmation step for destructive hosted tools was found (14 of 20). The observability tools return logs, traces, errors and session data written by end users. No prompt-injection guidance was found in the MCP docs, which warn only that an API key in a config file may appear in a conversation (3 of 15). Change history with an API at `/api/v2/auditlog` and comments on updates, limited to 30 days on the Developer plan, and the pricing table lists audit logging under Enterprise only (11 of 15). The security page lists SOC 2 Type II, ISO 27001 and FedRAMP authorisation. security.txt returns 404, and no disclosure policy or bug bounty was found on the pages read (12 of 20)." }, "scores": { "a": 79, "b": 66 } }, { "by": 6, "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. Statuspage at status.launchdarkly.com with 51 components and incident history (20). Read from the history feed (the host's robots.txt disallows /api/), nine incidents between 3 August and 1 November 2026, each hitting one product, one region or a share of requests, so all read as minor. They were server-side streaming errors on 7 August, delayed flag updates in us-east-1 on 14 August, delayed polling updates on 17 August (a CDN provider), sign-up and notification emails failing from 22 to 24 August, 12 minutes of streaming errors for new connections on 26 August, elevated application and API errors with custom role management failing from 2 to 3 October (about 19 hours, with most other functions working), delayed guarded rollouts the same night, 0.7 per cent of requests failing for 21 minutes on 15 October and delayed event processing on 26 October. The 10 July outage, marked critical, has left the window (20). The API docs describe global, route, token and IP limits and say the numbers are not published. Limit and remaining headers report them at run time (5 of 15). 429s carry reset headers, IP limits carry `Retry-After`, and the docs ask for jitter and backoff. No idempotency keys were found, though JSON patch can test a resource version and 409 is documented as retryable (11 of 15). The SLA commits to 99.9 per cent for Enterprise support and 99.99 per cent for Premium support (10). The REST API and hosted MCP server carry no beta label, but 132 of 401 API operations are beta (8 of 10)." }, "scores": { "a": 80, "b": 74 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Harness Inc.", "b": "Catamorphic, Co. (dba LaunchDarkly)", "name": "Vendor" }, { "a": "https://mcp.harness.io/mcp", "b": "https://mcp.launchdarkly.com/mcp/launchdarkly", "name": "Hosted endpoint" }, { "a": "HTTP, stdio, Streamable HTTP", "b": "HTTP, Streamable HTTP, stdio", "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": "none", "b": "Proprietary service under LaunchDarkly's terms. The local MCP server is MIT and the ldcli CLI is Apache-2.0", "name": "Licence" }, { "a": "11", "b": "141", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-11-04", "b": "2026-10-27", "name": "Last release" }, { "a": "no date given", "b": "2025-09-08", "name": "Terms last updated" }, { "a": "no date given", "b": "2025-04-08", "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": "yes", "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": "3.3M npm/wk, 2.2M PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3.5/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "LaunchDarkly scores 71.3 (BB) on agent readiness against Harness Feature Management \u0026 Experimentation's 69.2 (B), and leads in 4 of 7 scored categories. Harness Feature Management \u0026 Experimentation leads on reliability, agent ergonomics and security \u0026 auth.", "question": "Which is better for AI agents, Harness Feature Management \u0026 Experimentation or LaunchDarkly?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Harness Feature Management \u0026 Experimentation and LaunchDarkly need an API key?" }, { "answer": "Yes. Harness Feature Management \u0026 Experimentation has a hosted endpoint at https://mcp.harness.io/mcp and LaunchDarkly at https://mcp.launchdarkly.com/mcp/launchdarkly.", "question": "Can an agent call Harness Feature Management \u0026 Experimentation and LaunchDarkly without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 80 against 74", "Agent ergonomics, 83 against 69", "Security \u0026 auth, 79 against 66" ], "also": null, "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": [ "Schema \u0026 documentation, 89 against 71", "Payments \u0026 pricing, 40 against 15", "Transparency \u0026 trust, 81 against 61" ], "also": [ "Agent-ready, a grade of BB or better", "Free to start without a card" ], "goodFor": "An agent that creates and targets feature flags, runs rollouts and experiments, reads experiment results and cleans up stale flags.", "slug": "launchdarkly", "watchFor": "The hosted MCP server lists 141 tools, and no tool filter for it was found in the reviewed documentation" } ], "history": { "harness-fme": null, "launchdarkly": [ { "causes": [ "time" ], "date": "2026-11-01", "delta": 2, "from": 69.3, "fromGrade": "B", "to": 71.3, "toGrade": "BB" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 69.2, "fromGrade": "B", "to": 69.3, "toGrade": "B" } ] }, "job": { "capability": "analytics.flags", "name": "Feature flags" }, "others": [ { "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-rudderstack-mcp.json", "title": "Harness Feature Management \u0026 Experimentation vs RudderStack MCP", "url": "https://www.anchorterminal.com/compare/harness-fme-vs-rudderstack-mcp" }, { "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/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/amplitude-vs-launchdarkly.json", "title": "Amplitude vs LaunchDarkly", "url": "https://www.anchorterminal.com/compare/amplitude-vs-launchdarkly" }, { "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/countly-vs-launchdarkly.json", "title": "Countly vs LaunchDarkly", "url": "https://www.anchorterminal.com/compare/countly-vs-launchdarkly" }, { "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/flagsmith-vs-launchdarkly.json", "title": "Flagsmith vs LaunchDarkly", "url": "https://www.anchorterminal.com/compare/flagsmith-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/launchdarkly-vs-mixpanel.json", "title": "LaunchDarkly vs Mixpanel", "url": "https://www.anchorterminal.com/compare/launchdarkly-vs-mixpanel" }, { "json": "https://www.anchorterminal.com/compare/launchdarkly-vs-optimizely.json", "title": "LaunchDarkly vs Optimizely Experimentation", "url": "https://www.anchorterminal.com/compare/launchdarkly-vs-optimizely" }, { "json": "https://www.anchorterminal.com/compare/launchdarkly-vs-posthog.json", "title": "LaunchDarkly vs PostHog", "url": "https://www.anchorterminal.com/compare/launchdarkly-vs-posthog" }, { "json": "https://www.anchorterminal.com/compare/launchdarkly-vs-statsig.json", "title": "LaunchDarkly vs Statsig", "url": "https://www.anchorterminal.com/compare/launchdarkly-vs-statsig" }, { "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-launchdarkly.json", "title": "GrowthBook vs LaunchDarkly", "url": "https://www.anchorterminal.com/compare/growthbook-vs-launchdarkly" }, { "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/harness-fme-vs-mostly-good-metrics.json", "title": "Harness Feature Management \u0026 Experimentation vs Mostly Good Metrics", "url": "https://www.anchorterminal.com/compare/harness-fme-vs-mostly-good-metrics" }, { "json": "https://www.anchorterminal.com/compare/launchdarkly-vs-matomo.json", "title": "LaunchDarkly vs Matomo", "url": "https://www.anchorterminal.com/compare/launchdarkly-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": 6, "edge": "harness-fme", "harness-fme": 80, "key": "reliability", "launchdarkly": 74, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 18, "edge": "launchdarkly", "harness-fme": 71, "key": "schema", "launchdarkly": 89, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 14, "edge": "harness-fme", "harness-fme": 83, "key": "ergonomics", "launchdarkly": 69, "name": "Agent ergonomics", "weight": 13 }, { "by": 13, "edge": "harness-fme", "harness-fme": 79, "key": "security", "launchdarkly": 66, "name": "Security \u0026 auth", "weight": 14 }, { "by": 25, "edge": "launchdarkly", "harness-fme": 15, "key": "payments", "launchdarkly": 40, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 1, "edge": "launchdarkly", "harness-fme": 81, "key": "maintenance", "launchdarkly": 82, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 20, "edge": "launchdarkly", "harness-fme": 61, "key": "transparency", "launchdarkly": 81, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "LaunchDarkly scores 71.3 (BB) on agent readiness against Harness Feature Management \u0026 Experimentation's 69.2 (B), and leads in 4 of 7 scored categories. Harness Feature Management \u0026 Experimentation leads on reliability, agent ergonomics and security \u0026 auth. Both do feature flags.", "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.", "launchdarkly": "LaunchDarkly suits agents that manage feature flags, rollouts and experiments. The hosted MCP server uses OAuth with dynamic client registration and marks its tools read-only or destructive, and the Developer plan is free without a card. The server lists 141 tools, numeric rate limits are unpublished, and every REST API version except 20240415 stops working on 31 December 2026." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/harness-fme-vs-launchdarkly", "json": "https://www.anchorterminal.com/compare/harness-fme-vs-launchdarkly.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/harness-fme-vs-launchdarkly.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/harness-fme-vs-launchdarkly.min.md" }, "markdown": "LaunchDarkly scores 71.3 (BB) on agent readiness against Harness Feature Management \u0026 Experimentation's 69.2 (B), and leads in 4 of 7 scored categories. Harness Feature Management \u0026 Experimentation leads on reliability, agent ergonomics and security \u0026 auth. Both do feature flags.\n\n- Harness Feature Management \u0026 Experimentation: grade B, 69.2/100, rank #258 of 1510. Markdown https://www.anchorterminal.com/tools/harness-fme.md · JSON https://www.anchorterminal.com/api/v1/tools/harness-fme.json\n- LaunchDarkly: grade BB, 71.3/100, rank #163 of 1510. Markdown https://www.anchorterminal.com/tools/launchdarkly.md · JSON https://www.anchorterminal.com/api/v1/tools/launchdarkly.json\n- Best product analytics and experimentation tools for AI agents: https://www.anchorterminal.com/best/product-analytics/index.md\n- All 170 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 74\n- Agent ergonomics, 83 against 69\n- Security \u0026 auth, 79 against 66\n\nWatch for: No FME prices are published; Enterprise is by quotation and free plan limits are unstated\n\n### LaunchDarkly (BB)\n\nGood for: An agent that creates and targets feature flags, runs rollouts and experiments, reads experiment results and cleans up stale flags.\n\nAhead on:\n- Schema \u0026 documentation, 89 against 71\n- Payments \u0026 pricing, 40 against 15\n- Transparency \u0026 trust, 81 against 61\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- Free to start without a card\n\nWatch for: The hosted MCP server lists 141 tools, and no tool filter for it was found in the reviewed documentation\n\n\n## Why the edge\n\n### Payments \u0026 pricing: LaunchDarkly +25\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- LaunchDarkly (40): No x402, MPP or L402 (0). Per-unit prices are public without a login, at $10 a service connection a month, $8.33 per 1,000 client-side MAU a month billed yearly and $5 per 1,000 additional AI runs. Enterprise is custom (20). The Developer plan is free with no card (20). A person signs up in a browser and approves OAuth or creates a token (0).\n\n### Transparency \u0026 trust: LaunchDarkly +20\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- LaunchDarkly (81): Closed hosted service under published terms. The SDKs and `ldcli` are Apache-2.0 and the local MCP server is MIT (17 of 30). The privacy policy (8 April 2025) excludes data processed for customers, which the DPA (1 May 2024) covers, with deletion on written request after termination. The privacy policy gives no retention periods. The terms allow use of anonymised and aggregated data, and no clause on model training was found (20 of 30). The end-of-life policy gives API and SDK versions 12 months after a new release, and the version table lists end-of-life dates. Beta resources may change without notice (17 of 20). The sub-processor list (15 May 2026) gives locations, with Anthropic, OpenAI and Speakeasy under AI services, the DPA gives 30 days' notice of new sub-processors, and EU and federal instances exist (20).\n\n### Schema \u0026 documentation: LaunchDarkly +18\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- LaunchDarkly (89): OpenAPI 3.0.3 served without a login at app.launchdarkly.com/api/v2/openapi.json, with 253 paths and 401 operations (25). The hosted MCP input schemas need a sign-in and were not read. A docs index for agents at launchdarkly.com/docs/llms.txt, and docs pages answer as Markdown with .md (10). 399 of 401 operations have a description. The MCP tool descriptions on the server page average about 740 characters and state pagination, sorting, plan limits and which tool to call next (17). 169 enums across 746 schemas. JSON patch bodies and semantic patch instructions are loosely typed objects (9). 1,853 examples in the spec, 429 documented on 287 operations and 403 on 355, and an error table with a suggested fix for each status (13). Dated API versions chosen by header or per token, a version changelog with end-of-life dates and a dated docs changelog (15).\n\n### Agent ergonomics: Harness Feature Management \u0026 Experimentation +14\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- LaunchDarkly (69): The hosted MCP server lists 141 tools, far past 30 (5). The OAuth metadata names reader, writer and observability scopes, but no tool filter for the hosted server was found. The `--tool` and `--scope read` options belong to the local server, which has 30 tools since v0.7.2 (27 October 2026), so 3 of 10 added back (8). The API has `limit` and `offset` on 61 operations, filters and sorting, summary and detailed representations and an `expand` parameter on 40 (18). Errors carry `code`, `message` and `id`, with a table of statuses and fixes (15). The server page marks 73 tools read-only, 35 destructive and 89 idempotent. There are no idempotency keys on REST writes, and JSON patch can test a version before applying (15). Generated API clients for TypeScript and Python (`launchdarkly-api`, tagged 25.1.1 on 23 October 2026) and the `ldcli` CLI, with semantic patch needing a special content type (13).\n\n### Security \u0026 auth: Harness Feature Management \u0026 Experimentation +13\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- LaunchDarkly (66): The hosted MCP server uses OAuth with PKCE (S256), dynamic client registration, a revocation endpoint and three scopes, and an authorised app can never do more than the member who approved it. API access tokens are revocable and resettable with a Reader, Writer, Admin or Owner role. Custom roles and inline policies need a plan with custom roles, and service tokens need Enterprise. No secret in a URL query string is documented (26 of 30). Reader role and reader scope, `--scope read` and `--tool` on the local server, and approval requests for changes on Enterprise. No confirmation step for destructive hosted tools was found (14 of 20). The observability tools return logs, traces, errors and session data written by end users. No prompt-injection guidance was found in the MCP docs, which warn only that an API key in a config file may appear in a conversation (3 of 15). Change history with an API at `/api/v2/auditlog` and comments on updates, limited to 30 days on the Developer plan, and the pricing table lists audit logging under Enterprise only (11 of 15). The security page lists SOC 2 Type II, ISO 27001 and FedRAMP authorisation. security.txt returns 404, and no disclosure policy or bug bounty was found on the pages read (12 of 20).\n\n### Reliability: Harness Feature Management \u0026 Experimentation +6\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- LaunchDarkly (74): Graded on the hosted service with the hosted lines. Statuspage at status.launchdarkly.com with 51 components and incident history (20). Read from the history feed (the host's robots.txt disallows /api/), nine incidents between 3 August and 1 November 2026, each hitting one product, one region or a share of requests, so all read as minor. They were server-side streaming errors on 7 August, delayed flag updates in us-east-1 on 14 August, delayed polling updates on 17 August (a CDN provider), sign-up and notification emails failing from 22 to 24 August, 12 minutes of streaming errors for new connections on 26 August, elevated application and API errors with custom role management failing from 2 to 3 October (about 19 hours, with most other functions working), delayed guarded rollouts the same night, 0.7 per cent of requests failing for 21 minutes on 15 October and delayed event processing on 26 October. The 10 July outage, marked critical, has left the window (20). The API docs describe global, route, token and IP limits and say the numbers are not published. Limit and remaining headers report them at run time (5 of 15). 429s carry reset headers, IP limits carry `Retry-After`, and the docs ask for jitter and backoff. No idempotency keys were found, though JSON patch can test a resource version and 409 is documented as retryable (11 of 15). The SLA commits to 99.9 per cent for Enterprise support and 99.99 per cent for Premium support (10). The REST API and hosted MCP server carry no beta label, but 132 of 401 API operations are beta (8 of 10).\n\n## Score by category\n\n| Category | Weight | Harness Feature Management \u0026 Experimentation | LaunchDarkly | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 80 | 74 | Harness Feature Management \u0026 Experimentation +6 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 71 | 89 | LaunchDarkly +18 |\n| Agent ergonomics | 13% (16.2 this run) | 83 | 69 | Harness Feature Management \u0026 Experimentation +14 |\n| Security \u0026 auth | 14% (17.5 this run) | 79 | 66 | Harness Feature Management \u0026 Experimentation +13 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 15 | 40 | LaunchDarkly +25 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 81 | 82 | LaunchDarkly +1 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 61 | 81 | LaunchDarkly +20 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **69.2 · B** | **71.3 · BB** | |\n\n## Facts side by side\n\n| Fact | Harness Feature Management \u0026 Experimentation | LaunchDarkly |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Harness Inc. | Catamorphic, Co. (dba LaunchDarkly) |\n| Hosted endpoint | `https://mcp.harness.io/mcp` | `https://mcp.launchdarkly.com/mcp/launchdarkly` |\n| Transports | HTTP, stdio, Streamable HTTP | HTTP, Streamable HTTP, stdio |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | none | Proprietary service under LaunchDarkly's terms. The local MCP server is MIT and the ldcli CLI is Apache-2.0 |\n| Tools exposed | 11 | 141 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-11-04 | 2026-10-27 |\n| Terms last updated | no date given | 2025-09-08 |\n| Privacy policy last updated | no date given | 2025-04-08 |\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 | yes |\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 | 3.3M npm/wk, 2.2M PyPI/wk |\n| Agent reviews | none | 3.5/5 (4) |\n\n## How the scores have moved\n\n### Harness Feature Management \u0026 Experimentation\n\nNo score change since it was listed.\n\n### LaunchDarkly\n\n- +2.0 on 1 November 2026 (B to BB): time\n- +0.1 on 27 October 2026: checklist\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**LaunchDarkly.** LaunchDarkly suits agents that manage feature flags, rollouts and experiments. The hosted MCP server uses OAuth with dynamic client registration and marks its tools read-only or destructive, and the Developer plan is free without a card. The server lists 141 tools, numeric rate limits are unpublished, and every REST API version except 20240415 stops working on 31 December 2026.\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### LaunchDarkly\n\n1. Connect to https://mcp.launchdarkly.com/mcp/launchdarkly over streamable HTTP with OAuth. On the EU or federal instance run the local `@launchdarkly/mcp-server` with `--server-url`\n2. Authorise with a Reader role or the `reader` scope unless the task writes. A 403 after consent means the member's role lacks access\n3. Send `LD-API-Version: 20240415` on every REST call, and `LD-API-Version: beta` for beta resources, which answer 403 without it\n4. Read `X-Ratelimit-Global-Remaining`, `X-Ratelimit-Route-Remaining` and `X-Ratelimit-Reset` on each response, and wait `Retry-After` seconds on an IP limit\n5. Send `Content-Type: application/json; domain-model=launchdarkly.semanticpatch` for semantic patches, or the body is read as JSON patch and answers 400\n\n## Questions\n\n### Which is better for AI agents, Harness Feature Management \u0026 Experimentation or LaunchDarkly?\n\nLaunchDarkly scores 71.3 (BB) on agent readiness against Harness Feature Management \u0026 Experimentation's 69.2 (B), and leads in 4 of 7 scored categories. Harness Feature Management \u0026 Experimentation leads on reliability, agent ergonomics and security \u0026 auth.\n\n### Do Harness Feature Management \u0026 Experimentation and LaunchDarkly 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 LaunchDarkly without installing anything?\n\nYes. Harness Feature Management \u0026 Experimentation has a hosted endpoint at https://mcp.harness.io/mcp and LaunchDarkly at https://mcp.launchdarkly.com/mcp/launchdarkly.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/harness-fme-vs-launchdarkly.json, and with the fewest tokens: https://www.anchorterminal.com/compare/harness-fme-vs-launchdarkly.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"harness-fme\", \"b\": \"launchdarkly\"}`. From a terminal: `anchor compare harness-fme launchdarkly`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/harness-fme.json and https://www.anchorterminal.com/api/v1/tools/launchdarkly.json\n\n## Other comparisons with Harness Feature Management \u0026 Experimentation or LaunchDarkly\n\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 RudderStack MCP](https://www.anchorterminal.com/compare/harness-fme-vs-rudderstack-mcp.md)\n- [Harness Feature Management \u0026 Experimentation vs Woopra](https://www.anchorterminal.com/compare/harness-fme-vs-woopra.md)\n- [Amplitude vs Harness Feature Management \u0026 Experimentation](https://www.anchorterminal.com/compare/amplitude-vs-harness-fme.md)\n- [Amplitude vs LaunchDarkly](https://www.anchorterminal.com/compare/amplitude-vs-launchdarkly.md)\n- [Countly vs Harness Feature Management \u0026 Experimentation](https://www.anchorterminal.com/compare/countly-vs-harness-fme.md)\n- [Countly vs LaunchDarkly](https://www.anchorterminal.com/compare/countly-vs-launchdarkly.md)\n- [Flagsmith vs Harness Feature Management \u0026 Experimentation](https://www.anchorterminal.com/compare/flagsmith-vs-harness-fme.md)\n- [Flagsmith vs LaunchDarkly](https://www.anchorterminal.com/compare/flagsmith-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- [LaunchDarkly vs Mixpanel](https://www.anchorterminal.com/compare/launchdarkly-vs-mixpanel.md)\n- [LaunchDarkly vs Optimizely Experimentation](https://www.anchorterminal.com/compare/launchdarkly-vs-optimizely.md)\n- [LaunchDarkly vs PostHog](https://www.anchorterminal.com/compare/launchdarkly-vs-posthog.md)\n- [LaunchDarkly vs Statsig](https://www.anchorterminal.com/compare/launchdarkly-vs-statsig.md)\n- [GrowthBook vs Harness Feature Management \u0026 Experimentation](https://www.anchorterminal.com/compare/growthbook-vs-harness-fme.md)\n- [GrowthBook vs LaunchDarkly](https://www.anchorterminal.com/compare/growthbook-vs-launchdarkly.md)\n- [Harness Feature Management \u0026 Experimentation vs Matomo](https://www.anchorterminal.com/compare/harness-fme-vs-matomo.md)\n- [Harness Feature Management \u0026 Experimentation vs Mostly Good Metrics](https://www.anchorterminal.com/compare/harness-fme-vs-mostly-good-metrics.md)\n- [LaunchDarkly vs Matomo](https://www.anchorterminal.com/compare/launchdarkly-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 LaunchDarkly", "url": "" } ], "description": "LaunchDarkly scores 71.3 (BB) to Harness Feature Management \u0026 Experimentation's 69.2 (B) for feature flags. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Harness Feature Management \u0026 Experimentation B 69.2", "LaunchDarkly BB 71.3", "scores" ], "h1": "Harness Feature Management \u0026 Experimentation vs LaunchDarkly", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/harness-fme-vs-launchdarkly", "published": "2026-10-01", "section": "tools", "title": "Harness Feature Management \u0026 Experimentation vs LaunchDarkly (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/harness-fme-vs-launchdarkly" }, "tokens": { "markdown": 5600, "slim": 3380 }, "version": 1 }