- Reliability 8/20
- Static review sees only server.json and README; no executable source, test files, or CI workflows are supplied, so MCP initialization, the tools/list handshake, and whether check_sensitive_words / get_word_suggestions behave as declared cannot be verified. The README usage examples are untrusted evidence and do not count as execution proof. Plausible positives: the package is npm-published, uses stdio transport, and names/tools are internally consistent, suggesting a workable happy path. However error handling, quota exhaustion (100/day), and upstream-service outage behavior are undisclosed, and boundary cases are absent. With the static cap of 12 and missing evidence treated as a deduction rather than a best case, the score is 8.
- Security and permissions 8/20
- No malware, credential theft, or covert exfiltration is visible, and install examples contain only placeholder tokens (your_token_here), so no red line is triggered. Concerns: the server ships user text (potentially containing phone numbers and WeChat IDs) to a remote WORDSCHECK_API_BASE endpoint whose privacy and retention behavior is undocumented; WORDSCHECK_ACCESS_TOKEN is passed in plain env with no scoping or least-privilege note; WORDSCHECK_API_BASE is user-overridable, widening the data-egress surface. The tool surface is read-only detection with no delete/pay/deploy side effects, which limits operational risk. Incomplete disclosure of data flow and permissions yields 8.
- Maintenance 11/20
- The repository is not archived, carries a clear MIT license, has one open issue, and the description claims daily dictionary updates, indicating ongoing activity; contact channels (WeChat, email) are provided. But within the static evidence there is no CHANGELOG, no semantic release history, no dependency-update policy, and no security-response/security policy; version 1.0.0 makes cadence hard to judge, and CONTRIBUTING.md is referenced but not evidenced. Governance and versioning gaps yield 11.
- Documentation 12/20
- The README is well layered: bilingual entry points, feature list, tool table, multi-client install (Claude Desktop/Cursor/Windsurf/Claude Code/OpenClaw), runnable JSON config snippets, a full detection output example with JSON return shape, risk-level table, platform dictionary table, quota table (free 100/day, unlimited with token), and contact info. Deductions: no statement on remote-API privacy or data retention, no error-code/timeout/quota-exhaustion troubleshooting, no input-schema detail for the two tools (e.g. platform parameter), and it embeds promotional links (mcp-custom-dev) plus personal contact details. Usable overall but with hidden assumptions, so 12.
- Setup experience 12/20
- The install path is clear and short: npx -y chinese-sensitive-words-mcp runs as a stdio server, and the README provides copy-pasteable config blocks for mainstream clients plus a one-line Claude Code variant. Node.js/npx is a prerequisite but is not stated explicitly. Custom endpoint and token are configured via env in a conventional, reversible way. Deductions: no version pinning (upstream drift risk), no offline/registration-unavailable fallback, and no connectivity verification step. Constrained by the static cap of 15 (no CI, no committed tests), the score is 12.