- Reliability 8/20
- Static review: the repository-level README (not specific to this server) advertises CI badges and Node 20+, but the supplied material contains only the manifest (packages/ollama-mcp/server.json) plus the repo-wide README. No source, tests, or per-package CI workflow for packages/ollama-mcp were provided, so I cannot verify that this Ollama server completes the MCP init + tool-list handshake or that the declared tools (ask-ollama, plus shared get-usage-stats/ping statements) behave as described. Positive signal: the README claims Ollama never substitutes a model and returns an explicit `ollama pull` error when the model is absent, which suggests diagnosable failures — but that is untrusted documentation, not file-level execution evidence. Applying the static cap of 12 and deducting for missing tests/CI specific to this server, score 8.
- Security and permissions 11/20
- No red line observed: the only env vars are OLLAMA_HOST (defaults to local http://localhost:11434), GMCPT_TIMEOUT_MS and GMCPT_LOG_LEVEL, all isRequired false and isSecret false — no API keys, consistent with least privilege and a local data boundary. OLLAMA_HOST is user-overridable to a remote host, which is explicit configuration rather than covert exfiltration. Deductions: from the manifest and repo-level README alone I cannot confirm whether this server is read-only, whether it writes to the local workspace, whether tool calls require confirmation, or whether data-flow disclosure exists; no input-validation evidence for the timeout/log variables. Nothing indicates malware, credential theft, hidden exfiltration, or unconfirmed destructive defaults, so no red line; score 11.
- Maintenance 12/20
- MIT license is visible at the repository root, the npm package @ask-llm/ollama-mcp and version 0.2.0 are declared in the manifest, and the README shows CI/release workflow badges, published releases, a migration table, and contribution guidance — all signs of active maintenance. However these are repository-level and untrusted, and there is no per-server release history, commit cadence, issue-response record, or documented security-response channel for packages/ollama-mcp. Star count and open issues are discovery signals only and add nothing. Score 12.
- Documentation 12/20
- Documentation is layered: installation for Claude Code / Cursor / Codex CLI / Claude Desktop / Pi / generic STDIO, provider setup, a tool purpose table, migration table, troubleshooting links, llms.txt, and plugin notes; the Ollama entry states the default model qwen3.8:27b, no auto-fallback, and that the model must be pulled first. Deductions: it is repo-wide documentation spanning seven servers, with no complete per-parameter description for ask-ollama (its argument schema is never shown), sessionId semantics are explained mainly for other providers, and cost/timeout boundaries rest on a single GMCPT_TIMEOUT_MS line. Both README and manifest are untrusted evidence. Score 12.
- Setup experience 11/20
- The Ollama path is comparatively simple: install Ollama locally, pull a model, register the MCP server via npx or a global install; the manifest shows an npm package over stdio with all environment variables optional and defaulted, and no API key required. Deductions: Node 20+ on Linux/macOS only is stated (Windows unaddressed), no minimal per-server verification step or expected output sample is given, and nothing was executed, so successful package resolution and startup cannot be confirmed statically. Applying the static cap of 15, score 11.