kimi-tree-lens
Syntax-tree X-ray for Kimi Code — tree-sitter powered code navigation via MCP (Java/Python/TypeScript/TSX/Go)
Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
zhaoxingxing06
Source: github_code
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.
KIMI_CODE_HOMETREE_SITTER_MCP_CACHE_DIRTREE_SITTER_MCP_CACHE_SPIN_MSTREE_SITTER_MCP_FRESHEN_BUDGET_MSTREE_SITTER_MCP_MAX_FILESTREE_SITTER_MCP_OUTLINE_DIRTREE_SITTER_MCP_POOLTREE_SITTER_MCP_ROOTSTREE_SITTER_MCP_STORETREE_SITTER_MCP_TIMEOUT_MSTREE_SITTER_MCP_USER_QUERIESTREE_SITTER_MCP_WATCH_DEBOUNCE_MSTool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
16/16 tools missing one or more hints — list_definitions (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); cached_outline (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); read_definition (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +13 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
Destructive tools are labelled
16 tools perform destructive updates without destructiveHint — list_definitions deletes at line 512 (fsSync.rmSync(buildLockFile)); cached_outline deletes at line 512 (fsSync.rmSync(buildLockFile)); read_definition deletes at line 512 (fsSync.rmSync(buildLockFile))
Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.
Descriptions match behaviour
3 tools describe read intent but their handlers mutate — list_definitions (line 432: fsSync.mkdirSync(path.dirname(buildLockFile), { recursive: true })); read_definition (line 432: fsSync.mkdirSync(path.dirname(buildLockFile), { recursive: true })); list_presets (line 432: fsSync.mkdirSync(path.dirname(buildLockFile), { recursive: true }))
Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.
Tests exist
No test files found
Add tests that exercise each declared tool.
Tool description accuracy
3 tools have description/behavior mismatches: list_definitions: description implies read-only but handler writes/deletes/executes; read_definition: description implies read-only but handler writes/deletes/executes; list_presets: description implies read-only but handler writes/deletes/executes
Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/zhaoxingxing06/kimi-tree-lens)?variant=verified from the URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check