- Reliability 4/20
- Only the README was supplied; no server source, tests, or CI exist to verify the MCP init handshake or that declared tools match real behavior. A happy path is plausible from the docs, but reproducibility and error-path evidence are missing, so the score is low.
- Security and permissions 3/20
- The server exposes execute_code for LLM-driven arbitrary PyQGIS execution, with no documented confirmation or approval step, and the socket server has no described authentication or data boundary. This is an unconfirmed remote-command default, triggering the 0-4 red-line range; score is 3.
- Maintenance 3/20
- The repo is not archived and has open issues, but there is no evidence of commits, releases, or versioning; the license is unknown and no security-response channel is documented. Stars are discovery signals only; maintenance governance evidence is insufficient.
- Documentation 10/20
- The README is fairly complete with prerequisites, plugin installation, Claude config, a tool list, and an example workflow; however, troubleshooting, detailed tool parameters, limitations, and permission/data-flow disclosures are missing. Several assumptions such as absolute paths and local socket behavior are unexplained.
- Setup experience 10/20
- Instructions are clear and include uv, plugin copying, and a Claude Desktop JSON config example; however, setup is entirely manual and fragile, with no automated installer or CI verification. Cross-platform paths are shown, but hidden pitfalls remain.