# Harness Feature Management & Experimentation > Harness Feature Management & 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. - Canonical: https://www.anchorterminal.com/tools/harness-fme - Pricing: https://www.anchorterminal.com/tools/harness-fme#pricing - Reviews: https://www.anchorterminal.com/tools/harness-fme#reviews - Markdown: https://www.anchorterminal.com/tools/harness-fme.md (~7,450 tokens) - Slim: https://www.anchorterminal.com/tools/harness-fme.min.md (~1,580 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/harness-fme.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key) - DNS: dig +short TXT harness-fme.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.. and .vs.. under the zone, and the same under grade.letme.dev) - Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data) - Updated: 2026-11-07 ## Overview **Grade B · 69.2/100 · rank #257 of 1486 · #4 in Product analytics & experimentation · not agent-ready · confidence medium** ## Assessment 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. ## Facts | Field | Value | | --- | --- | | Vendor | Harness Inc. (https://www.harness.io) | | Kind | HTTP API | | Category | Product analytics & experimentation (https://www.anchorterminal.com/categories/product-analytics) | | Transport | HTTP, stdio, Streamable HTTP | | Endpoint | `https://mcp.harness.io/mcp` | | Auth | OAuth or key · 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 (Freemium) · 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. | | x402 | No · No x402, MPP or L402 in the FME docs, the Split API reference or harness.io/pricing (checked 2026-11-06). | | Licence | unknown | | Tools exposed | 11 | | Packages | npm: `harness-mcp-v2` | | Source | https://github.com/harness/mcp-server | | Docs | https://developer.harness.io/feature-management-experimentation/feature-management-and-experimentation-documentation | | llms.txt | https://developer.harness.io/llms.txt | | Last release | 2026-11-04 | | npm downloads / week | 8,800 | | Surface listed | The FME Admin API at api.split.io (reference at docs.split.io) and the FME toolset of the Harness MCP server, local through npm or hosted at mcp.harness.io, read from developer.harness.io, docs.split.io, the harness/mcp-server repository, harness.io pricing, security and privacy pages and status.harness.io on 6 November 2026. No account was made and no tool was called | | Which product | Split Software's feature flag and experimentation platform, part of Harness since 2024 and sold as the FME module. Harness also has an older Feature Flags (FF) module, a separate product on the same status page | | FME resource types | fme_workspace, fme_environment, fme_feature_flag (list, get, create, update, delete, kill, restore, archive), fme_feature_flag_definition, fme_rule_based_segment, fme_rule_based_segment_definition and fme_rollout_status | | Admin API | Projects, environments, feature flags and definitions, segments, rule-based and large segments, change requests, identities, attributes, events, flag sets, groups, restrictions and API keys, with a Postman collection, a Python wrapper and a CLI | | Skills | The harness-fme Claude Code plugin packages 16 skills for flags, segments, metrics, experiments and rollout pipelines | | Rate limits | About 20 Admin API requests per 10 seconds per organisation and per IP; SDK evaluation traffic is not limited by it | | Legal entity | Harness Inc., 55 Stockton St, 8th Floor, San Francisco, per the privacy statement | | 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 | | JSON | https://www.anchorterminal.com/api/v1/tools/harness-fme.json | ## Score breakdown (methodology v0.7, October 2026 research run) Assessed 2026-11-06 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 80 | 16.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 71 | 11.5 | | Agent ergonomics | 13% | 16.2 | 83 | 13.5 | | Security & auth | 14% | 17.5 | 79 | 13.8 | | Payments & pricing | 10% | 12.5 | 15 | 1.9 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 81 | 7.1 | | Transparency & trust (editorial 60, provenance 61) | 7% | 8.8 | 61 | 5.3 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **69.2 → B** | ### Why each score - Reliability 80 (checked 2026-11-06): 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. - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 71 (checked 2026-11-06): 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. - Agent ergonomics 83 (checked 2026-11-06): 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. - Security & auth 79 (checked 2026-11-06): 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. - Payments & pricing 15 (checked 2026-11-06): 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. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 81 (checked 2026-11-06): 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. - Transparency & trust 61 (checked 2026-11-06): 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. Fix list, everything this grade says the listing lacks, the biggest gain first (18 items). What it covers is at https://www.anchorterminal.com/fixes/harness-fme.md (JSON https://www.anchorterminal.com/fixes/harness-fme.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{"listing": "harness-fme", "plan": "read"}`, free while the beta runs ### What we couldn't check - Disclosure. On 6 November 2026 we read https://status.harness.io/api/v2/incidents.json and components.json before reading robots.txt, which disallows /api/ on that host. Both FME incidents were then confirmed on the allowed /history pages. - unchecked: FME Free Plan limits and whether a card is needed, which aren't published - unchecked: the sub-processor list on trust.harness.io, which wasn't read - unchecked: GitHub issue response times on harness/mcp-server, because the GitHub API refused us for its rate limit - Whether the harness/mcp-server package is published in the official MCP registry; a search for harness namespaces found none - The FME MCP docs page and the repository README disagree on how to install the server ### Sources - FME MCP tools: (seen 2026-11-06) - Harness MCP server repository: (seen 2026-11-06) - FME API best practices: (seen 2026-11-06) - Admin API authentication: (seen 2026-11-06) - Admin API key roles: (seen 2026-11-06) - Admin API rate limiting: (seen 2026-11-06) - Admin API error codes: (seen 2026-11-06) - status history: (seen 2026-11-06) - pricing: (seen 2026-11-06) - start FME free plan: (seen 2026-11-06) - security page: (seen 2026-11-06) - privacy statement: (seen 2026-11-06) - npm package: (seen 2026-11-06) ## Score history Every move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/harness-fme/history.json - 2026-11-06: graded 69.2 B (methodology 0.7) ## Who's behind it (provenance 61/100, checked 2026-11-06) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Harness Inc. | 20/20 | | Domain age | harness.io, no registry record we could read | 0/15 | | Endpoint on the vendor's domain | mcp.harness.io is not on harness.io | 0/15 | | Terms of service | read, states 5 of the 7 things a reader expects, and has 1 clause that costs points | 6.3/10 | | Privacy policy | read, states 7 of the 8 things a reader expects | 9.3/10 | | Status page | status.harness.io | 10/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | | People named | 2 named with their role, 1 with a public profile | 10/10 | | Support route | a support address, help pages, a community | 5/5 | 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. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://www.harness.io/legal/subscription-terms), read 2026-11-06, gives no date, states 5 of the 7 things a reader expects. - To know. Restricts benchmarking or competitive use (costs points). "…interfere with its operation, or circumvent its access restrictions or (e) use the Harness Platform to develop a competing product." - To know. Says access can be ended without notice or for any reason. "Either party may terminate access at any time." - Not found in the text. Gives the date it was last updated. - Names the governing law or courts. The law of the State of California. - States a limit on its liability. Capped at $1,000. - Not found in the text. Says how changes to the terms are announced. **Privacy policy** (https://www.harness.io/legal/privacy), read 2026-11-06, gives no date, states 7 of the 8 things a reader expects. - Not found in the text. Gives the date it was last updated. - Says how long data is kept. For as long as needed, with no period named. - Says where data is transferred or stored. Relies on the Data Privacy Framework. ## Humans behind the project (researched 2026-11-06 from public pages, not part of the grade) ### Key people - Jyoti Bansal, Co-Founder & CEO. LinkedIn: https://www.linkedin.com/in/jyotibansal/ - Rishi Singh, Co-Founder & Board Member - Note: Harness's about page names Jyoti Bansal as Co-Founder & CEO, with his LinkedIn, and Rishi Singh as Co-Founder & Board Member; the Series A release (October 2017) calls Rishi Singh CTO and co-founder. FME is the former Split Software, acquired by Harness in May 2024 per Harness's press page. Investors and rounds are from Harness's own press releases: Series A (October 2017, $20M led by Menlo Ventures and BIG Labs), Series B (2019, $60M led by IVP, GV and ServiceNow Ventures), Series C and B-1 (January 2021, $115M, $1.7B valuation), Series D (April 2022, $230M at $3.7B, led by Norwest) and Series E (11 December 2025, $240M led by Goldman Sachs Alternatives, including a $40M tender offer, valuing Harness at $5.5B). The about page says Harness has raised $570M and shows the same investors' logos. Silicon Valley Bank, named among existing investors in the Series D release, and Hercules Capital provided the $150M financing of May 2024, which the releases describe as debt, so neither is listed as an investor. Harness also announced its acquisition of Augment Code on 8 October 2026. - Harness Inc.: LinkedIn https://www.linkedin.com/company/harnessinc X https://x.com/harnessio GitHub https://github.com/harness ### Ownership and investors - Raised: $570M in total, as of November 2026 (source https://www.harness.io/company/about-us) - Valuation: $5.5B as announced (the source doesn't say pre- or post-money), Series E, December 2025, December 2025 (source https://www.harness.io/press-and-news/harness-announces-240m-financing-round-led-by-goldman-sachs) - Backed by: Menlo Ventures, BIG Labs, IVP, GV, ServiceNow, Unusual Ventures, Alkeon Capital, Battery Ventures, Citi, Norwest, Sorenson Capital, Thomvest Ventures, J.P. Morgan, Capital One, Splunk, Adage Capital Partners, Balyasny Asset Management, Gaingels, Harmonic Growth Partners, Goldman Sachs ### Getting support - Support email: security@harness.io - Help: https://developer.harness.io/feature-management-experimentation/feature-management-and-experimentation-documentation - Help: https://status.harness.io - Community (Harness MCP server issues): https://github.com/harness/mcp-server/issues - Sources: https://www.harness.io/company/about-us, https://www.harness.io/press-and-news/harness-acquires-split-software-to-enhance-feature-management, https://www.harness.io/press-and-news/harness-announces-60m-series-b-financing-from-ivp-gv-and-servicenow, https://www.harness.io/company/security, https://www.harness.io/legal/privacy, https://www.harness.io/press-and-news/harness-launches-with-20-million-series-a-to-simplify-continuous-delivery-using-artificial-intelligence, https://www.harness.io/press-and-news/harness-reaches-1-7-billion-valuation-with-115-million-in-new-financing, https://www.harness.io/press-and-news/harness-valuation-soars-to-3-7-billion-with-230-million-in-series-d-funding, https://www.harness.io/press-and-news/harness-announces-240m-financing-round-led-by-goldman-sachs ## Live (updated 2026-11-07 18:21 UTC) - Right now: up, HTTP 401, 211 ms, checked 2026-11-07 18:20 UTC (get on `https://mcp.harness.io/mcp`, asks for auth) - Uptime 24h 100.0% (200 probes) · 30 days 100.0% (200 probes) · p50 195 ms · p95 280 ms - Vendor status page: no problems reported, All Systems Operational - github `harness/mcp-server` v3.2.40, released 2026-11-05 - npm `harness-mcp-v2` 3.2.40 - security.txt: none - Watching privacy - Watching terms - Always current: https://www.anchorterminal.com/api/v1/live/harness-fme.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## 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 ## Before you call it (notes for agents) 1. Start the MCP server with `--toolsets=fme` so only FME resource types load 2. Call `harness_describe(resource_type='fme_feature_flag')` before a create or update to see the fields 3. Filter fme_feature_flag lists by name, tags or rollout status rather than listing every flag 4. Set HARNESS_READ_ONLY for analysis tasks; leave confirmation on for kill, restore and delete 5. On 429, wait at least the larger X-RateLimit-Reset-Seconds value before retrying ## Connect Install: ```bash npx harness-mcp-v2@latest ``` MCP client configuration: ```json { "mcpServers": { "harness": { "args": [ "harness-mcp-v2@latest", "--toolsets=fme" ], "command": "npx", "env": { "HARNESS_API_KEY": "pat.xxx" } } } } ``` Through letme: https://letme.dev/harness-fme. letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Statsig | BB | 72.4 | 127 | analytics.experiments, analytics.flags, analytics.events | no | https://www.anchorterminal.com/tools/statsig.md | | Amplitude | B | 69.3 | 249 | analytics.experiments, analytics.flags, analytics.events | no | https://www.anchorterminal.com/tools/amplitude.md | | GrowthBook | B | 68.6 | 278 | analytics.experiments, analytics.flags, analytics.events | no | https://www.anchorterminal.com/tools/growthbook.md | | PostHog | B | 67.4 | 327 | analytics.events, analytics.experiments, analytics.flags | no | https://www.anchorterminal.com/tools/posthog.md | | Mixpanel | B | 62 | 577 | analytics.events, analytics.experiments, analytics.flags | no | https://www.anchorterminal.com/tools/mixpanel.md | | Flagsmith | C | 61.2 | 620 | analytics.flags, analytics.experiments, analytics.events | no | https://www.anchorterminal.com/tools/flagsmith.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The Harness MCP server 2.0 exposes 11 generic tools (harness_list, harness_get, harness_create, harness_update, harness_delete, harness_execute and others) over 269 resource types, and `--toolsets=fme` limits it to seven FME resource types (source: ) - The Admin API allows about 20 requests per 10-second window per organisation and per IP, returns 429 with X-RateLimit-Remaining and X-RateLimit-Reset-Seconds headers, and the MCP server retries 429s with exponential backoff up to 3 times (source: ) - HARNESS_READ_ONLY blocks every create, update, delete and execute call, and writes ask for confirmation by MCP elicitation unless HARNESS_AUTO_APPROVE_RISK allows them (source: ) - harness-mcp-v2 3.2.40 on npm, MIT, 14 tagged releases between 8 August and 4 November 2026 (source: ) - Harness announced its acquisition of Split Software in May 2024; Split's pricing URL now redirects to harness.io/pricing (source: ) - The FME MCP docs page still tells readers to build a Go binary from source, while the repository is now a TypeScript package run with npx (source: ) - #4 of 18 in Best product analytics and experimentation tools for AI agents: https://www.anchorterminal.com/best/product-analytics/index.md - All 153 product analytics comparisons: https://www.anchorterminal.com/compare/product-analytics/index.md ## Compare - [Amplitude vs Harness Feature Management & Experimentation](https://www.anchorterminal.com/compare/amplitude-vs-harness-fme.md): B 69.3 vs B 69.2 - [Countly vs Harness Feature Management & Experimentation](https://www.anchorterminal.com/compare/countly-vs-harness-fme.md): E 38.8 vs B 69.2 - [Flagsmith vs Harness Feature Management & Experimentation](https://www.anchorterminal.com/compare/flagsmith-vs-harness-fme.md): C 61.2 vs B 69.2 - [Harness Feature Management & Experimentation vs LaunchDarkly](https://www.anchorterminal.com/compare/harness-fme-vs-launchdarkly.md): B 69.2 vs BB 71.3 - [Harness Feature Management & Experimentation vs Mixpanel](https://www.anchorterminal.com/compare/harness-fme-vs-mixpanel.md): B 69.2 vs B 62 - [Harness Feature Management & Experimentation vs Optimizely Experimentation](https://www.anchorterminal.com/compare/harness-fme-vs-optimizely.md): B 69.2 vs B 64.9 - [Harness Feature Management & Experimentation vs PostHog](https://www.anchorterminal.com/compare/harness-fme-vs-posthog.md): B 69.2 vs B 67.4 - [Harness Feature Management & Experimentation vs Statsig](https://www.anchorterminal.com/compare/harness-fme-vs-statsig.md): B 69.2 vs BB 72.4 - [Fullstory vs Harness Feature Management & Experimentation](https://www.anchorterminal.com/compare/fullstory-vs-harness-fme.md): B 63.3 vs B 69.2 - [Harness Feature Management & Experimentation vs Heap](https://www.anchorterminal.com/compare/harness-fme-vs-heap.md): B 69.2 vs D 48.2 - [Harness Feature Management & Experimentation vs OpenPanel](https://www.anchorterminal.com/compare/harness-fme-vs-openpanel.md): B 69.2 vs C 61 - [Harness Feature Management & Experimentation vs Woopra](https://www.anchorterminal.com/compare/harness-fme-vs-woopra.md): B 69.2 vs E 44.4 - [GrowthBook vs Harness Feature Management & Experimentation](https://www.anchorterminal.com/compare/growthbook-vs-harness-fme.md): B 68.6 vs B 69.2 - [Harness Feature Management & Experimentation vs Matomo](https://www.anchorterminal.com/compare/harness-fme-vs-matomo.md): B 69.2 vs C 61.7 - [Harness Feature Management & Experimentation vs Mostly Good Metrics](https://www.anchorterminal.com/compare/harness-fme-vs-mostly-good-metrics.md): B 69.2 vs E 41.7 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on harness.io or one of its subdomains, or the README at the root of github.com/harness/mcp-server. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "harness-fme", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Harness Feature Management & Experimentation on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Harness Feature Management & Experimentation on Anchor Terminal](https://www.anchorterminal.com/badges/harness-fme.svg)](https://www.anchorterminal.com/tools/harness-fme) ``` Plain link: ```html Harness Feature Management & Experimentation on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Harness Feature Management & Experimentation is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/harness-fme-dark.png - Light: https://www.anchorterminal.com/assets/share/harness-fme-light.png --- Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp