{ "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" }, "tool": { "slug": "harness-fme", "name": "Harness Feature Management \u0026 Experimentation", "vendor": "Harness Inc.", "vendorUrl": "https://www.harness.io", "kind": "http-api", "category": "product-analytics", "summary": "Harness Feature Management \u0026 Experimentation (FME), formerly Split, manages feature flags, targeting, metrics and experiments. Agents reach it through the Admin API at api.split.io and the FME toolset of the Harness MCP server.", "url": "https://www.anchorterminal.com/tools/harness-fme", "markdownUrl": "https://www.anchorterminal.com/tools/harness-fme.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/harness-fme.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/harness-fme.json", "dns": "harness-fme.grade.anchorterminal.com", "repo": "https://github.com/harness/mcp-server", "transports": [ "http", "stdio", "streamable-http" ], "remoteUrl": "https://mcp.harness.io/mcp", "packages": [ { "registry": "npm", "name": "harness-mcp-v2" } ], "auth": "mixed", "authNotes": "The Admin API takes an Admin API key as a Bearer token, or a Harness personal access token (PAT) or service account token (SAT) in `x-api-key`. Admin keys carry fixed roles that can be combined and cannot be edited after creation, and a key cannot create another with more roles. The local MCP server reads HARNESS_API_KEY. The hosted MCP endpoint uses Harness Platform OAuth and must be enabled per account by Harness Support.", "pricing": "freemium", "pricingNotes": "An FME Free Plan is enabled from inside a Harness account; its limits are not published. The Enterprise plan and FME pricing are by quotation through sales. No FME prices appear on harness.io/pricing.", "priceSummary": "Freemium", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the FME docs, the Split API reference or harness.io/pricing (checked 2026-11-06).", "endpoints": [] }, "toolCount": 11, "popularity": { "githubStars": null, "npmWeekly": 8800, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://developer.harness.io/feature-management-experimentation/feature-management-and-experimentation-documentation", "llmsTxt": "https://developer.harness.io/llms.txt", "capabilities": [ "analytics.flags", "analytics.experiments", "analytics.events" ], "tags": [ "official", "hosted", "mcp", "remote-mcp", "oauth", "llms-txt", "free-tier", "sales-led", "status-page", "soc2", "iso27001", "typescript", "python", "cli", "closed-source" ], "lastRelease": "2026-11-04", "graded": true, "anchor": { "graded": true, "score": 69.2, "grade": "B", "agentReady": false, "rank": 257, "ranked": true, "rankOf": 1486, "categoryRank": 4, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 83, "maintenance": 81, "payments": 15, "reliability": 80, "schema": 71, "security": 79, "transparency": 61 }, "pending": [ "performance", "tasks" ], "breakdown": [ { "key": "reliability", "name": "Reliability", "weight": 16, "effectiveWeight": 20, "score": 80, "points": 16, "reason": "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.", "checked": "2026-11-06" }, { "key": "performance", "name": "Performance", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "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." }, { "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "effectiveWeight": 16.25, "score": 71, "points": 11.54, "reason": "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.", "checked": "2026-11-06" }, { "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "effectiveWeight": 16.25, "score": 83, "points": 13.49, "reason": "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.", "checked": "2026-11-06" }, { "key": "security", "name": "Security \u0026 auth", "weight": 14, "effectiveWeight": 17.5, "score": 79, "points": 13.83, "reason": "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.", "checked": "2026-11-06" }, { "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "effectiveWeight": 12.5, "score": 15, "points": 1.88, "reason": "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.", "checked": "2026-11-06" }, { "key": "tasks", "name": "Task success", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "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." }, { "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "effectiveWeight": 8.75, "score": 81, "points": 7.09, "reason": "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.", "checked": "2026-11-06" }, { "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "effectiveWeight": 8.75, "score": 61, "points": 5.34, "note": "editorial 60, provenance 61", "reason": "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.", "checked": "2026-11-06" } ], "assessment": { "date": "2026-11-06", "basis": "public evidence", "confidence": "medium", "notes": { "ergonomics": "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.", "maintenance": "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.", "payments": "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.", "reliability": "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.", "schema": "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.", "security": "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.", "transparency": "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." }, "sources": [ { "what": "FME MCP tools", "url": "https://developer.harness.io/feature-management-experimentation/use-fme/release-agent/mcp-tools.md", "seen": "2026-11-06" }, { "what": "Harness MCP server repository", "url": "https://github.com/harness/mcp-server", "seen": "2026-11-06" }, { "what": "FME API best practices", "url": "https://developer.harness.io/feature-management-experimentation/management-and-administration/api-best-practices.md", "seen": "2026-11-06" }, { "what": "Admin API authentication", "url": "https://docs.split.io/reference/authentication.md", "seen": "2026-11-06" }, { "what": "Admin API key roles", "url": "https://docs.split.io/reference/api-keys-overview.md", "seen": "2026-11-06" }, { "what": "Admin API rate limiting", "url": "https://docs.split.io/reference/rate-limiting.md", "seen": "2026-11-06" }, { "what": "Admin API error codes", "url": "https://docs.split.io/reference/error-codes.md", "seen": "2026-11-06" }, { "what": "status history", "url": "https://status.harness.io/history", "seen": "2026-11-06" }, { "what": "pricing", "url": "https://www.harness.io/pricing", "seen": "2026-11-06" }, { "what": "start FME free plan", "url": "https://developer.harness.io/feature-management-experimentation/new-to-fme/split-and-harness.md", "seen": "2026-11-06" }, { "what": "security page", "url": "https://www.harness.io/company/security", "seen": "2026-11-06" }, { "what": "privacy statement", "url": "https://www.harness.io/legal/privacy", "seen": "2026-11-06" }, { "what": "npm package", "url": "https://registry.npmjs.org/harness-mcp-v2/latest", "seen": "2026-11-06" } ], "openQuestions": [ "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" ] }, "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 }, "scoreHistory": [ { "date": "2026-11-06", "grade": "B", "kind": "listed", "method": "0.7", "score": 69.2 } ] }, "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" }, "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 (https://github.com/harness/mcp-server)", "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 (https://developer.harness.io/feature-management-experimentation/use-fme/release-agent/mcp-tools.md)", "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 (https://github.com/harness/mcp-server/blob/main/README.md)", "harness-mcp-v2 3.2.40 on npm, MIT, 14 tagged releases between 8 August and 4 November 2026 (https://registry.npmjs.org/harness-mcp-v2/latest)", "Harness announced its acquisition of Split Software in May 2024; Split's pricing URL now redirects to harness.io/pricing (https://www.harness.io/press-and-news/harness-acquires-split-software-to-enhance-feature-management)", "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 (https://developer.harness.io/feature-management-experimentation/use-fme/release-agent/mcp-tools.md)" ], "area": "business", "details": [ { "label": "Surface listed", "value": "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" }, { "label": "Which product", "value": "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" }, { "label": "FME resource types", "value": "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" }, { "label": "Admin API", "value": "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" }, { "label": "Skills", "value": "The harness-fme Claude Code plugin packages 16 skills for flags, segments, metrics, experiments and rollout pipelines" }, { "label": "Rate limits", "value": "About 20 Admin API requests per 10 seconds per organisation and per IP; SDK evaluation traffic is not limited by it" }, { "label": "Legal entity", "value": "Harness Inc., 55 Stockton St, 8th Floor, San Francisco, per the privacy statement" } ], "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, "checks": [ { "check": "Legal entity named", "value": "Harness Inc.", "points": 20, "max": 20, "state": "ok" }, { "check": "Domain age", "value": "harness.io, no registry record we could read", "points": 0, "max": 15, "state": "no" }, { "check": "Endpoint on the vendor's domain", "value": "mcp.harness.io is not on harness.io", "points": 0, "max": 15, "state": "no" }, { "check": "Terms of service", "value": "read, states 5 of the 7 things a reader expects, and has 1 clause that costs points", "points": 6.3, "max": 10, "state": "part" }, { "check": "Privacy policy", "value": "read, states 7 of the 8 things a reader expects", "points": 9.3, "max": 10, "state": "part" }, { "check": "Status page", "value": "status.harness.io", "points": 10, "max": 10, "state": "ok" }, { "check": "Changelog", "value": "published", "points": 10, "max": 10, "state": "ok" }, { "check": "security.txt", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "People named", "value": "2 named with their role, 1 with a public profile", "points": 10, "max": 10, "state": "ok" }, { "check": "Support route", "value": "a support address, help pages, a community", "points": 5, "max": 5, "state": "ok" } ], "policies": [ { "kind": "terms", "url": "https://www.harness.io/legal/subscription-terms", "state": "read", "readAt": "2026-11-06", "words": 5498, "points": 6.3, "max": 10, "expected": [ { "key": "terms.date", "label": "Gives the date it was last updated", "found": false }, { "key": "terms.law", "label": "Names the governing law or courts", "found": true, "quote": "The laws of the State of California govern this Agreement and any action arising out of or relating to this Agreement, without reference to conflict of law rules.", "says": "The law of the State of California" }, { "key": "terms.liability", "label": "States a limit on its liability", "found": true, "quote": "NOTWITHSTANDING ANYTHING ELSE IN THIS AGREEMENT, NO WARRANTIES, INDEMNITIES, SLAS, OR SUPPORT APPLY TO TRIALS AND BETAS AND HARNESS’S LIABILITY FOR TRIALS AND BETAS IS LIMITED TO $1,000.", "says": "Capped at $1,000" }, { "key": "terms.termination", "label": "Says how the agreement or account can be ended", "found": true, "quote": "Harness may suspend access to the Harness Platform and performance of any Professional Services if it does not receive payment from the Sales Partner." }, { "key": "terms.changes", "label": "Says how changes to the terms are announced", "found": false }, { "key": "terms.use", "label": "Lists what users may not do", "found": true, "quote": "Customer will not and will not permit anyone else to: (a) resell or sublicense the Harness Platform (in whole or part), grant non-Users access to the Harness Platform, or use the Harness Platform to provide a hosted or managed service, (b) reverse engineer, decompile, or seek to access the source code of the Harness P…" }, { "key": "terms.sla", "label": "Refers to a service level or uptime commitment", "found": true, "quote": "Harness will provide support for the applicable Module at service levels as described in the applicable Order Form and Support Terms and SLA, available at https://www.harness.io/legal/support-policy-sla (“Support”)." } ], "toKnow": [ { "key": "terms.benchmark", "label": "Restricts benchmarking or competitive use", "found": true, "quote": "…interfere with its operation, or circumvent its access restrictions or (e) use the Harness Platform to develop a competing product.", "costsPoints": true }, { "key": "terms.cutoff", "label": "Says access can be ended without notice or for any reason", "found": true, "quote": "Either party may terminate access at any time." } ] }, { "kind": "privacy", "url": "https://www.harness.io/legal/privacy", "state": "read", "readAt": "2026-11-06", "words": 2296, "points": 9.3, "max": 10, "expected": [ { "key": "privacy.date", "label": "Gives the date it was last updated", "found": false }, { "key": "privacy.collected", "label": "Says what personal data is collected", "found": true, "quote": "This statement explains how we collect, use, share, and protect personal data when you:" }, { "key": "privacy.retention", "label": "Says how long data is kept", "found": true, "quote": "As long as needed to manage our relationship with you", "says": "For as long as needed, with no period named" }, { "key": "privacy.processors", "label": "Says who else receives the data", "found": true, "quote": "Third parties and partners: From your employer, event organizers, marketing agencies, sponsors, and our trusted service providers and data enrichment vendors (such as CRM and professional contact platforms)." }, { "key": "privacy.sale", "label": "Says whether personal data is sold or shared for advertising", "found": true, "quote": "You can opt out of targeted advertising, “sale,” and “sharing,” and appeal a denied request where state law provides for it." }, { "key": "privacy.rights", "label": "Says what rights people have over their data", "found": true, "quote": "Data Subject rights depend on where you are located." }, { "key": "privacy.contact", "label": "Gives a privacy contact", "found": true, "quote": "Depending on your interaction with Harness, different parts of this Privacy Statement may be relevant to you." }, { "key": "privacy.transfers", "label": "Says where data is transferred or stored", "found": true, "quote": "Data Privacy Framework and its UK and Swiss extensions, where the recipient is certified;", "says": "Relies on the Data Privacy Framework" } ] } ] }, "humans": { "slug": "harness-fme", "checked": "2026-11-06", "company": "Harness Inc.", "people": [ { "name": "Jyoti Bansal", "role": "Co-Founder \u0026 CEO", "founder": true, "linkedin": "https://www.linkedin.com/in/jyotibansal/", "page": "/people/jyoti-bansal/" }, { "name": "Rishi Singh", "role": "Co-Founder \u0026 Board Member", "founder": true, "page": "/people/rishi-singh/" } ], "peopleNote": "Harness's about page names Jyoti Bansal as Co-Founder \u0026 CEO, with his LinkedIn, and Rishi Singh as Co-Founder \u0026 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.", "companySocial": { "linkedin": "https://www.linkedin.com/company/harnessinc", "x": "https://x.com/harnessio", "github": "https://github.com/harness" }, "support": { "emails": [ "security@harness.io" ], "urls": [ "https://developer.harness.io/feature-management-experimentation/feature-management-and-experimentation-documentation", "https://status.harness.io" ], "community": [ { "label": "Harness MCP server issues", "url": "https://github.com/harness/mcp-server/issues", "kind": "github" } ], "contactUrls": [ "https://www.harness.io/company/contact-sales" ] }, "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" ], "ownership": { "status": "private", "totalRaised": { "amount": "$570M", "asOf": "2026-11", "source": "https://www.harness.io/company/about-us" }, "valuation": { "amount": "$5.5B", "basis": "stated", "round": "Series E, December 2025", "asOf": "2025-12-11", "source": "https://www.harness.io/press-and-news/harness-announces-240m-financing-round-led-by-goldman-sachs" }, "checked": "2026-11-06", "sources": [ "https://www.harness.io/company/about-us", "https://www.harness.io/press-and-news/harness-announces-240m-financing-round-led-by-goldman-sachs", "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-reaches-1-7-billion-valuation-with-115-million-in-new-financing", "https://www.harness.io/press-and-news/harness-announces-60m-series-b-financing-from-ivp-gv-and-servicenow", "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-acquires-split-software-to-enhance-feature-management" ] }, "investors": [ { "name": "Menlo Ventures", "kind": "vc", "rounds": [ "Series A, October 2017", "Series B, 2019", "Series B-1, January 2021", "Series D, April 2022", "Series E, December 2025 (tender offer)" ], "lead": true, "url": "https://menlovc.com", "source": "https://www.harness.io/press-and-news/harness-launches-with-20-million-series-a-to-simplify-continuous-delivery-using-artificial-intelligence", "quote": "launched from stealth today with $20 million in Series A funding led by Menlo Ventures and BIG Labs", "page": "/investors/menlo-ventures/" }, { "name": "BIG Labs", "kind": "other", "rounds": [ "Series A, October 2017" ], "lead": true, "source": "https://www.harness.io/press-and-news/harness-launches-with-20-million-series-a-to-simplify-continuous-delivery-using-artificial-intelligence", "quote": "launched from stealth today with $20 million in Series A funding led by Menlo Ventures and BIG Labs", "page": "/investors/big-labs/" }, { "name": "IVP", "kind": "vc", "rounds": [ "Series B, 2019", "Series B-1, January 2021", "Series D, April 2022", "Series E, December 2025 (tender offer)" ], "lead": true, "url": "https://www.ivp.com", "source": "https://www.harness.io/press-and-news/harness-announces-60m-series-b-financing-from-ivp-gv-and-servicenow", "quote": "closed a $60 million Series B funding round led by IVP, GV, and ServiceNow Ventures. Existing investors Menlo Ventures and Unusual Ventures also participated in the round.", "page": "/investors/ivp/" }, { "name": "GV", "kind": "vc", "rounds": [ "Series B, 2019", "Series D, April 2022" ], "lead": true, "url": "https://www.gv.com", "source": "https://www.harness.io/press-and-news/harness-announces-60m-series-b-financing-from-ivp-gv-and-servicenow", "quote": "closed a $60 million Series B funding round led by IVP, GV, and ServiceNow Ventures. Existing investors Menlo Ventures and Unusual Ventures also participated in the round.", "page": "/investors/gv/" }, { "name": "ServiceNow Ventures", "firm": "ServiceNow", "kind": "corporate", "rounds": [ "Series B, 2019", "Series D, April 2022" ], "lead": true, "url": "https://www.servicenow.com", "source": "https://www.harness.io/press-and-news/harness-announces-60m-series-b-financing-from-ivp-gv-and-servicenow", "quote": "closed a $60 million Series B funding round led by IVP, GV, and ServiceNow Ventures. Existing investors Menlo Ventures and Unusual Ventures also participated in the round.", "page": "/investors/servicenow/" }, { "name": "Unusual Ventures", "kind": "vc", "rounds": [ "Series B, 2019", "Series B-1, January 2021", "Series D, April 2022", "Series E, December 2025 (tender offer)" ], "lead": true, "url": "https://www.unusual.vc", "source": "https://www.harness.io/press-and-news/harness-reaches-1-7-billion-valuation-with-115-million-in-new-financing", "page": "/investors/unusual-ventures/" }, { "name": "Alkeon Capital", "kind": "vc", "rounds": [ "Series C, January 2021", "Series D, April 2022" ], "lead": true, "url": "https://www.alkeon.com", "source": "https://www.harness.io/press-and-news/harness-reaches-1-7-billion-valuation-with-115-million-in-new-financing", "page": "/investors/alkeon-capital/" }, { "name": "Battery Ventures", "kind": "vc", "rounds": [ "Series C, January 2021", "Series D, April 2022" ], "url": "https://www.battery.com", "source": "https://www.harness.io/press-and-news/harness-reaches-1-7-billion-valuation-with-115-million-in-new-financing", "page": "/investors/battery-ventures/" }, { "name": "Citi Ventures", "firm": "Citi", "kind": "corporate", "rounds": [ "Series C, January 2021", "Series D, April 2022" ], "url": "https://www.citi.com/ventures", "source": "https://www.harness.io/press-and-news/harness-reaches-1-7-billion-valuation-with-115-million-in-new-financing", "page": "/investors/citi/" }, { "name": "Norwest Venture Partners", "firm": "Norwest", "kind": "vc", "rounds": [ "Series C, January 2021", "Series D, April 2022" ], "lead": true, "url": "https://www.nvp.com", "source": "https://www.harness.io/press-and-news/harness-valuation-soars-to-3-7-billion-with-230-million-in-series-d-funding", "quote": "Norwest Venture Partners led the Series D round, with new investors J.P. Morgan, Capital One Ventures, Splunk Ventures, Adage Capital Partners, Balyasny Asset Management, Gaingels, Harmonic Growth Partners and all existing investors participating", "page": "/investors/norwest/" }, { "name": "Sorenson Capital", "kind": "vc", "rounds": [ "Series C, January 2021", "Series D, April 2022" ], "url": "https://www.sorensoncapital.com", "source": "https://www.harness.io/press-and-news/harness-reaches-1-7-billion-valuation-with-115-million-in-new-financing", "page": "/investors/sorenson-capital/" }, { "name": "Thomvest Ventures", "kind": "vc", "rounds": [ "Series C, January 2021", "Series D, April 2022" ], "source": "https://www.harness.io/press-and-news/harness-reaches-1-7-billion-valuation-with-115-million-in-new-financing", "page": "/investors/thomvest-ventures/" }, { "name": "J.P. Morgan", "kind": "corporate", "rounds": [ "Series D, April 2022" ], "url": "https://www.jpmorgan.com", "source": "https://www.harness.io/press-and-news/harness-valuation-soars-to-3-7-billion-with-230-million-in-series-d-funding", "quote": "Norwest Venture Partners led the Series D round, with new investors J.P. Morgan, Capital One Ventures, Splunk Ventures, Adage Capital Partners, Balyasny Asset Management, Gaingels, Harmonic Growth Partners and all existing investors participating", "page": "/investors/j-p-morgan/" }, { "name": "Capital One Ventures", "firm": "Capital One", "kind": "corporate", "rounds": [ "Series D, April 2022" ], "url": "https://www.capitalone.com", "source": "https://www.harness.io/press-and-news/harness-valuation-soars-to-3-7-billion-with-230-million-in-series-d-funding", "quote": "Norwest Venture Partners led the Series D round, with new investors J.P. Morgan, Capital One Ventures, Splunk Ventures, Adage Capital Partners, Balyasny Asset Management, Gaingels, Harmonic Growth Partners and all existing investors participating", "page": "/investors/capital-one/" }, { "name": "Splunk Ventures", "firm": "Splunk", "kind": "corporate", "rounds": [ "Series D, April 2022" ], "source": "https://www.harness.io/press-and-news/harness-valuation-soars-to-3-7-billion-with-230-million-in-series-d-funding", "quote": "Norwest Venture Partners led the Series D round, with new investors J.P. Morgan, Capital One Ventures, Splunk Ventures, Adage Capital Partners, Balyasny Asset Management, Gaingels, Harmonic Growth Partners and all existing investors participating", "page": "/investors/splunk/" }, { "name": "Adage Capital Partners", "kind": "other", "rounds": [ "Series D, April 2022" ], "source": "https://www.harness.io/press-and-news/harness-valuation-soars-to-3-7-billion-with-230-million-in-series-d-funding", "quote": "Norwest Venture Partners led the Series D round, with new investors J.P. Morgan, Capital One Ventures, Splunk Ventures, Adage Capital Partners, Balyasny Asset Management, Gaingels, Harmonic Growth Partners and all existing investors participating", "page": "/investors/adage-capital-partners/" }, { "name": "Balyasny Asset Management", "kind": "other", "rounds": [ "Series D, April 2022" ], "source": "https://www.harness.io/press-and-news/harness-valuation-soars-to-3-7-billion-with-230-million-in-series-d-funding", "quote": "Norwest Venture Partners led the Series D round, with new investors J.P. Morgan, Capital One Ventures, Splunk Ventures, Adage Capital Partners, Balyasny Asset Management, Gaingels, Harmonic Growth Partners and all existing investors participating", "page": "/investors/balyasny-asset-management/" }, { "name": "Gaingels", "kind": "vc", "rounds": [ "Series D, April 2022" ], "url": "https://gaingels.com", "source": "https://www.harness.io/press-and-news/harness-valuation-soars-to-3-7-billion-with-230-million-in-series-d-funding", "quote": "Norwest Venture Partners led the Series D round, with new investors J.P. Morgan, Capital One Ventures, Splunk Ventures, Adage Capital Partners, Balyasny Asset Management, Gaingels, Harmonic Growth Partners and all existing investors participating", "page": "/investors/gaingels/" }, { "name": "Harmonic Growth Partners", "kind": "vc", "rounds": [ "Series D, April 2022" ], "source": "https://www.harness.io/press-and-news/harness-valuation-soars-to-3-7-billion-with-230-million-in-series-d-funding", "quote": "Norwest Venture Partners led the Series D round, with new investors J.P. Morgan, Capital One Ventures, Splunk Ventures, Adage Capital Partners, Balyasny Asset Management, Gaingels, Harmonic Growth Partners and all existing investors participating", "page": "/investors/harmonic-growth-partners/" }, { "name": "Goldman Sachs Alternatives", "firm": "Goldman Sachs", "kind": "vc", "rounds": [ "Series E, December 2025" ], "lead": true, "url": "https://www.goldmansachs.com", "source": "https://www.harness.io/press-and-news/harness-announces-240m-financing-round-led-by-goldman-sachs", "quote": "a $200 million investment led by Goldman Sachs Alternatives and a planned $40 million tender offer with participation from IVP, Menlo Ventures, and Unusual Ventures", "page": "/investors/goldman-sachs/" } ] }, "pageJsonUrl": "https://www.anchorterminal.com/tools/harness-fme.json", "live": { "slug": "harness-fme", "probe": { "target": "https://mcp.harness.io/mcp", "method": "get", "lastAt": "2026-11-07T18:20:29.454967067Z", "lastOk": true, "lastStatus": 401, "lastMs": 211, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 195, "p95ms24h": 280, "samples24h": 200, "samples30d": 200, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://status.harness.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T18:21:14.597545686Z" }, "versions": [ { "registry": "github", "name": "harness/mcp-server", "version": "v3.2.40", "released": "2026-11-05", "seenAt": "2026-11-06T23:32:13.419387707Z" }, { "registry": "npm", "name": "harness-mcp-v2", "version": "3.2.40", "seenAt": "2026-11-06T23:32:12.430886041Z" } ], "githubStars": 112, "npmWeekly": 8800, "securityTxt": { "url": "https://harness.io/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:19.957252225Z" }, "llmsTxt": { "url": "https://developer.harness.io/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:41.749004752Z" }, "pages": [ { "url": "https://www.harness.io/legal/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:29:30.551687912Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "b15935b42065" }, { "url": "https://www.harness.io/legal/subscription-terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:29:35.70684084Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "871b29e12dd4" } ], "updatedAt": "2026-11-07T18:21:14.597545686Z" } } }