- Reliability 7/20
- Evidence is limited to the README and server.json, both of which are untrusted; no source code, CI workflows, or committed tests were supplied for verification. The README contains multiple internal contradictions: tool-count figures disagree (19 universal vs 41 total vs 40+ resource-specific tools consolidated), the required Node.js version is inconsistent (badge says >=20, prerequisites say v18+), environment variables documented in the README (ATTIO_ACCESS_TOKEN, ATTIO_DEFAULT_DEAL_STAGE, etc.) are absent from the manifest, the manifest is at 1.6.1 while the README headlines v1.4.0, and the README admits universal-tools docs are being updated to match the implementation. The happy path is not reliably reproducible from the supplied material, so the score is deducted to 7.
- Security and permissions 11/20
- No red line was triggered: all auth examples use placeholders (your_api_key_here) and no real secrets, malware, or exfiltration patterns are visible. ATTIO_API_KEY is properly marked required and secret in the manifest. The README claims MCP safety annotations (readOnlyHint/destructiveHint), a search-only least-privilege mode, and dry-run write prompts, but none of this can be verified from source. Deductions: the API key grants full-workspace CRUD including delete and batch delete without verifiable mandatory confirmation; the remote Cloudflare Worker deployment widens the attack surface; and 90 open issues may include unresolved security concerns. Scored 11.
- Maintenance 10/20
- The repository is not archived, the manifest is at version 1.6.1, and the README references many merged PRs and claims Sigstore npm provenance, indicating sustained activity and release engineering. Deductions: repository metadata reports License: NOASSERTION while the README claims Apache 2.0, a governance gap; 90 open issues is high relative to 69 stars; the README still leads with v1.4.0 content while the manifest is at 1.6.1, showing stale version documentation; and no security-response channel is disclosed. Scored 10.
- Documentation 12/20
- The README is layered and extensive: tiered installation, per-client config JSON examples, tool/prompt tables, a migration guide, troubleshooting links, a docs directory, usage examples, and disclosed limitations (tasks attribute filtering, pagination) plus some cost info (Cloudflare free tier). Deductions: multiple contradictions (Node version, tool counts, env-var lists); an explicit admission that universal-tool docs lag the implementation; hidden assumptions around the field-mapping configuration declared CRITICAL; and no cost disclosure for the Attio API itself. Scored 12.
- Setup experience 12/20
- Multiple install paths are provided (npm global install, one-line shell installers, manual JSON configs for Claude Desktop/Cursor/Claude Code, Docker, and Cloudflare Worker) with good mainstream-client coverage. Deductions: setup is multi-step and fragile — users must manually copy and edit a field-mapping user.json or the server may not work correctly; a package-name trap exists (installing attio-mcp-server yields stale v0.0.2); the shell installers pipe curl to bash; and no verifiable execution evidence (real CI plus committed tests) was supplied, so per static calibration setup is capped at 15. Scored 12.