- Reliability 2/20
- No server manifest was provided ([not cached]), and the README describes a general-purpose AI coding agent platform (VS Code/JetBrains extensions, CLI, cloud agent) rather than an MCP server — there is no tool list, no MCP init/handshake evidence, and no description of declared-tool-to-behavior mapping. The README even states the project ships an 'MCP marketplace' to connect to external MCP servers, indicating it functions as an MCP client/host, not the MCP server under review. With no tool definitions or reproducible startup evidence, and per the static calibration rule capping reliability at 12 absent CI/test evidence, this must score very low.
- Security and permissions 6/20
- No red-line issue is evident (no default unconfirmed destructive/pay/deploy actions, no leaked credentials in examples). However, the README explicitly notes that `kilo run --auto` 'disables all permission prompts and lets the agent execute any action without confirmation,' mitigated only by a text warning to use it in trusted environments — this is a meaningful gap in least-privilege and confirmation disclosure. Because the object is not actually shown to be an MCP server, there is no visibility into any tool-exposure permission model, data boundaries, or credential handling, so the security picture is highly incomplete and must be scored conservatively.
- Maintenance 10/20
- The repository is MIT-licensed, not archived, and includes CONTRIBUTING.md, RELEASING.md (with separate release processes for VS Code, CLI, and JetBrains), and a CODE_OF_CONDUCT.md, indicating some governance structure. Star and issue counts are discovery signals only and are not used to raise the score. Without concrete evidence of commit cadence, recent release dates, or a security-response channel in the supplied material, sustained maintenance cannot be verified, warranting a mid-range score.
- Documentation 8/20
- The README documents general product installation (VS Code/JetBrains/CLI across multiple package managers), agent modes, and CI/CD automation reasonably well, with a link to external docs. However, there is no documentation whatsoever addressing an MCP server role: no tool parameter documentation, no authentication flow, no rate-limit/cost disclosure, and no MCP-protocol-specific troubleshooting. Since the review object is nominally an MCP server, this core documentation gap caps the score at a middling level based only on general product docs.
- Setup experience 4/20
- Install instructions are provided for multiple channels (npm, curl, pnpm, bun, Homebrew, AUR, GitHub release binaries) for installing the Kilo Code agent itself, but none of these describe configuring it as an MCP server inside a mainstream MCP client (e.g., no command/args/env config block for Claude Desktop or similar). There is no evidence the project can be discovered or invoked as an MCP server by a client. Per the static calibration rule, setup cannot exceed 15 without real CI and committed tests covering the server's key paths, and given the absence of any MCP-specific connection steps, a low score is warranted.