- Reliability 5/20
- No source code, tests, or CI workflow specific to mcp/packages/automotive/server.json was provided; the manifest and README claims (9 tools, stdio, npm package) are untrusted evidence. The MCP init/tool-list handshake and tool behavior cannot be verified. Deducted heavily for missing execution evidence.
- Security and permissions 6/20
- No red-line issues found, but source is absent, so credential handling, network calls, least privilege, and confirmation flows cannot be assessed. Deducted for missing evidence rather than assuming best case.
- Maintenance 12/20
- Repository is Apache-2.0, not archived, with 1,276 stars and 72 open issues; package version 1.1.0 is declared. However, no server-specific changelog, dependency update evidence, or security-response channel for this server was supplied. Stars are only a discovery signal.
- Documentation 5/20
- Only a one-line install command and a tool-count (9) in the specialty-server table are present; no tool parameters, auth, limits, cost, or troubleshooting docs for the automotive server. The broader MCP README is not attributable to this server.
- Setup experience 8/20
- Install is a single npx command (automotive-3d-mcp) with stdio transport, which is straightforward for mainstream clients. But no automotive-specific client config example, runtime prerequisites, or verified working setup was supplied; static calibration caps this and no execution evidence exists.