- Reliability 9/20
- The manifest declares 25 tools, but no paraview server source, tests, or CI evidence is provided for the reviewed path; the CI/coverage badges belong to the whole monorepo and cannot be attributed to paraview. Version inconsistencies exist: the manifest pins clio-kit 2.10.6, README examples use 2.4.3, and the table lists contract version 2.2.3 for paraview. Not scored lower because tool descriptions are concrete and the happy path is plausible, but per static calibration rules no execution evidence caps it at 12; actual evidence is thinner, so 9.
- Security and permissions 12/20
- No malware, credential theft, or red-line behavior found; tools are mostly local ParaView visualization operations. However, screenshot/STL tools write to the filesystem with no stated permission boundaries, confirmation mechanisms, or data-flow disclosure; the local rendering process attack surface is undiscussed. Not a red-line risk, but scored mid-range (12) due to missing least-privilege and side-effect disclosure.
- Maintenance 12/20
- Project appears active (BSD-3-Clause, NSF/IIT backing, 26 stars, 39 open issues, named team and sponsors). But license evidence is README-level only; no paraview-directory-level maintenance evidence, security response channel, or server-specific release history is shown. Monorepo activity does not prove this server's activity, hence 12.
- Documentation 9/20
- The README targets the entire clio-kit; paraview gets only one table row. No paraview-specific prerequisites (ParaView/Python binding versions), tool parameter docs, limitations, or troubleshooting. Resource and prompt have one-line descriptions only. Usable but with many hidden assumptions, so 9.
- Setup experience 11/20
- uv install instructions and multi-client config examples are provided, and paraview can be launched via 'clio-kit mcp-server paraview'. However, examples pin 2.4.3 while the manifest says 2.10.6 (version drift), and preparing the local ParaView dependency — essential for this server — is entirely undocumented, leaving post-install usability uncertain; 11.