io.github.radwanalmsora/devlens-mcp
NPM · @RADWANALMSORA26/DEVLENS-MCP
Production TypeScript & JavaScript AST code analysis and risk assessment MCP server.
Available components
Last scanned (21 hours ago)
Scores higher than 31% of npm servers
Category Developer Tools
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 41 of 113 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 230 tokens (~28/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 58
First indexed and scored.
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 4 Nov 2026 · Analysed npm/@radwanalmsora26/devlens-mcp@0.1.6
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 113 packages
| Packages resolved | 113 |
|---|---|
| Stale | 41 |
| 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_impact ~32
Identify files affected by modifying a target module (blast radius).
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | yes | Modified file path. |
No output schema declared.
No examples provided.
analyze_project ~22
Map project structure, detect frameworks, package manager, and language distribution.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
assess_change_risk ~41
Assess modification risk (LOW/MEDIUM/HIGH/CRITICAL) using complexity and dependency signals.
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | yes | Target file path. |
No output schema declared.
No examples provided.
detect_dead_code ~18
Identify unreferenced exports within the project.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
find_symbol ~46
Locate functions, classes, interfaces, types, and variables across the project.
| Name | Type | Req | Description |
|---|---|---|---|
| exactMatch | boolean | – | Require exact match. |
| name | string | yes | Symbol name to search for. |
No output schema declared.
No examples provided.
get_project_context ~22
Return concise, token-optimized project context for AI coding agents.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_project_diagnostics ~18
Report broken imports and circular dependency loops.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
trace_dependencies ~31
Trace incoming, outgoing, and external dependencies of a file.
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | yes | Target file path. |
No output schema declared.
No examples provided.
How do I install the io.github.radwanalmsora/devlens-mcp server?
io.github.radwanalmsora/devlens-mcp runs locally as an npm package, launched with npx -y @radwanalmsora26/devlens-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 · @radwanalmsora26/devlens-mcp
claude mcp add radwanalmsora-devlens-mcp -- npx -y @radwanalmsora26/devlens-mcp
What is the io.github.radwanalmsora/devlens-mcp server?
io.github.radwanalmsora/devlens-mcp is listed in the public MCP registry as io.github.radwanalmsora/devlens-mcp. Production TypeScript & JavaScript AST code analysis and risk assessment MCP server. This page covers its npm package (@radwanalmsora26/devlens-mcp).
Is the io.github.radwanalmsora/devlens-mcp server safe to use?
io.github.radwanalmsora/devlens-mcp scores 61 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. 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 io.github.radwanalmsora/devlens-mcp server expose?
io.github.radwanalmsora/devlens-mcp exposes 8 tools: analyze_project, find_symbol, trace_dependencies, analyze_impact, detect_dead_code, and 3 more. Their descriptions and schemas cost roughly 230 tokens of context every time the server is loaded.
Is the io.github.radwanalmsora/devlens-mcp server still maintained?
io.github.radwanalmsora/devlens-mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 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 io.github.radwanalmsora/devlens-mcp server under?
io.github.radwanalmsora/devlens-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.