- Reliability 9/20
- The manifest declares a single stdio transport, npm package @ask-llm/[email protected], and four optional env vars (default model alias, fallback model, timeout, log level). Its name io.github.Lykhoyda/ask-claude and description of read-only second opinions match the README's ask-claude entry (Opus with Sonnet fallback, native sessions, Read/Glob/Grep-only workspace access), so there is no visible contradiction between declared scope and described behavior. However, the supplied source material contains only server.json and the README; it includes no source code for packages/claude-mcp, no committed tests, and no per-package CI workflow, so the MCP init + tool-list handshake, error surfaces, and failure paths (missing CLI, unauthenticated CLI, the default 600000 ms timeout, model fallback) cannot be verified as controlled and diagnosable. Per the static calibration, reliability must not exceed 12 without verifiable execution evidence; scored 9, with deductions for absent committed tests/run evidence for this server and for an external runtime dependency (Claude Code CLI) whose presence and auth state cannot be confirmed statically.
- Security and permissions 13/20
- By description this server only produces read-only second opinions, and the README states ask-claude is limited to Read/Glob/Grep-level workspace access. All env vars in the manifest are marked isSecret=false and no API key or token is involved; install examples contain no real secrets. No malware, credential theft, covert exfiltration, fabricated identity/claims, or irreversible delete/pay/deploy/remote-command defaults appear, so no red-line trigger applies and the score is not in the 0-4 range. The notable residual risk is data flow: prompts and any workspace files read are passed through the local Claude Code CLI to a remote Anthropic model, a boundary only implied by README prose rather than demonstrated by server-level permission declarations, confirmation prompts, or scoping controls in the provided files; the 10-minute default timeout and override-able model alias are controllable but noteworthy. Scored 13; deductions for relying on README-level (not code-level) disclosure of the outbound data boundary and for the absence of a least-privilege declaration or explicit confirmation evidence for this package.
- Maintenance 13/20
- Evidence shows the repository is not archived, is MIT-licensed, and the README carries CI and release badges, version numbers, an explicit issues entry point, and CONTRIBUTING guidance, indicating release and contribution processes exist. The manifest version 0.0.1 matches the package version, giving basic versioning consistency. Gaps remain: commit cadence, issue responsiveness, and dependency-update practice for this server cannot be confirmed from the supplied material, the version is still early (0.0.1), and no security-response channel (e.g., SECURITY.md or a reporting path) is provided. Scored 13, deducting for early-stage versioning, no security-response channel evidence, and unverifiable issue/dependency maintenance rather than assuming the best case.
- Documentation 14/20
- The README is comparatively layered: it separates the unified server from per-provider packages, provides a package mapping table, multi-client configuration examples (Claude Code, Cursor, Codex CLI, Claude Desktop, Pi, generic STDIO), provider auth prerequisites, per-provider default and fallback models, and explicit disclosure of constraints such as the Gemini CLI enterprise gate; it also points to a docs site and llms.txt. For this server specifically it states the intended use (an independent Claude opinion from a non-Claude host) and the read-only workspace-tool boundary. Deductions: there is no per-parameter documentation for ask-claude (sessionId semantics, AskResponse/outputSchema fields, exact failure return shapes), troubleshooting is delegated to an external docs site that cannot be verified from the static material, and env-var coverage is manifest-level only. Scored 14 rather than higher.
- Setup experience 13/20
- The install path is clear and short: npx -y @ask-llm/claude-mcp (or codex mcp add claude -- npx -y @ask-llm/claude-mcp), with a Codex CLI TOML snippet and a generic STDIO JSON snippet, prerequisites being Node.js 20+ plus an installed and authenticated Claude Code CLI. This is a directly reusable configuration form for mainstream clients. Deductions: Linux/macOS only (README explicitly excludes Windows), a mandatory extra manual step of installing and authenticating the external Claude Code CLI, env vars to configure (though defaulted), and no concrete troubleshooting steps for typical failures (CLI absent/unauthenticated, model overload). Per the static calibration, setup must not exceed 15 without verifiable execution evidence for this package; scored 13.