- Reliability 10/20
- Manifest declares 16 tools, stdio transport, and a PyPI package identifier 'clio-kit' with positional args 'mcp-server pandas' — internally coherent. However this is a static review with no committed tests or CI evidence specific to the pandas server's key paths (repo badges are unverified claims); tool-behavior fidelity cannot be confirmed. Version drift exists: manifest package version 2.10.6 vs README install 2.4.3, and README describes pandas as merely 'CSV data loading and filtering', inconsistent with the declared 16-tool breadth. Deducted for absent server-level test evidence and version inconsistency.
- Security and permissions 12/20
- DataFrame tools are local file operations with no declared network access or credential handling; main risks are file read/write side effects (save_data, clean_data) with no disclosed confirmation mechanism, path scoping, or data-flow disclosure in either manifest or README. No red-line issues found (no malware, credentials, or dangerous irreversible defaults), but incomplete permission/confirmation/scoping evidence caps the score at 12.
- Maintenance 14/20
- BSD-3-Clause license is clear; NSF funding, IIT research center ownership, Zulip community, and 39 open issues indicate active use and engagement. But version governance is muddled (2.10.6 vs 2.4.3 vs table contract versions) and no server-level security-response channel is evidenced — 'active but with governance/versioning gaps' tier.
- Documentation 12/20
- README covers installation, client configs (Cursor, Claude Code, VS Code, Claude Desktop), usage examples, and troubleshooting; however this is monorepo-level documentation with no pandas-specific tool parameter tables, limits, or cost notes, and README's description of pandas ('CSV data loading and filtering') contradicts the declared 16-tool capability, showing capability-doc drift.
- Setup experience 12/20
- One-command uv tool install plus JSON config examples for four mainstream clients with stdio transport make setup straightforward; but the install example version (2.4.3) mismatches the manifest package version (2.10.6), and without verifiable execution evidence of a working client connection, static calibration caps setup at 12.