MCP server for crawling web pages and converting to markdown
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.
2 critical findings reported by osv-scanner. The composite score alone does not reflect this — read the per-scanner reports below.
npm: crawl-page-mcp-server @ 1.0.6, 0 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- crawl-page-mcp-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
12 findings · 7.7s
v0.3.74
7 findings · 2.1s
v0.1.0
0 findings · 3.5s
v0.1.0
1 finding · 3.5s
v0.1.0
0 findings · 6.8s
v0.71.0
102 findings · 0.3s
v2.3.8
192 findings · 7.1s
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 | Flagged46 | — | 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 314 findings across every scanner that examined this package. None of the 2 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 8 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
5 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE, opt.nerlo-rules.nerlo-install-run-bundled-artifact · Files: /repo/test/SKILL.md, /repo/docs/SKILL.md, /repo/docs/quick-start.md · reported by cisco-skill-scanner, nerlo-install-instruction
2 Test or fixture file — The match is in a test or fixture. Our own check confirmed the file is not part of what gets installed.
Rules: LOW_ANALYZABILITY, DATA_EXFIL_JS_FS_ACCESS · Files: /repo/test, /repo/test/test-windows-compatibility.js · reported by cisco-skill-scanner
The model could have called any of these a false positive and did not.
6 GHSA-23c5-xmqv-rm74
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
6 GHSA-3ppc-4f35-3m26
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
6 GHSA-7r86-cg39-jmmj
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-2g4f-4pwh-qvx6
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-3jxr-9vmj-r5cp
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-3v7f-55p6-f55p
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4
4 The model did not answer for these findings.
Rules: CVE-2026-44488, GHSA-fxqj-rqcc-2cmp · Files: package-lock.json, pnpm-lock.yaml, /repo/package-lock.json and 1 more · reported by trivy, osv-scanner
4 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-MCP-ATTEST-001, AAK-SEC-MD-001, SOCIAL_ENG_VAGUE_DESCRIPTION and 1 more · Files: mcp-config-example.json, SECURITY.md, /repo/SKILL.md · reported by agent-audit-kit, cisco-skill-scanner
Critical dependency vulnerability and network risks.
The artifact has a critical vulnerability in its dependencies, identified in `package-lock.json` and `pnpm-lock.yaml`. It also contains code that could facilitate DNS rebinding attacks, potentially leading to unauthorized network egress or access to internal services. The use of the Anthropic SDK in `src/index.ts` implies network egress for API calls and handling of API credentials.
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.
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml, package-lock.json and 1 more · reported by osv-scanner, trivy
4 GHSA-7q8q-rj6j-mhjq
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml, package-lock.json and 1 more · reported by osv-scanner, trivy
4 GHSA-c2c7-rcm5-vvqj
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-f886-m6hf-6m8v
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-jqh4-m9w3-8hp9
Files: package-lock.json, pnpm-lock.yaml, /repo/package-lock.json and 1 more · reported by trivy, osv-scanner
4 GHSA-mh99-v99m-4gvg
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-mmx7-hfxf-jppx
Files: package-lock.json, pnpm-lock.yaml, /repo/package-lock.json and 1 more · reported by trivy, osv-scanner
4 GHSA-pmv8-rq9r-6j72
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml, package-lock.json and 1 more · reported by osv-scanner, trivy
4 GHSA-r4q5-vmmm-2653
Files: package-lock.json, pnpm-lock.yaml, /repo/package-lock.json and 1 more · reported by trivy, osv-scanner
4 GHSA-rgw5-rvv9-x895
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 CVE-2025-15284
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2025-58754
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2025-62718
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2025-66414
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-11525
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-12143
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-12151
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-13697
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-14643
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-15157
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-1525
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-1526
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-1527
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-1528
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-16728
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-16729
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-22036
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-2229
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-2391
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-25639
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-40175
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-42033
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-42034
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-42035
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-42036
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-42037
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-42038
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-42039
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-42040
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-42041
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-42042
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-42043
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-42044
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-42264
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-44486
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-44487
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-44490
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-44494
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-44495
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-44496
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-6733
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-8723
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-9678
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-9679
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 DATA_EXFIL_JS_FS_ACCESS
Files: /repo/scripts/add-shebang.js · reported by cisco-skill-scanner
2 GHSA-25h7-pfq9-p65f
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-28wg-ghj8-5hjv
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-2mjp-6q6p-2qxm
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-2v37-7h3g-55p8
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-35jp-ww65-95wh
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-35p6-xmwp-9g52
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3g43-6gmg-66jw
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3p68-rc4w-qgx5
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3qcw-2rhx-2726
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3w6x-2g7m-8v23
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-43fc-jf86-j433
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-445q-vr5w-6q77
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-4992-7rv2-5pvq
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-4c8g-83qw-93j6
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-4cwx-7wf7-3272
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-4hjh-wcwx-xvwj
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-52cp-r559-cp3m
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-5c9x-8gcm-mpgx
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-5p4m-2wfm-xmqj
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-62hf-57xw-28j9
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-6chq-wfr3-2hj9
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-6g55-p6wh-862q
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-6rw7-vpxm-498p
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-777c-7fjr-54vf
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-7h2j-956f-4vf2
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-7p8r-x3mc-p8w7
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-898c-q2cr-xwhg
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-8xcm-r25x-g524
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-f23m-r3pf-42rh
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-f269-vfmq-vjvj
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-fvcv-3m26-pcqx
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-g8m3-5g58-fq7m
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-g9mf-h72j-4rw9
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-h67p-54hq-rp68
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-hcf7-66rw-9f5r
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-hfxv-24rg-xrqf
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-hmw2-7cc7-3qxx
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-j5f8-grm9-p9fc
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-jr45-8vmc-qm54
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-m7pr-hjqh-92cm
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-m8rv-5g2x-5cg5
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-mh29-5h37-fv8m
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-p88m-4jfj-68fv
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-p92q-9vqr-4j8v
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-pf86-5x62-jrwf
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-pmwg-cvhr-8vh7
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-pr7r-676h-xcf6
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-q3j6-qgpj-74h6
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-q8mj-m7cp-5q26
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-q8qp-cvcw-x6jj
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-qx2v-qp2m-jg93
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-r28c-9q8g-f849
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-r5fr-rjxr-66jc
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-rf6f-7fwh-wjgh
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-v2hh-gcrm-f6hx
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-v39h-62p7-jpjc
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-v3r7-h72x-cjcm
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-v9p9-hfj2-hcw8
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-vf2m-468p-8v99
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-vrm6-8vpv-qv8q
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-vxpw-j846-p89q
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-w48q-cv73-mx4w
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-w7fw-mjwx-w883
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-w9j2-pvgh-6h63
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-xhjh-pmcv-23jw
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-xx6v-rp6x-q39c
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-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-MCP-SSRF-001
Files: src/index.ts · reported by agent-audit-kit
1 AAK-OAUTH-3P-001
Files: package.json · reported by agent-audit-kit
1 AAK-SUPPLY-005
Files: package-lock.json · reported by agent-audit-kit
1 DATA_EXFIL_JS_NETWORK
Files: /repo/src/index.ts · reported by cisco-skill-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
Showing 25 of 146; the rest are in the per-scanner reports above.