Loading the registry…
MCP server for LDBD — submit asset price-direction predictions from Claude Desktop or Claude Code
The publisher performed an authenticated act of publication — proving control of a namespace in the official MCP registry, or appearing in a first-party catalogue an operator curates. That establishes WHO published it. It is not a security finding, and attested artifacts carry Flagged verdicts too.
npm: mcp-ldbd @ 0.3.0, 0 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- mcp-ldbd
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.7s
v2.0.11
5 findings · 8.5s
v0.3.74
5 findings · 1.0s
v0.2.0
2 findings · 4.6s
v0.2.0
0 findings · 4.6s
v0.1.0
0 findings · 9.2s
v0.71.0
38 findings · 0.3s
v2.3.8
38 findings · 10.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
2 scans on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Sep 11, 2026 | Flagged43 | — | 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 |
| Jul 31, 2026 | Flagged43 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completenerlo-multi-source: completetrivy: completeosv-scanner: completetrivy_image ·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 88 findings across every scanner that examined this package.
These findings are in files this artifact installs and are not placeholder values. No false-positive basis can be corroborated for such a finding, so this review never dismisses one; they were not sent to the model and stand at their scanner's severity.
2 DATA_EXFIL_JS_NETWORK
Files: /repo/src/index.ts · reported by cisco-skill-scanner
2 GHSA-frvp-7c67-39w9
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 opt.nerlo-rules.nerlo-js-secret-to-network-egress
Files: /repo/src/index.ts · reported by nerlo-behavioral
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-SEC-MD-001
Files: SECURITY.md · reported by agent-audit-kit
1 CVE-2026-12590
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-13676
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-16221
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-18446
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42338
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44455
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44456
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44457
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44458
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44459
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-47673
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-47674
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-47675
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-47676
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-54286
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-54287
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-54288
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-54289
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-54290
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59895
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59896
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59897
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-6321
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-6322
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-69192
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-69207
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-71848
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-71849
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-71850
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-76172
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-82417
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-82562
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-84363
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-84364
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-84365
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-8723
Files: pnpm-lock.yaml · reported by trivy
1 GHSA-2gcr-mfcq-wcc3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3hrh-pfw6-9m5x
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4c8g-83qw-93j6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4mjr-xmp4-gh2g
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-54fx-42gc-7vw4
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-69xw-7hcm-h432
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-79qm-7rj5-m7r9
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-7p8r-x3mc-p8w7
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-88fw-hqm2-52qc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8j4g-w8fx-2239
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-9vqf-7f2p-gf9v
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-crvj-82cr-hjcx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-f23p-vx2j-j53r
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-f577-qrjj-4474
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-f65p-4m7j-42xc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-g6gw-c38x-mqfc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-gqvv-2mrq-wpjv
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-hm8q-7f3q-5f36
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-hvrm-45r6-mjfj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-j6c9-x7qj-28xf
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-jqff-g426-hqxp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mwp4-54f8-5fhr
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-p77w-8qqv-26rm
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-q3j6-qgpj-74h6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-q8mj-m7cp-5q26
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-qp7p-654g-cw7p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-rv63-4mwf-qqc2
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v2hh-gcrm-f6hx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v2v4-37r5-5v8g
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v39h-62p7-jpjc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v422-hmwv-36x6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-w62v-xxxg-mg59
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-wgpf-jwqj-8h8p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-wwfh-h76j-fc44
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-x5fp-wj9c-mxmx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xgm2-5f3f-mvvc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xrhx-7g5j-rcj5
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
1 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · reported by cisco-skill-scanner
The model could have called any of these a false positive and did not.
1 CVE-2026-75975
Files: pnpm-lock.yaml · reported by trivy
Critical vulnerabilities, credential access, and network egress detected.
The artifact contains multiple high-severity vulnerabilities, including two instances where secrets are sent over the network from `/repo/src/index.ts`. A DNS rebinding vulnerability was identified in `package.json`, and an Anthropic SDK is used in `src/index.ts`. Additionally, numerous high-severity vulnerabilities in dependencies, as listed in `pnpm-lock.yaml`, warrant attention.
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.