- Reliability 10/20
- Static review sees only the server.json manifest plus README; there are no CI workflows or committed tests covering the server's key paths (get_ai_context, run_commands, export_diagram). The manifest is internally consistent and coherent with the README (stdio transport, Python 3.10+, .nsm workspace), tool signatures and descriptions align, and the ordering prerequisite (get_ai_context before edits) is stated. However, absence of verifiable execution evidence, of documented failure handling (subprocess errors, missing paths, timeouts on large networks), and of any pinned dependency detail (requirements_mcp.txt not visible) keeps this mid-range.
- Security and permissions 9/20
- No red line is triggered: no credential theft, no covert exfiltration, no unconfirmed destructive defaults. Design is local stdio, no data retention claimed, set_workspace is explicitly constrained to the user's home directory and writability-checked, and exports write only into the workspace. Deductions: run_commands can execute arbitrary Network Sketcher CLI mutations (delete/rename) with no documented confirmation or dry-run step, and the get_ai_context requirement is a soft workflow gate rather than an access control; no secrets or real tokens appear in the install examples.
- Maintenance 14/20
- License is explicit (Apache-2.0) with clear copyright attribution (Cisco Systems / Yusuke Ogawa), the version string shows semantic versioning intent (3.1.2r), and the repo is active (392 stars, 0 open issues). Missing evidence, however, for release cadence, dependency update policy, and a security-response channel; no CHANGELOG or CI status is provided, so governance details remain a gap and the score is good-but-not-full.
- Documentation 15/20
- README is layered and thorough: three-edition comparison, feature support matrix, disclosed limitations (stdio only, single user, long generation times, PPTX/SVG not directly viewable by the LLM, recommended model), install steps, dual-client config examples for Cursor and Claude Code, and platform notes. Tool descriptions in the manifest are likewise detailed (e.g. the area/format constraints on export_diagram). Deductions: no troubleshooting section for dependency or Python-version issues (requirements_mcp.txt content, engine 3.9+ vs SDK 3.10+), leaving hidden assumptions.
- Setup experience 11/20
- The install path is short and clear: git clone, pip install -r requirements_mcp.txt, then register the python script in Cursor's mcp.json or via claude mcp add, with the -- separator and scope options explained and copy-pasteable examples. But it requires the full repository (network-sketcher_online present), manual absolute-path substitution, and the README states Windows-only testing (macOS/Linux untested), with no packaging, container, or one-command install. Workable but manual and somewhat fragile, so below the top tier.