{ "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": "Harness Feature Management \u0026 Experimentation scores 69.2 (B) on agent readiness against PostHog's 67.4 (B), and leads in 1 of 7 scored categories. PostHog leads on schema \u0026 documentation, security \u0026 auth, payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust.", "b": { "slug": "posthog", "name": "PostHog", "vendor": "PostHog Inc.", "vendorUrl": "https://posthog.com", "kind": "http-api", "category": "product-analytics", "summary": "PostHog is an open-source product analytics platform with session replay, feature flags, experiments, error tracking and a data warehouse. Agents reach PostHog Cloud through a REST API with a public OpenAPI spec and an official hosted MCP server.", "url": "https://www.anchorterminal.com/tools/posthog", "markdownUrl": "https://www.anchorterminal.com/tools/posthog.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/posthog.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/posthog.json", "dns": "posthog.grade.anchorterminal.com", "repo": "https://github.com/PostHog/posthog", "license": "MIT for the repository outside the `ee` directory, which has its own licence. PostHog Cloud is a hosted service under PostHog's terms", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://us.posthog.com", "packages": [ { "registry": "npm", "name": "posthog-node" }, { "registry": "npm", "name": "posthog-js" }, { "registry": "pypi", "name": "posthog" }, { "registry": "npm", "name": "@posthog/cli" } ], "auth": "mixed", "authNotes": "Self-serve. Private endpoints take a Bearer personal API key (`phx_`) that a signed-in user creates with chosen scopes and project or organisation access, or an OAuth access token. OAuth at oauth.posthog.com supports PKCE, dynamic client registration and client ID metadata documents, with no app review needed to go live. The MCP server uses OAuth by default or a personal API key made with the MCP Server preset. Project secret API keys are in beta. Capture and flag evaluation take the public project token.", "pricing": "freemium", "pricingNotes": "Free plan with no card, covering 1 million analytics events and 1 million flag requests a month. The paid plan has no base fee and no seat charge, and bills per unit above the free allowance (analytics events from $0.00005). API and MCP calls are not billed, but personal API key queries draw on an hourly read budget that is larger on a paid plan (https://posthog.com/pricing, checked 2026-10-07).", "priceSummary": "$0.0001 / tx", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs, the OpenAPI spec or the pricing page (checked 2026-10-07).", "endpoints": [] }, "toolCount": 1183, "popularity": { "githubStars": 40176, "npmWeekly": 15243417, "pypiWeekly": null, "asOf": "2026-10-07" }, "docsUrl": "https://posthog.com/docs/api", "llmsTxt": "https://posthog.com/llms.txt", "openapi": "https://app.posthog.com/api/schema/", "registryName": "io.github.PostHog/mcp", "capabilities": [ "analytics.query", "analytics.events", "analytics.funnels", "analytics.experiments", "analytics.flags", "observability.errors", "observability.logs" ], "tags": [ "official", "hosted", "open-source", "mcp", "oauth", "openapi", "llms-txt", "free-tier", "no-card", "eu-region", "status-page", "soc2", "typescript", "python" ], "lastRelease": "2026-10-30", "graded": true, "anchor": { "graded": true, "score": 67.4, "grade": "B", "agentReady": false, "rank": 328, "ranked": true, "rankOf": 1510, "categoryRank": 6, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 78, "maintenance": 89, "payments": 40, "reliability": 84, "schema": 81, "security": 84, "transparency": 83 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": -10, "negativeNotes": [ "-3: 2025-11-24. Malicious versions of posthog-node, posthog-js and six other npm packages were published with a stolen token after an attacker took CI secrets through a pull request workflow. PostHog removed them in about five hours and published a post-mortem on 26 November 2025, so the deduction is reduced (https://posthog.com/blog/nov-24-shai-hulud-attack-post-mortem).", "-2: 2026-05-29, disclosed 2026-06-02 as PSA-2026-00001 (critical). Researchers used an unsandboxed, outdated Chromium to reach a US Cloud pod and read internal production credentials. PostHog says no customer data was accessed and the credentials were rotated. Fixed and documented (https://posthog.com/handbook/company/security-advisories).", "-2: 2026-07-11 to 2026-08-04, disclosed 2026-08-21 as PSA-2026-00002 (high). Customer-run nginx proxies set up as PostHog's guide showed sent traffic to released AWS addresses, and a researcher read traffic from six EU customers. The report sat in triage for five weeks. Fixed and documented (https://posthog.com/handbook/company/security-advisories).", "-3: 2026-10-23. posthog 7.75.11 (PyPI) and posthog-node 5.57.1 (npm) stopped copying the `headers` and `authorization` of MCP tool definitions into `$ai_tools` on AI events, and stopped sending exception text that can quote prompts in `$ai_error` when privacy mode is on. The package changelogs describe the fix, and PostHog's security advisories page lists no advisory for it (https://github.com/PostHog/posthog-python/blob/main/posthog/CHANGELOG.md)." ], "verdict": "PostHog suits agents that need to query product data and manage flags or experiments. Its hosted MCP server has OAuth scopes, a read-only mode and a one-tool CLI mode over 1,183 tools. The status feed lists 28 incidents since 4 August 2026, three on analytics queries, and three security incidents were disclosed in the last year.", "bestFor": "An agent that answers product questions in SQL or with funnel, retention and trends queries, and that manages feature flags, experiments and error tracking in the same project.", "strengths": [ "Public OpenAPI 3.1 spec with 2,347 operations and a scope on most of them, plus llms.txt and a Markdown copy of every docs page", "Hosted MCP server with OAuth, a read-only switch, filters by product area or tool name and pinning to one project", "CLI mode registers one `exec` tool that searches, inspects and calls the 1,183 tools on demand", "Free plan without a card, with 1 million analytics events and 1 million flag requests a month, and public per-unit prices above that", "MIT source outside the `ee` directory, a public SOC 2 Type 2 report and a public security advisories page" ], "weaknesses": [ "28 incidents on the status feed between 4 August and 27 October 2026, three of them analytics query timeouts or failures", "Three security incidents in twelve months, among them malicious npm SDK versions on 24 November 2025. A 23 October 2026 SDK fix for MCP credentials in AI events had no advisory", "API queries stop at 10 seconds of execution, three at a time per project, with an hourly read budget on personal API keys", "No API versioning or deprecation policy was found, and the query docs reserve the right to restrict export-like queries without notice", "Customer content can be used to train PostHog's own models unless the customer opts out in settings" ], "agentNotes": [ "Add `?readonly=true` or the `x-posthog-read-only` header to the MCP URL unless the task needs writes", "Pin the session with `x-posthog-project-id`, which also removes the `switch-project` and `switch-organization` tools", "In CLI mode run `info \u003ctool\u003e` once before `call`, and send one `exec` command per request", "On a 429 with code `api_queries_budget_exceeded`, wait for `Retry-After` and read `X-PostHog-Query-Budget-Remaining-Bytes`", "Page SQL results by keyset on `timestamp`. `OFFSET` returns 400 for personal API keys, and results cap at 50,000 rows" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3.3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 67.4 } ], "editorialScores": { "ergonomics": 78, "maintenance": 89, "payments": 40, "reliability": 84, "schema": 81, "security": 84, "transparency": 71 }, "provenanceScore": 95, "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 @posthog/wizard mcp add", "http": "curl \\\n -H 'Content-Type: application/json' \\\n -H \"Authorization: Bearer $POSTHOG_PERSONAL_API_KEY\" \\\n https://us.posthog.com/api/projects/:project_id/query/ \\\n -d '{\"query\": {\"kind\": \"HogQLQuery\", \"query\": \"select event, count() from events group by event limit 100\"}}'", "claudeCode": "claude mcp add --transport http posthog https://mcp.posthog.com/mcp -s user", "config": { "mcpServers": { "posthog": { "url": "https://mcp.posthog.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/analytics.query", "tool": "https://letme.dev/posthog" }, "area": "business", "unitPrices": [ { "item": "Product analytics event", "unit": "tx", "usd": 0.00005, "note": "1 to 2 million a month, first 1 million free, lower above" }, { "item": "Feature flag request", "unit": "tx", "usd": 0.0001, "note": "1 to 2 million a month, first 1 million free, lower above" }, { "item": "Session recording", "unit": "tx", "usd": 0.005, "note": "5,001 to 15,000 a month, first 5,000 free" }, { "item": "Data warehouse row", "unit": "record", "usd": 0.000015, "note": "1 to 10 million a month, first 1 million free" }, { "item": "Boost package", "unit": "month", "usd": 250 }, { "item": "Scale package", "unit": "month", "usd": 750 }, { "item": "Enterprise package", "unit": "month", "usd": 2000 } ], "provenance": { "legalEntity": "PostHog Inc. (formerly Hiberly Inc.)", "domain": "posthog.com", "domainRegistered": "2020-01-23", "endpointOnVendorDomain": true, "terms": "https://posthog.com/terms", "privacy": "https://posthog.com/privacy", "statusPage": "https://www.posthogstatus.com", "changelog": "https://posthog.com/changelog", "securityTxt": "valid", "checked": "2026-10-07", "notes": [ "The privacy policy names PostHog Inc., formerly known as Hiberly Inc., and its subsidiaries. The security handbook names Hiberly Ltd. as the UK entity.", "posthog.com/.well-known/security.txt expires 2027-08-30 and points to the security handbook. The copy on us.posthog.com expired 2024-03-14.", "status.posthog.com redirects to www.posthogstatus.com.", "RDAP for posthog.com gives a registration date of 2020-01-23.", "The API, OAuth server and MCP server answer on posthog.com subdomains." ], "score": 95 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/posthog.json", "live": { "slug": "posthog", "probe": { "target": "https://us.posthog.com", "method": "get", "lastAt": "2026-11-07T19:22:27.254792206Z", "lastOk": true, "lastStatus": 200, "lastMs": 501, "authRequired": false, "uptime24h": 100, "uptime30d": 99.99, "p50ms24h": 445, "p95ms24h": 567, "samples24h": 238, "samples30d": 7473, "days": [ { "date": "2026-10-08", "probes": 93, "ok": 93 }, { "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": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 252 }, { "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": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "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://www.posthogstatus.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:37.450387165Z" }, "versions": [ { "registry": "github", "name": "PostHog/posthog", "version": "desktop-v0.61.959", "released": "2026-11-06", "seenAt": "2026-11-06T23:57:41.813768908Z" }, { "registry": "mcp-registry", "name": "io.github.PostHog/mcp", "version": "1.0.1", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "npm", "name": "@posthog/cli", "version": "0.19.0", "seenAt": "2026-11-06T23:57:40.070966304Z" }, { "registry": "npm", "name": "posthog-js", "version": "1.447.3", "seenAt": "2026-11-06T23:57:38.624326161Z" }, { "registry": "npm", "name": "posthog-node", "version": "5.63.1", "seenAt": "2026-11-06T23:57:37.623108072Z" }, { "registry": "pypi", "name": "posthog", "version": "7.86.0", "released": "2026-11-06", "seenAt": "2026-11-06T23:57:39.946740628Z" } ], "githubStars": 40679, "npmWeekly": 20839148, "pypiWeekly": 12063741, "securityTxt": { "url": "https://posthog.com/.well-known/security.txt", "state": "valid", "expires": "2027-08-30T00:00:00.000Z", "checkedAt": "2026-11-07T16:00:18.698644072Z" }, "llmsTxt": { "url": "https://posthog.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:40.03441392Z" }, "domain": { "domain": "posthog.com", "registered": "2020-01-23", "source": "https://rdap.verisign.com/com/v1/domain/posthog.com", "checkedAt": "2026-11-01T14:23:59.370052225Z" }, "pages": [ { "url": "https://posthog.com/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:17:07.593863392Z", "changedAt": "2026-11-07T14:17:07.593863392Z", "fingerprint": "e3af71f7b627" }, { "url": "https://posthog.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:17:09.971897037Z", "changedAt": "2026-11-07T14:17:09.971897037Z", "fingerprint": "b6bf14465bc4" }, { "url": "https://posthog.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:17:12.346376074Z", "changedAt": "2026-11-07T14:17:12.346376074Z", "fingerprint": "562ec288cab5" }, { "url": "https://posthog.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:17:15.548582875Z", "changedAt": "2026-11-07T14:17:15.548582875Z", "fingerprint": "78b5df11b9ff" } ], "mcpTools": { "url": "https://mcp.posthog.com/mcp", "checkedAt": "2026-11-07T01:46:54.661711518Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:46:54.661711518Z" }, "github": { "repo": "posthog/posthog", "checkedAt": "2026-11-02T09:17:59.883331399Z", "stars": 40594, "archived": false, "issuesEnabled": true, "pushedAt": "2026-11-02T09:17:42Z", "openIssues": 3875, "openPRs": 1342, "issuesOpened90d": 1602, "issuesClosed90d": 1028, "prsMerged90d": 18318, "ci": { "branch": "master", "runs": 50, "success": 50, "failure": 0, "other": 0, "latest": "success", "latestAt": "2026-10-23T00:10:29Z" }, "advisories": [ { "ghsa": "GHSA-wqqw-r8c5-j67c", "cve": "CVE-2023-46746", "severity": "low", "published": "2023-11-28T12:07:41Z" } ] }, "updatedAt": "2026-11-07T19:22:27.254792206Z" } }, "edges": [ { "by": 25, "category": "payments", "leads": "posthog", "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 for every product published without a login, in a Markdown pricing page too (20). Free plan with no card (20). A person signs up in a browser and creates a key or approves OAuth (0)." }, "scores": { "a": 15, "b": 40 } }, { "by": 22, "category": "transparency", "leads": "posthog", "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": "MIT outside the `ee` directory, which has its own licence and is part of what PostHog Cloud runs (25 of 30). Privacy policy, a self-serve DPA and the terms agree. The terms let PostHog use de-identified customer content to train its own models unless the customer opts out, and bar third parties from training on it. The privacy policy gives no retention periods, while the pricing page gives 1 year on the free plan and 7 on paid (22). No deprecation policy was found, and the query docs reserve the right to restrict export-like queries without notice. 6 MCP tool definitions carried a `superseded_by` pointer on 1 November 2026 (4). Sub-processor list updated 12 June 2026 with locations, 14 days' notice of changes, and data in Virginia or Germany (20)." }, "scores": { "a": 61, "b": 83 } }, { "by": 10, "category": "schema", "leads": "posthog", "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.1 served without a login, 1,742 paths and 2,347 operations, and typed JSON Schema inputs on the MCP tools (25). llms.txt, and every docs page has a Markdown copy at the same address with .md (10). 1,487 of 2,347 operations (63 per cent) have a description. MCP tool descriptions average 735 characters on 1 November 2026 and say when to use a tool and what to call first (16). 1,243 enums across 4,792 schemas and a required scope on most operations (13). 706 examples in the spec. It documents 400 on 224 operations and 429 on 55, and the docs show the error shape with examples (9). Dated public changelog with RSS, but the spec version is fixed at 1.0.0 and the API has no versions (8)." }, "scores": { "a": 71, "b": 81 } }, { "by": 8, "category": "maintenance", "leads": "posthog", "name": "Maintenance \u0026 community", "reasons": { "a": "harness-mcp-v2 3.2.40 was tagged on 4 November 2026 (30). 14 tagged MCP releases between 8 August and 4 November (20). 100 commits since 8 August in the clone; FME docs and SDK release notes are dated, with support and a community site. Issue response times weren't read because the GitHub API refused us for its rate limit (15 of 25). Not found in the official MCP registry under a Harness namespace; official SDKs are current (8 of 15). MIT package with npm shrinkwrap and tests; CI state not read (8 of 10). 30+20+15+8+8 = 81.", "b": "The changelog's newest entries are dated 30 October 2026, and posthog-node 5.61.1 and the Python SDK's posthog-v7.81.1 came out the same day (30). 204 dated changelog entries since 3 August 2026 (20). Public changelog, community questions and in-app support. Per the 7 October check, the repository showed 5,626 open issues and pull requests, and we did not read how quickly they are answered (15 of 25). `io.github.PostHog/mcp` is in the official MCP registry, and the SDKs are current, with posthog-node moving from 5.55.0 to 5.61.1 between 7 and 30 October 2026 (15). 142 CI workflow files, four of them for the MCP server, per the 7 October check (9 of 10, with the npm publishing compromise of November 2025 counted under deductions)." }, "scores": { "a": 81, "b": 89 } }, { "by": 5, "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": "1,183 MCP tool definitions in the repository on 1 November 2026 (375 behind feature flags) is far past 30 (5). Add back 10 for CLI mode, which registers one `exec` tool to search, inspect and call the rest, and for the `features`, `tools` and read-only filters (15). Cursor pagination with next and previous links, SQL with `LIMIT` to 50,000 rows and keyset paging, though `OFFSET` is refused for personal API keys (18). Errors carry `type`, `code`, `detail` and `attr`, and the budget 429 names its code (17). Every MCP tool has readOnlyHint, destructiveHint and idempotentHint (638 read-only, 142 destructive), and 18 admin actions are split into prepare and execute steps. No idempotency keys on REST writes (15). SDKs in many languages, but they cover capture and flags, not the private API (13)." }, "scores": { "a": 83, "b": 78 } }, { "by": 5, "category": "security", "leads": "posthog", "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 with PKCE, 226 scopes, a revocation endpoint and dynamic registration, or personal API keys with scopes, project limits and rolling. A key can still be created with full access, and keys found in public GitHub repositories are rolled automatically (28). Read-only mode, filters by product area or tool, project pinning, and a typed confirmation for 18 admin actions (18). The MCP docs warn about prompt injection and tell users to review tool calls, and the CLI escapes informational responses. No further mitigation is documented for event and replay data that end users wrote (9). Activity logs with an API, MCP calls recorded with the caller's IP, and an admin view of every key with last use. Longer retention needs a platform package (12). security.txt valid to 30 August 2027, Bugcrowd disclosure programme paid in merchandise, public SOC 2 Type 2 report, annual penetration test and a public advisories page (17)." }, "scores": { "a": 79, "b": 84 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Harness Inc.", "b": "PostHog Inc.", "name": "Vendor" }, { "a": "https://mcp.harness.io/mcp", "b": "https://us.posthog.com", "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": "not published", "b": "$0.0001 per transaction", "name": "Price for feature flags" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "MIT for the repository outside the `ee` directory, which has its own licence. PostHog Cloud is a hosted service under PostHog's terms", "name": "Licence" }, { "a": "11", "b": "1183", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "io.github.PostHog/mcp", "name": "MCP registry" }, { "a": "2026-11-04", "b": "2026-10-30", "name": "Last release" }, { "a": "no date given", "b": "2026-06-29", "name": "Terms last updated" }, { "a": "no date given", "b": "2026-06-29", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "yes, with an opt-out", "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": "40k stars, 15.2M npm/wk", "name": "Popularity" }, { "a": "none", "b": "3.3/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "Harness Feature Management \u0026 Experimentation scores 69.2 (B) on agent readiness against PostHog's 67.4 (B), and leads in 1 of 7 scored categories. PostHog leads on schema \u0026 documentation, security \u0026 auth, payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust.", "question": "Which is better for AI agents, Harness Feature Management \u0026 Experimentation or PostHog?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Harness Feature Management \u0026 Experimentation and PostHog need an API key?" }, { "answer": "Yes. Harness Feature Management \u0026 Experimentation has a hosted endpoint at https://mcp.harness.io/mcp and PostHog at https://us.posthog.com.", "question": "Can an agent call Harness Feature Management \u0026 Experimentation and PostHog without installing anything?" }, { "answer": "No open-source release is listed for Harness Feature Management \u0026 Experimentation. PostHog is open source (MIT for the repository outside the `ee` directory, which has its own licence. PostHog Cloud is a hosted service under PostHog's terms).", "question": "Are Harness Feature Management \u0026 Experimentation and PostHog open source?" } ], "goodFor": [ { "aheadOn": [ "Agent ergonomics, 83 against 78" ], "also": [ "Runs on your own machine", "No incidents deducted, where PostHog loses 10 points for them" ], "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, 81 against 71", "Security \u0026 auth, 84 against 79", "Payments \u0026 pricing, 40 against 15", "Maintenance \u0026 community, 89 against 81", "Transparency \u0026 trust, 83 against 61" ], "also": [ "Free to start without a card", "Open source" ], "goodFor": "An agent that answers product questions in SQL or with funnel, retention and trends queries, and that manages feature flags, experiments and error tracking in the same project.", "slug": "posthog", "watchFor": "28 incidents on the status feed between 4 August and 27 October 2026, three of them analytics query timeouts or failures" } ], "history": { "harness-fme": null, "posthog": [ { "causes": [ "security", "correction" ], "date": "2026-11-01", "delta": -1, "from": 68.4, "fromGrade": "B", "to": 67.4, "toGrade": "B" } ] }, "job": { "capability": "analytics.flags", "name": "Feature flags" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amplitude-vs-posthog.json", "title": "Amplitude vs PostHog", "url": "https://www.anchorterminal.com/compare/amplitude-vs-posthog" }, { "json": "https://www.anchorterminal.com/compare/basedash-mcp-vs-posthog.json", "title": "Basedash MCP vs PostHog", "url": "https://www.anchorterminal.com/compare/basedash-mcp-vs-posthog" }, { "json": "https://www.anchorterminal.com/compare/countly-vs-posthog.json", "title": "Countly vs PostHog", "url": "https://www.anchorterminal.com/compare/countly-vs-posthog" }, { "json": "https://www.anchorterminal.com/compare/fullstory-vs-posthog.json", "title": "Fullstory vs PostHog", "url": "https://www.anchorterminal.com/compare/fullstory-vs-posthog" }, { "json": "https://www.anchorterminal.com/compare/matomo-vs-posthog.json", "title": "Matomo vs PostHog", "url": "https://www.anchorterminal.com/compare/matomo-vs-posthog" }, { "json": "https://www.anchorterminal.com/compare/mixpanel-vs-posthog.json", "title": "Mixpanel vs PostHog", "url": "https://www.anchorterminal.com/compare/mixpanel-vs-posthog" }, { "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/openpanel-vs-posthog.json", "title": "OpenPanel vs PostHog", "url": "https://www.anchorterminal.com/compare/openpanel-vs-posthog" }, { "json": "https://www.anchorterminal.com/compare/pendo-vs-posthog.json", "title": "Pendo vs PostHog", "url": "https://www.anchorterminal.com/compare/pendo-vs-posthog" }, { "json": "https://www.anchorterminal.com/compare/posthog-vs-rudderstack-mcp.json", "title": "PostHog vs RudderStack MCP", "url": "https://www.anchorterminal.com/compare/posthog-vs-rudderstack-mcp" }, { "json": "https://www.anchorterminal.com/compare/posthog-vs-statsig.json", "title": "PostHog vs Statsig", "url": "https://www.anchorterminal.com/compare/posthog-vs-statsig" }, { "json": "https://www.anchorterminal.com/compare/posthog-vs-userpilot.json", "title": "PostHog vs Userpilot", "url": "https://www.anchorterminal.com/compare/posthog-vs-userpilot" }, { "json": "https://www.anchorterminal.com/compare/posthog-vs-woopra.json", "title": "PostHog vs Woopra", "url": "https://www.anchorterminal.com/compare/posthog-vs-woopra" }, { "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/heap-vs-posthog.json", "title": "Heap vs PostHog", "url": "https://www.anchorterminal.com/compare/heap-vs-posthog" }, { "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/flagsmith-vs-posthog.json", "title": "Flagsmith vs PostHog", "url": "https://www.anchorterminal.com/compare/flagsmith-vs-posthog" }, { "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-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-posthog.json", "title": "LaunchDarkly vs PostHog", "url": "https://www.anchorterminal.com/compare/launchdarkly-vs-posthog" }, { "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-posthog.json", "title": "GrowthBook vs PostHog", "url": "https://www.anchorterminal.com/compare/growthbook-vs-posthog" }, { "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/optimizely-vs-posthog.json", "title": "Optimizely Experimentation vs PostHog", "url": "https://www.anchorterminal.com/compare/optimizely-vs-posthog" } ], "panel": null, "scores": [ { "by": 4, "edge": "posthog", "harness-fme": 80, "key": "reliability", "name": "Reliability", "posthog": 84, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 10, "edge": "posthog", "harness-fme": 71, "key": "schema", "name": "Schema \u0026 documentation", "posthog": 81, "weight": 13 }, { "by": 5, "edge": "harness-fme", "harness-fme": 83, "key": "ergonomics", "name": "Agent ergonomics", "posthog": 78, "weight": 13 }, { "by": 5, "edge": "posthog", "harness-fme": 79, "key": "security", "name": "Security \u0026 auth", "posthog": 84, "weight": 14 }, { "by": 25, "edge": "posthog", "harness-fme": 15, "key": "payments", "name": "Payments \u0026 pricing", "posthog": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 8, "edge": "posthog", "harness-fme": 81, "key": "maintenance", "name": "Maintenance \u0026 community", "posthog": 89, "weight": 7 }, { "by": 22, "edge": "posthog", "harness-fme": 61, "key": "transparency", "name": "Transparency \u0026 trust", "posthog": 83, "weight": 7 } ], "summary": "Harness Feature Management \u0026 Experimentation scores 69.2 (B) on agent readiness against PostHog's 67.4 (B), and leads in 1 of 7 scored categories. PostHog leads on schema \u0026 documentation, security \u0026 auth, payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust. 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.", "posthog": "PostHog suits agents that need to query product data and manage flags or experiments. Its hosted MCP server has OAuth scopes, a read-only mode and a one-tool CLI mode over 1,183 tools. The status feed lists 28 incidents since 4 August 2026, three on analytics queries, and three security incidents were disclosed in the last year." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/harness-fme-vs-posthog", "json": "https://www.anchorterminal.com/compare/harness-fme-vs-posthog.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/harness-fme-vs-posthog.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/harness-fme-vs-posthog.min.md" }, "markdown": "Harness Feature Management \u0026 Experimentation scores 69.2 (B) on agent readiness against PostHog's 67.4 (B), and leads in 1 of 7 scored categories. PostHog leads on schema \u0026 documentation, security \u0026 auth, payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust. 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- PostHog: grade B, 67.4/100, rank #328 of 1510. Markdown https://www.anchorterminal.com/tools/posthog.md · JSON https://www.anchorterminal.com/api/v1/tools/posthog.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- Agent ergonomics, 83 against 78\n\nAlso in its favour:\n- Runs on your own machine\n- No incidents deducted, where PostHog loses 10 points for them\n\nWatch for: No FME prices are published; Enterprise is by quotation and free plan limits are unstated\n\n### PostHog (B)\n\nGood for: An agent that answers product questions in SQL or with funnel, retention and trends queries, and that manages feature flags, experiments and error tracking in the same project.\n\nAhead on:\n- Schema \u0026 documentation, 81 against 71\n- Security \u0026 auth, 84 against 79\n- Payments \u0026 pricing, 40 against 15\n- Maintenance \u0026 community, 89 against 81\n- Transparency \u0026 trust, 83 against 61\n\nAlso in its favour:\n- Free to start without a card\n- Open source\n\nWatch for: 28 incidents on the status feed between 4 August and 27 October 2026, three of them analytics query timeouts or failures\n\n\n## Why the edge\n\n### Payments \u0026 pricing: PostHog +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- PostHog (40): No x402, MPP or L402 (0). Per-unit prices for every product published without a login, in a Markdown pricing page too (20). Free plan with no card (20). A person signs up in a browser and creates a key or approves OAuth (0).\n\n### Transparency \u0026 trust: PostHog +22\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- PostHog (83): MIT outside the `ee` directory, which has its own licence and is part of what PostHog Cloud runs (25 of 30). Privacy policy, a self-serve DPA and the terms agree. The terms let PostHog use de-identified customer content to train its own models unless the customer opts out, and bar third parties from training on it. The privacy policy gives no retention periods, while the pricing page gives 1 year on the free plan and 7 on paid (22). No deprecation policy was found, and the query docs reserve the right to restrict export-like queries without notice. 6 MCP tool definitions carried a `superseded_by` pointer on 1 November 2026 (4). Sub-processor list updated 12 June 2026 with locations, 14 days' notice of changes, and data in Virginia or Germany (20).\n\n### Schema \u0026 documentation: PostHog +10\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- PostHog (81): OpenAPI 3.1 served without a login, 1,742 paths and 2,347 operations, and typed JSON Schema inputs on the MCP tools (25). llms.txt, and every docs page has a Markdown copy at the same address with .md (10). 1,487 of 2,347 operations (63 per cent) have a description. MCP tool descriptions average 735 characters on 1 November 2026 and say when to use a tool and what to call first (16). 1,243 enums across 4,792 schemas and a required scope on most operations (13). 706 examples in the spec. It documents 400 on 224 operations and 429 on 55, and the docs show the error shape with examples (9). Dated public changelog with RSS, but the spec version is fixed at 1.0.0 and the API has no versions (8).\n\n### Maintenance \u0026 community: PostHog +8\n\n- Harness Feature Management \u0026 Experimentation (81): harness-mcp-v2 3.2.40 was tagged on 4 November 2026 (30). 14 tagged MCP releases between 8 August and 4 November (20). 100 commits since 8 August in the clone; FME docs and SDK release notes are dated, with support and a community site. Issue response times weren't read because the GitHub API refused us for its rate limit (15 of 25). Not found in the official MCP registry under a Harness namespace; official SDKs are current (8 of 15). MIT package with npm shrinkwrap and tests; CI state not read (8 of 10). 30+20+15+8+8 = 81.\n- PostHog (89): The changelog's newest entries are dated 30 October 2026, and posthog-node 5.61.1 and the Python SDK's posthog-v7.81.1 came out the same day (30). 204 dated changelog entries since 3 August 2026 (20). Public changelog, community questions and in-app support. Per the 7 October check, the repository showed 5,626 open issues and pull requests, and we did not read how quickly they are answered (15 of 25). `io.github.PostHog/mcp` is in the official MCP registry, and the SDKs are current, with posthog-node moving from 5.55.0 to 5.61.1 between 7 and 30 October 2026 (15). 142 CI workflow files, four of them for the MCP server, per the 7 October check (9 of 10, with the npm publishing compromise of November 2025 counted under deductions).\n\n### Agent ergonomics: Harness Feature Management \u0026 Experimentation +5\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- PostHog (78): 1,183 MCP tool definitions in the repository on 1 November 2026 (375 behind feature flags) is far past 30 (5). Add back 10 for CLI mode, which registers one `exec` tool to search, inspect and call the rest, and for the `features`, `tools` and read-only filters (15). Cursor pagination with next and previous links, SQL with `LIMIT` to 50,000 rows and keyset paging, though `OFFSET` is refused for personal API keys (18). Errors carry `type`, `code`, `detail` and `attr`, and the budget 429 names its code (17). Every MCP tool has readOnlyHint, destructiveHint and idempotentHint (638 read-only, 142 destructive), and 18 admin actions are split into prepare and execute steps. No idempotency keys on REST writes (15). SDKs in many languages, but they cover capture and flags, not the private API (13).\n\n### Security \u0026 auth: PostHog +5\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- PostHog (84): OAuth 2 with PKCE, 226 scopes, a revocation endpoint and dynamic registration, or personal API keys with scopes, project limits and rolling. A key can still be created with full access, and keys found in public GitHub repositories are rolled automatically (28). Read-only mode, filters by product area or tool, project pinning, and a typed confirmation for 18 admin actions (18). The MCP docs warn about prompt injection and tell users to review tool calls, and the CLI escapes informational responses. No further mitigation is documented for event and replay data that end users wrote (9). Activity logs with an API, MCP calls recorded with the caller's IP, and an admin view of every key with last use. Longer retention needs a platform package (12). security.txt valid to 30 August 2027, Bugcrowd disclosure programme paid in merchandise, public SOC 2 Type 2 report, annual penetration test and a public advisories page (17).\n\n## Score by category\n\n| Category | Weight | Harness Feature Management \u0026 Experimentation | PostHog | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 80 | 84 | PostHog +4 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 71 | 81 | PostHog +10 |\n| Agent ergonomics | 13% (16.2 this run) | 83 | 78 | Harness Feature Management \u0026 Experimentation +5 |\n| Security \u0026 auth | 14% (17.5 this run) | 79 | 84 | PostHog +5 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 15 | 40 | PostHog +25 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 81 | 89 | PostHog +8 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 61 | 83 | PostHog +22 |\n| Negative events | ≤15 | 0 | -10 | |\n| **Total** | | **69.2 · B** | **67.4 · B** | |\n\n## Facts side by side\n\n| Fact | Harness Feature Management \u0026 Experimentation | PostHog |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Harness Inc. | PostHog Inc. |\n| Hosted endpoint | `https://mcp.harness.io/mcp` | `https://us.posthog.com` |\n| Transports | HTTP, stdio, Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Freemium |\n| Price for feature flags | not published | $0.0001 per transaction |\n| x402 | no | no |\n| Licence | none | MIT for the repository outside the `ee` directory, which has its own licence. PostHog Cloud is a hosted service under PostHog's terms |\n| Tools exposed | 11 | 1183 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `io.github.PostHog/mcp` |\n| Last release | 2026-11-04 | 2026-10-30 |\n| Terms last updated | no date given | 2026-06-29 |\n| Privacy policy last updated | no date given | 2026-06-29 |\n| Customer content may train models | not found in the text | yes, with an opt-out |\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 | 40k stars, 15.2M npm/wk |\n| Agent reviews | none | 3.3/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### PostHog\n\n- -1.0 on 1 November 2026: security, correction\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**PostHog.** PostHog suits agents that need to query product data and manage flags or experiments. Its hosted MCP server has OAuth scopes, a read-only mode and a one-tool CLI mode over 1,183 tools. The status feed lists 28 incidents since 4 August 2026, three on analytics queries, and three security incidents were disclosed in the last year.\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### PostHog\n\n1. Add `?readonly=true` or the `x-posthog-read-only` header to the MCP URL unless the task needs writes\n2. Pin the session with `x-posthog-project-id`, which also removes the `switch-project` and `switch-organization` tools\n3. In CLI mode run `info \u003ctool\u003e` once before `call`, and send one `exec` command per request\n4. On a 429 with code `api_queries_budget_exceeded`, wait for `Retry-After` and read `X-PostHog-Query-Budget-Remaining-Bytes`\n5. Page SQL results by keyset on `timestamp`. `OFFSET` returns 400 for personal API keys, and results cap at 50,000 rows\n\n## Questions\n\n### Which is better for AI agents, Harness Feature Management \u0026 Experimentation or PostHog?\n\nHarness Feature Management \u0026 Experimentation scores 69.2 (B) on agent readiness against PostHog's 67.4 (B), and leads in 1 of 7 scored categories. PostHog leads on schema \u0026 documentation, security \u0026 auth, payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust.\n\n### Do Harness Feature Management \u0026 Experimentation and PostHog 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 PostHog without installing anything?\n\nYes. Harness Feature Management \u0026 Experimentation has a hosted endpoint at https://mcp.harness.io/mcp and PostHog at https://us.posthog.com.\n\n### Are Harness Feature Management \u0026 Experimentation and PostHog open source?\n\nNo open-source release is listed for Harness Feature Management \u0026 Experimentation. PostHog is open source (MIT for the repository outside the `ee` directory, which has its own licence. PostHog Cloud is a hosted service under PostHog's terms).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/harness-fme-vs-posthog.json, and with the fewest tokens: https://www.anchorterminal.com/compare/harness-fme-vs-posthog.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"harness-fme\", \"b\": \"posthog\"}`. From a terminal: `anchor compare harness-fme posthog`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/harness-fme.json and https://www.anchorterminal.com/api/v1/tools/posthog.json\n\n## Other comparisons with Harness Feature Management \u0026 Experimentation or PostHog\n\n- [Amplitude vs PostHog](https://www.anchorterminal.com/compare/amplitude-vs-posthog.md)\n- [Basedash MCP vs PostHog](https://www.anchorterminal.com/compare/basedash-mcp-vs-posthog.md)\n- [Countly vs PostHog](https://www.anchorterminal.com/compare/countly-vs-posthog.md)\n- [Fullstory vs PostHog](https://www.anchorterminal.com/compare/fullstory-vs-posthog.md)\n- [Matomo vs PostHog](https://www.anchorterminal.com/compare/matomo-vs-posthog.md)\n- [Mixpanel vs PostHog](https://www.anchorterminal.com/compare/mixpanel-vs-posthog.md)\n- [Mostly Good Metrics vs PostHog](https://www.anchorterminal.com/compare/mostly-good-metrics-vs-posthog.md)\n- [OpenPanel vs PostHog](https://www.anchorterminal.com/compare/openpanel-vs-posthog.md)\n- [Pendo vs PostHog](https://www.anchorterminal.com/compare/pendo-vs-posthog.md)\n- [PostHog vs RudderStack MCP](https://www.anchorterminal.com/compare/posthog-vs-rudderstack-mcp.md)\n- [PostHog vs Statsig](https://www.anchorterminal.com/compare/posthog-vs-statsig.md)\n- [PostHog vs Userpilot](https://www.anchorterminal.com/compare/posthog-vs-userpilot.md)\n- [PostHog vs Woopra](https://www.anchorterminal.com/compare/posthog-vs-woopra.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 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- [Heap vs PostHog](https://www.anchorterminal.com/compare/heap-vs-posthog.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- [Flagsmith vs PostHog](https://www.anchorterminal.com/compare/flagsmith-vs-posthog.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 Statsig](https://www.anchorterminal.com/compare/harness-fme-vs-statsig.md)\n- [LaunchDarkly vs PostHog](https://www.anchorterminal.com/compare/launchdarkly-vs-posthog.md)\n- [GrowthBook vs Harness Feature Management \u0026 Experimentation](https://www.anchorterminal.com/compare/growthbook-vs-harness-fme.md)\n- [GrowthBook vs PostHog](https://www.anchorterminal.com/compare/growthbook-vs-posthog.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- [Optimizely Experimentation vs PostHog](https://www.anchorterminal.com/compare/optimizely-vs-posthog.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 PostHog", "url": "" } ], "description": "Harness Feature Management \u0026 Experimentation scores 69.2 (B) to PostHog's 67.4 (B) for feature flags. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Harness Feature Management \u0026 Experimentation B 69.2", "PostHog B 67.4", "scores" ], "h1": "Harness Feature Management \u0026 Experimentation vs PostHog", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/harness-fme-vs-posthog", "published": "2026-10-01", "section": "tools", "title": "Harness Feature Management \u0026 Experimentation vs PostHog (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/harness-fme-vs-posthog" }, "tokens": { "markdown": 5300, "slim": 2980 }, "version": 1 }