Code Lens
NPM · @J0HANZ/CODE-LENS-MCP · SCANNED SEP 20
Gemini-powered MCP server for code analysis.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 48 of 136 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to j0hanz/code-lens). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 195 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 3271 tokens (~102/item across 32 items; 13 tools + 19 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Code Lens MCP server?
Code Lens runs locally as an npm package, launched with npx -y @j0hanz/code-lens-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @j0hanz/code-lens-mcp
claude mcp add j0hanz-code-lens -- npx -y @j0hanz/code-lens-mcp
{
"mcpServers": {
"j0hanz-code-lens": {
"command": "npx",
"args": [
"-y",
"@j0hanz/code-lens-mcp"
]
}
}
} {
"servers": {
"j0hanz-code-lens": {
"command": "npx",
"args": [
"-y",
"@j0hanz/code-lens-mcp"
]
}
}
} codex mcp add j0hanz-code-lens -- npx -y @j0hanz/code-lens-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"j0hanz-code-lens": {
"type": "local",
"command": [
"npx",
"-y",
"@j0hanz/code-lens-mcp"
],
"enabled": true
}
}
} openclaw mcp add j0hanz-code-lens --command npx --arg -y --arg @j0hanz/code-lens-mcp
mcp_servers:
j0hanz-code-lens:
command: "npx"
args: ["-y", "@j0hanz/code-lens-mcp"] {
"McpServers": {
"j0hanz-code-lens": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@j0hanz/code-lens-mcp"
]
}
}
} assistant mcp add j0hanz-code-lens -t stdio -c npx -a -y @j0hanz/code-lens-mcp
{
"mcpServers": {
"j0hanz-code-lens": {
"command": "npx",
"args": [
"-y",
"@j0hanz/code-lens-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@j0hanz/code-lens-mcp@0.12.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | j0hanz/code-lens |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/j0hanz/code-lens/.github/workflows/release.yml@refs/heads/master |
| Rekor log index | 1062872572 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:79779c679ded734ce46d7b7494b5a95c070a2e6b86bac4b91dd9feb2609cb62c8add542152a20391e5079dcae27f2be037260150802a0ea9ef0f79054 |
Background: How many MCP packages publish verified provenance →
Dependencies 136 packages
| Packages resolved | 136 |
|---|---|
| Deprecated | 1 |
| Stale | 47 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_pr_impact Analyze PR Impact ~64
Assess impact and risk from cached diff. Prerequisite: generate_diff. Auto-infer repo/language.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Primary language (e.g. TypeScript, Python, JavaScript, Go, Rust, Java). Auto-infer from files. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | Error payload when ok is false. |
| ok | boolean | yes | Whether the tool completed successfully. |
| result | object | – | Successful result payload. |
No examples provided.
analyze_time_space_complexity Analyze Time & Space Complexity ~60
Analyze Big-O complexity. Prerequisite: generate_diff. Auto-infer language.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Primary language (e.g. TypeScript, Python, JavaScript, Go, Rust, Java). Auto-infer from files. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | Error payload when ok is false. |
| ok | boolean | yes | Whether the tool completed successfully. |
| result | object | – | Successful result payload. |
No examples provided.
ask_about_code Ask About Code ~72
Answer questions about a cached file. Prerequisite: load_file. Auto-infer language.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Primary language (e.g. TypeScript, Python, JavaScript, Go, Rust, Java). Auto-infer from files. |
| question | string | yes | Question about the loaded file. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | Error payload when ok is false. |
| ok | boolean | yes | Whether the tool completed successfully. |
| result | object | – | Successful result payload. |
No examples provided.
detect_api_breaking_changes Detect API Breaking Changes ~60
Detect breaking API changes. Prerequisite: generate_diff. Auto-infer language.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Primary language (e.g. TypeScript, Python, JavaScript, Go, Rust, Java). Auto-infer from files. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | Error payload when ok is false. |
| ok | boolean | yes | Whether the tool completed successfully. |
| result | object | – | Successful result payload. |
No examples provided.
detect_code_smells Detect Code Smells ~63
Detect structural code smells in a cached file. Prerequisite: load_file. Auto-infer language.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Primary language (e.g. TypeScript, Python, JavaScript, Go, Rust, Java). Auto-infer from files. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | Error payload when ok is false. |
| ok | boolean | yes | Whether the tool completed successfully. |
| result | object | – | Successful result payload. |
No examples provided.
generate_diff Generate Diff ~98
Generate a diff of the current branch working changes and cache it for all review tools. You MUST call this tool before calling any other review tool. Use "unstaged" for working-tree changes not yet staged, or "staged" for changes already added with git add.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | "unstaged": working-tree changes not yet staged. "staged": changes added to the index with git add. Default: unstaged. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | Error payload when ok is false. |
| ok | boolean | yes | Whether the tool completed successfully. |
| result | object | – | Successful result payload. |
No examples provided.
generate_documentation Generate Documentation ~66
Generate documentation stubs for all public exports in a cached file. Prerequisite: load_file. Auto-infer language.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Primary language (e.g. TypeScript, Python, JavaScript, Go, Rust, Java). Auto-infer from files. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | Error payload when ok is false. |
| ok | boolean | yes | Whether the tool completed successfully. |
| result | object | – | Successful result payload. |
No examples provided.
generate_review_summary Generate Review Summary ~63
Summarize diff and risk level. Prerequisite: generate_diff. Auto-infer repo/language.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Primary language (e.g. TypeScript, Python, JavaScript, Go, Rust, Java). Auto-infer from files. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | Error payload when ok is false. |
| ok | boolean | yes | Whether the tool completed successfully. |
| result | object | – | Successful result payload. |
No examples provided.
generate_test_plan Generate Test Plan ~101
Generate test cases. Prerequisite: generate_diff. Auto-infer repo/language/framework.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Primary language (e.g. TypeScript, Python, JavaScript, Go, Rust, Java). Auto-infer from files. |
| maxTestCases | integer | – | Max test cases (1-30). Default: 15. |
| testFramework | string | – | Test framework (jest, pytest, etc). Auto-infer. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | Error payload when ok is false. |
| ok | boolean | yes | Whether the tool completed successfully. |
| result | object | – | Successful result payload. |
No examples provided.
load_file Load File ~90
Cache a single file for analysis tools (refactor_code, ask_about_code, verify_logic). Overwrites previous cache. Path is relative to server working directory (e.g. src/index.ts) or absolute (e.g. /home/user/project/src/index.ts).
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | yes | File path relative to workspace root (e.g. src/index.ts) or absolute. Must be within workspace. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | Error payload when ok is false. |
| ok | boolean | yes | Whether the tool completed successfully. |
| result | object | – | Successful result payload. |
No examples provided.
refactor_code Refactor Code ~92
Analyze cached file for complexity, duplication, naming, and grouping improvements. Prerequisite: load_file. Set maxSuggestions to cap output (default 10).
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Primary language (e.g. TypeScript, Python, JavaScript, Go, Rust, Java). Auto-infer from files. |
| maxSuggestions | integer | – | Max suggestions (1-15). Default: 10. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | Error payload when ok is false. |
| ok | boolean | yes | Whether the tool completed successfully. |
| result | object | – | Successful result payload. |
No examples provided.
verify_logic Verify Logic ~89
Verify algorithms and logic in a cached file using Gemini code execution sandbox. Prerequisite: load_file. Auto-infer language.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Primary language (e.g. TypeScript, Python, JavaScript, Go, Rust, Java). Auto-infer from files. |
| question | string | yes | What to verify in the loaded file (e.g. algorithm correctness, edge cases). |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | Error payload when ok is false. |
| ok | boolean | yes | Whether the tool completed successfully. |
| result | object | – | Successful result payload. |
No examples provided.
web_search Web Search ~113
Google Search with Grounding. Set topic to scope results; responseStyle controls output length.
| Name | Type | Req | Description |
|---|---|---|---|
| maxChars | integer | – | Truncate response text to this many characters. Default: no truncation. |
| query | string | yes | Search query. |
| responseStyle | string | – | concise: 2-4 sentences. detailed: full explanation. bullets: list. code_focused: code snippets. |
| topic | string | – | Domain focus (e.g. "TypeScript", "Docker"). Set to avoid irrelevant results. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | Error payload when ok is false. |
| ok | boolean | yes | Whether the tool completed successfully. |
| result | object | – | Successful result payload. |
No examples provided.
What is the Code Lens MCP server?
Code Lens is an MCP server listed in the public MCP registry as io.github.j0hanz/code-lens. Gemini-powered MCP server for code analysis. This page covers its npm package (@j0hanz/code-lens-mcp).
Is the Code Lens MCP server safe to use?
Code Lens scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Code Lens MCP server expose?
Code Lens exposes 13 tools: generate_diff, analyze_pr_impact, generate_review_summary, generate_test_plan, analyze_time_space_complexity, and 8 more. Their descriptions and schemas cost roughly 1,031 tokens of context every time the server is loaded.
Is the Code Lens MCP server still maintained?
Code Lens is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Code Lens MCP server under?
Code Lens declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.