- Reliability 8/20
- server.json clearly declares stdio transport and a fixed launch command (npx -y thumbgate serve), and the README explicitly warns against npm start (which launches the unrelated HTTP API from a sibling service). Beyond that, no tool list, parameter schema, or test evidence specific to this stdio server is provided; the README's CI badge and eval/monitor npm scripts appear to target a separate 'task outcome' subsystem, not proven to cover this server's init/tool-list handshake. Per the static calibration rule, without verifiable execution evidence (CI + committed tests) covering this server's key paths, reliability is capped at 12; given the thin evidence (no tool manifest, no server-specific tests visible), it is scored 8.
- Security and permissions 13/20
- THUMBGATE_MCP_PROFILE defaults to the least-privilege 'essential' profile, only expanding scope when explicitly set — a good least-privilege signal. The README also candidly discloses that only detected secret leaks and self-disable commands hard-block by default; other high-risk classes (rm -rf, force-push, off-scope edits, deploys) only warn-and-log by default and require THUMBGATE_STRICT_ENFORCEMENT=1 to deny, and for Cursor/Cline/OpenCode the gate_check is merely advisory (the agent can ignore it). This is not a red-line case, since the server itself does not execute the dangerous action — it only renders a verdict on another tool's call — and the limitation is clearly disclosed. Since no source-level tool/permission list could be verified, and there is an external network surface toward thumbgate.ai for licensing/billing, full marks are not warranted.
- Maintenance 13/20
- The project is MIT-licensed and the npm package is at version 1.36.1, indicating ongoing iteration; the README references a CI badge, a Changesets process, and release-confidence documentation, suggesting some release governance. However, 48 open issues against only 25 stars is a comparatively high ratio that may indicate unresolved backlog or slower responsiveness, and no recent-commit evidence is available. Scored as active but with governance/responsiveness gaps.
- Documentation 14/20
- The README is extremely thorough, covering install, architecture, CLI reference, built-in checks, recovery flow (break-glass), pricing, and FAQ, and links out to THREAT_MODEL.md, VERIFICATION_EVIDENCE.md, and other docs. However, a large portion is marketing/sales content (pricing tiers, enterprise pitch, SEO landing links) rather than technical reference, and since this repository ships 3 MCP servers, many tool names mentioned in the README (capture_feedback, gate_check, record_task_outcome, etc.) are not clearly attributed to this specific server.json stdio server versus its siblings — there is no formal parameter-level tool reference scoped to this server.
- Setup experience 13/20
- The manifest specifies a single, clear launch path (npx -y thumbgate serve over stdio), and the README has a dedicated section clarifying the correct MCP/registry install command and warning against a common misconfiguration (npm start launching the wrong HTTP service). This is clear and low-friction. However, per the static calibration rule, without source-verifiable test/CI evidence covering this exact path, setup is capped at 15; within that ceiling it is scored a relatively high but non-maximal 13.