Loading the registry…
File editing specialized MCP server for Claude Code
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
npm: mcp-file-editor @ 1.0.0, 0 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- mcp-file-editor
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
8 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v1.4.0
4 findings · 1.2s
v2.0.11
7 findings · 8.2s
v0.3.74
4 findings · 1.1s
v0.1.0
0 findings · 3.7s
v0.1.0
0 findings · 3.7s
v0.1.0
0 findings · 8.0s
v0.71.0
1 finding · 0.2s
v2.3.8
1 finding · 9.0s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Caution89 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source: completetrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Caution badge are computed from those raw severities alone. Nothing below moved them.
Out of 17 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 7 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
The model could have called any of these a false positive and did not.
4 DATA_EXFIL_JS_FS_ACCESS
Files: /repo/src/handlers.ts · reported by cisco-skill-scanner
1 AAK-ANTHROPIC-SDK-001
Files: src/index.ts · reported by agent-audit-kit
1 AAK-DNS-REBIND-002
Files: package.json · reported by agent-audit-kit
1 AAK-OAUTH-3P-001
Files: package.json · reported by agent-audit-kit
1 CVE-2025-66414
Files: package-lock.json · reported by trivy
1 GHSA-w48q-cv73-mx4w
Files: /repo/package-lock.json · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
6 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: permissions-no-block, hooks-no-stop-hooks, AAK-SEC-MD-001 and 1 more · Files: settings.json, .claude/settings.json, SECURITY.md and 1 more · reported by agentshield, agent-audit-kit, cisco-skill-scanner
1 The model did not answer for these findings.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION · Files: /repo/SKILL.md · reported by cisco-skill-scanner
Artifact has high-severity vulnerabilities and potential for DNS rebinding.
The artifact contains a high-severity DNS rebinding vulnerability identified in `package.json` and uses the Anthropic SDK in `src/index.ts`, which warrants attention. Multiple high-severity findings from the 'bearer' scanner are present in `src/handlers.ts` and `src/validation.ts`, indicating potential issues with sensitive data handling or insecure configurations. Additionally, the artifact includes dependencies with known high-severity vulnerabilities, specifically `GHSA-w48q-cv73-mx4w` and `CVE-2025-66414`, as noted in `package-lock.json`.
Concern level assessed by the review: High. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.