Loading the registry…
MCP Apply server implementation with Morph AI for intelligent code patching
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.
1 critical finding reported by osv-scanner. The composite score alone does not reflect this — read the per-scanner reports below.
npm: mcp-apply-server @ 1.1.1, 0 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- mcp-apply-server
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
0 findings · 0.5s
v2.0.11
7 findings · 7.7s
v0.3.74
3 findings · 1.0s
v0.1.0
0 findings · 3.1s
v0.1.0
0 findings · 3.1s
v0.1.0
0 findings · 7.3s
v0.71.0
34 findings · 0.3s
v2.3.8
73 findings · 7.4s
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 19, 2026 | Flagged49 | — | 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 Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 117 findings across every scanner that examined this package. None of the 1 finding rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 5 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.
2 CVE-2025-15284
Files: package-lock.json · reported by trivy
2 CVE-2026-2391
Files: package-lock.json · reported by trivy
2 CVE-2026-8723
Files: package-lock.json · reported by trivy
2 DATA_EXFIL_JS_FS_ACCESS
Files: /repo/src/index.ts · reported by cisco-skill-scanner
2 GHSA-23c5-xmqv-rm74
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-3jxr-9vmj-r5cp
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-3ppc-4f35-3m26
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-6rw7-vpxm-498p
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-7r86-cg39-jmmj
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-f886-m6hf-6m8v
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-mh99-v99m-4gvg
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-q8mj-m7cp-5q26
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-rgw5-rvv9-x895
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-v6h2-p8h4-qcjw
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-w7fw-mjwx-w883
Files: /repo/package-lock.json · reported by osv-scanner
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 AAK-SUPPLY-005
Files: package-lock.json · reported by agent-audit-kit
1 CVE-2025-66020
Files: package-lock.json · reported by trivy
1 CVE-2025-66414
Files: package-lock.json · reported by trivy
1 CVE-2025-69873
Files: package-lock.json · reported by trivy
1 CVE-2026-0621
Files: package-lock.json · reported by trivy
1 CVE-2026-11525
Files: package-lock.json · reported by trivy
1 CVE-2026-12151
Files: package-lock.json · reported by trivy
1 CVE-2026-12590
Files: package-lock.json · reported by trivy
1 CVE-2026-13697
Files: package-lock.json · reported by trivy
1 CVE-2026-14643
Files: package-lock.json · reported by trivy
1 CVE-2026-1525
Files: package-lock.json · reported by trivy
1 CVE-2026-1526
Files: package-lock.json · reported by trivy
1 CVE-2026-1527
Files: package-lock.json · reported by trivy
1 CVE-2026-1528
Files: package-lock.json · reported by trivy
1 CVE-2026-16728
Files: package-lock.json · reported by trivy
1 CVE-2026-16729
Files: package-lock.json · reported by trivy
1 CVE-2026-22036
Files: package-lock.json · reported by trivy
1 CVE-2026-2229
Files: package-lock.json · reported by trivy
1 CVE-2026-25536
Files: package-lock.json · reported by trivy
1 CVE-2026-31808
Files: package-lock.json · reported by trivy
1 CVE-2026-32630
Files: package-lock.json · reported by trivy
1 CVE-2026-32887
Files: package-lock.json · reported by trivy
1 CVE-2026-4923
Files: package-lock.json · reported by trivy
1 CVE-2026-4926
Files: package-lock.json · reported by trivy
1 CVE-2026-59952
Files: package-lock.json · reported by trivy
1 CVE-2026-6733
Files: package-lock.json · reported by trivy
1 CVE-2026-9678
Files: package-lock.json · reported by trivy
1 CVE-2026-9679
Files: package-lock.json · reported by trivy
1 GHSA-25h7-pfq9-p65f
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-27v5-c462-wpq7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-28wg-ghj8-5hjv
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2g4f-4pwh-qvx6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2mjp-6q6p-2qxm
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2v37-7h3g-55p8
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-345p-7cg4-v4c7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-35p6-xmwp-9g52
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-38f7-945m-qr2g
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3v7f-55p6-f55p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4992-7rv2-5pvq
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4cwx-7wf7-3272
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4w7w-66w2-5vf9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-52cp-r559-cp3m
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-5p4m-2wfm-xmqj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-5qjj-4xww-7phc
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-5v7r-6r5c-r473
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-5xrq-8626-4rwp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-67mh-4wv8-2f99
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-6g55-p6wh-862q
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-8r9q-7v3j-jr4g
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-8xcm-r25x-g524
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-93m4-6634-74q7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-c2c7-rcm5-vvqj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-f269-vfmq-vjvj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-fx2h-pf6j-xcff
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-fxqj-rqcc-2cmp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-g4jq-h2w9-997c
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-g8m3-5g58-fq7m
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-g9mf-h72j-4rw9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-h67p-54hq-rp68
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-j3q9-mxjg-w52f
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-j47w-4g3g-c36v
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-jqfw-vq24-v9c3
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-jr45-8vmc-qm54
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-m8rv-5g2x-5cg5
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-mh29-5h37-fv8m
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-mw96-cpmx-2vgc
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-p88m-4jfj-68fv
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-pr7r-676h-xcf6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-qx2v-qp2m-jg93
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-r28c-9q8g-f849
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-rf6f-7fwh-wjgh
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v3r7-h72x-cjcm
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v422-hmwv-36x6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v6wh-96g9-6wx3
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v9p9-hfj2-hcw8
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-vqpr-j7v3-hqw9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-vrm6-8vpv-qv8q
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-vxpw-j846-p89q
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w48q-cv73-mx4w
Files: /repo/package-lock.json · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
1 UNANALYZABLE_BINARY
Files: /repo/bun.lockb · reported by cisco-skill-scanner
4 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-SEC-MD-001, SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE and 1 more · Files: SECURITY.md, /repo/SKILL.md, /repo/bun.lockb · reported by agent-audit-kit, cisco-skill-scanner
1 The model did not answer for these findings.
Rules: CVE-2026-15157 · Files: package-lock.json · reported by trivy
Critical vulnerability and high severity risks identified.
The artifact contains a critical vulnerability (GHSA-5xrq-8626-4rwp) in a dependency, which could lead to severe system compromise. High severity findings from the `bearer` scanner in `src/index.ts` also indicate potential for insecure operations or sensitive data handling within the artifact's own code. These issues collectively present significant security risks.
Concern level assessed by the review: Critical. 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.
Showing 23 of 23; the rest are in the per-scanner reports above.