- Reliability 4/20
- Only the README and repository metadata are available; no source, CI, or tests can be verified. The README claims 35+ tools and a full agent loop, but there is no server manifest and no reproducible MCP initialization/tool-list handshake evidence. Error handling and dependency control cannot be confirmed. The static calibration caps this at 12, and evidence is insufficient, so scored 4.
- Security and permissions 3/20
- Red line triggered: the default permissionMode is bypassPermissions, and built-in tools include Bash, Write, and Edit, allowing irreversible delete/pay/deploy-style commands without confirmation. Passing the API key via environment variables is positive, but least privilege is absent by default, no sandbox is enabled by default, and external network and filesystem boundaries are unclear. Security scored 3.
- Maintenance 6/20
- The repository is not archived, has an MIT license, and 10 open issues, but no commit history, release records, or issue-response evidence is visible. Star count is only a discovery signal and earns no points. Lacking verifiable sustained maintenance and versioning evidence, scored 6.
- Documentation 12/20
- The README is fairly comprehensive: install steps, environment variables, API reference, 15 examples, architecture, and built-in tool tables are included. However, there is no troubleshooting section, no mainstream-client configuration example for using it as an MCP server, and no disclosure of the risks of the default bypassPermissions mode. It is good as a README, but as MCP-server documentation it has gaps; scored 12.
- Setup experience 5/20
- The SDK install steps are simple (npm install + environment variable), but there is no mainstream-client configuration example for adding this repository as an MCP server, nor is there a server manifest or executable-entry evidence. Examples in the README additionally require tsx. The static calibration allows above 15 only with verifiable execution evidence; here evidence is insufficient, so scored 5.