Functionize MCP server vs Kane CLI

Functionize MCP server 29

No machine-readable contract could be read. tools/list answers 401 without a signed-in account, and no public tool manifest, server card or source was found, so typed inputs on the tools are unchecked (0 of 25). llms.txt is an August 2025 crawl of the marketing site with no mention of MCP, but SETUP.md is Markdown written for an agent to run and the two skills are Markdown references for agents (10). Purpose and when to use each tool come only from the skills, which describe the session loop and say what Studio can't do; the tool descriptions themselves weren't read (8 of 20). Typed inputs, enums and constraints unread (0 of 15). Example prompts in the release posts and skills, and a troubleshooting table in SETUP.md with the 403 on a wrong team, redirect_uri not permitted and the unknown-tool reply; no documented error shape for tool calls (8 of 15). The plugin is versioned (1.1.0, skills 2.12.0 and 2.40.0) with a dated git history, but the server has no version or changelog (3 of 15).

Kane CLI 77

No OpenAPI or JSON Schema file. The NDJSON events are documented in typed Markdown tables, run_end is declared stable across versions, and each command family has its event list (10 of 25). Markdown docs in the repository, an agent skill and a context7.json for agents. The agents.md guide on testmuai.com wasn't readable and no llms.txt was checked (10). The user guide and skill say when to use run, testmd, testrun, assurance or Exploration, and when not (Exploration when there are no written requirements, read_only for data you care about) (17 of 20). Flag tables give defaults and allowed values for --mode, --target, --policy and --bug-detection; --variables and --session-context take free-form JSON (12 of 15). Examples throughout, exit-code tables and troubleshooting tables with named failures such as failed:setup_failed and RUN_ACTIVE. The README's run_end example names credits while the skill names credits_consumed (13 of 15). Semantic versions with a dated Keep a Changelog file and git tags (15).

Functionize MCP server 49

Read as a closed hosted service with a public plugin repository. The server was released on 8 October 2026, 16 days ago (30). The plugin repository has 19 dated commits from 26 August to 10 October 2026 and one version bump (1.1.0, 16 September), and the blog has the release of 8 October; no tagged releases or changelog, so 10 of 20. Support is through the in-app system with published response goals (2 hours for critical and high, 4 for medium, 24 for low), stated as goals, not commitments. No public changelog or community channel, and the GitHub issue pages answered 403 to us (6 of 25). Not in the official MCP registry (searches for functionize and com.functionize returned nothing on 24 October 2026) and no official SDK (0). The plugin is MIT with a current manifest but no CI or tests (3 of 10). The server is 16 days old by its release.

Kane CLI 77

0.10.0 on npm on 28 October 2026, 4 days ago (30). 28 releases from 3 August to 1 November 2026, 0.8.4 to 0.10.0, each in the changelog (20). The repository has 337 commits, pull requests up to #222 merged within days by LambdaTest staff, a Discord and an issue tracker. GitHub's API wasn't reachable from this session, so open issues and reply times weren't counted (12 of 25). Not an MCP server. The CLI and skill are current on npm and a Homebrew tap, with no SDK (10 of 15). CI runs the skill installer's tests on Linux, macOS and Windows with Node 18 and 22. The CLI's own source and tests aren't public, and the main package carries no npm provenance attestation while the skill package does (5 of 10). Kane CLI is six and a half months old by its first npm release.

Functionize MCP server 43

Graded on the MCP server. 10 tools by the README's count, with the long guidance moved into Claude Code skills that load only when used. The size of the definitions couldn't be read, so 20 of 25 rather than 25 for compact tools. Sessions can be listed and their events read or streamed, but no page size, filter or output-size control was found (5 of 20). Results carry the failing step, screenshots and logs, and SETUP.md maps symptoms to fixes; no error codes for tool calls were found (8 of 20). No idempotency key, and readOnlyHint and destructiveHint couldn't be checked; the skill's advice to list recent tests before creating again is the only retry guidance (3 of 20). Requests are plain words, the team defaults to the account's own and sign-in needs no key, but there's no official SDK (7 of 15).

Kane CLI 65

Graded on the CLI as an agent drives it. run_end carries summary, one_liner and only the values asked for with "store as" in final_state, and --max-steps and --timeout bound a run. The skill an agent loads is about 40 KB with 25 reference files (15 of 25). testrun selects by paths, --match and --tags, explore list and explore sessions filter by run, and --json on design and review commands; few size controls beyond that (14 of 20). Exit codes separate pass, fail, setup error and timeout, failure reasons are named, and refusals name the command to run next (18 of 20). Replays of saved tests come from cache, reconcile resumes rather than re-billing, and Exploration allows one run at a time. A one-shot run has no idempotency key and Exploration's default can change data (10 of 20). One required argument for run; Exploration's mutating default isn't a safe one; no SDKs, only the CLI from npm, Homebrew and a shell script (8 of 15).

Functionize MCP server 58

The editorial half. A closed service under dated terms naming Functionize, Inc. and California law (version 2.0, effective 10 July 2026), with the plugin and skills under MIT (17 of 30). The privacy policy (effective 10 July 2026) and terms agree that customer content isn't used to train foundation models except when aggregated and de-identified, while usage data may be used for training at Functionize's discretion. Deletion or anonymisation follows termination within about sixty days, sandbox data may be reset, and a DPA is by agreement only. No retention period for run artifacts is given (15 of 30). No deprecation policy; SETUP.md mentions a retired server address with no dated notice (2 of 20). Stripe is the only named sub-processor; cloud hosting and AI model providers are unnamed and no data location is stated (4 of 20).

Kane CLI 38

The editorial half. The wrapper, skill and docs are Apache-2.0. The runner, assurance and pinned Node binaries are labelled Apache-2.0 on npm with no source in the linked repository, and the service terms couldn't be read (12 of 30). The repository says what leaves the machine. Every run uploads to Test Manager with screenshots and an evidence pack recording the user's name and email, secrets are masked, credentials are stored with mode 0600, and the evidence viewer reads packs locally. The privacy policy, DPA and retention periods are on testmuai.com and weren't read (10 of 30). The changelog calls out breaking changes, such as the removal of the bare-objective shortcut in 0.4.1, but there's no deprecation policy or dated notice period (5 of 20). The changelog describes telemetry (a remote log, support ids, errors spooled and sent at exit) and a daily npm update check. The opt-out KANE_TELEMETRY=0 appears only in a skill reference, not the user guide (8 of 20).

Functionize MCP server 30

No x402, MPP or L402 (0). Plan prices are public ($0, $20 and $100 a month with their credits, add-on credits at $10 per 200,000), but the credits a task uses aren't published, so plan-only pricing (10). A Free plan with no card and no time limit (20). A person has to sign up for Studio and sign in through a browser before any call works (0).

Kane CLI 20

No x402, MPP or L402 (0). Plan prices are public per the listing check of 1 November 2026 (Starter $17 a month billed annually, Pro $89), and run_end reports credits per run, but the credit price per run isn't published, so plan-only pricing (10). The release says "free to start" and the check found a 10,000-credit, 30-day trial; whether it needs a card couldn't be read today. Judgement call (10 of 20). A person signs up and approves OAuth in a browser, or copies an access key from the dashboard, before any run (0).