- Reliability 7/20
- Only the README text was available; no manifest was cached and no CI workflow files or committed tests are visible to verify that the MCP init/tool-list handshake actually works or that the 20+ documented tools match real behavior. Per the static-review rule, without verifiable execution evidence (CI + tests) reliability cannot exceed 12; it is scored further down because there is zero execution or test evidence at all, only documentation-level claims.
- Security and permissions 9/20
- Authentication via token or username/password through environment variables is a standard, acceptable pattern, and no real secrets appear in the docs. However, the default mode is full read-write; read-only restriction requires the operator to explicitly set BITBUCKET_READ_ONLY=true. Irreversible/high-impact operations (merge_pull_request, decline_pull_request, delete_branch, delete_comment) have no documented confirmation step — enforcement of caution relies on the calling LLM/user rather than the server. BITBUCKET_CUSTOM_HEADERS allows arbitrary header injection into outbound requests, a moderate but bounded exposure. No red-line issue is present (no malware, no credential exfiltration, no fabricated identity), but least-privilege defaults and confirmation for destructive actions are incomplete.
- Maintenance 11/20
- Apache-2.0 license is present and the repo is not archived. The README's 'New Features' section shows a stream of recently added functionality (custom headers, PR discovery, branch management, etc.) and references a specific issue number (#14), indicating some responsiveness to community feedback. However, there is no visible versioning scheme, changelog, release cadence, contribution guide, or security-response channel to confirm ongoing commit activity or maintainer stability, so this can only be judged 'active but with governance gaps.'
- Documentation 16/20
- The README is well-layered: installation (Smithery and manual), build steps, per-tool purpose/parameters/use cases, abundant CLI examples, environment variable reference, an explicit allow/deny tool list for read-only mode, log-path priority, and custom header formatting are all documented. It lacks a dedicated troubleshooting section, rate-limit guidance, error-code semantics, or discussion of cross-platform caveats and failure-mode behavior.
- Setup experience 13/20
- The install path is clear: `npm install` → `npm run build` → manual entry of the node path and environment variables in the MCP client config, plus a one-command Smithery installer covering a mainstream client. This remains a semi-manual process requiring a manual build and absolute path configuration, and there is no CI/test evidence in the repo to confirm the build/run chain actually works end-to-end, so per the static-review cap this dimension cannot exceed 15.