Loading the registry…
MCP Server for extracting politician stock trades with prices from Capitol Trades. No API key required.
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: @anguslin/mcp-capitol-trades @ 1.0.1, 0 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- @anguslin/mcp-capitol-trades
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.9s
v2.0.11
7 findings · 9.1s
v0.3.74
4 findings · 1.5s
v0.1.0
0 findings · 4.7s
v0.1.0
0 findings · 4.7s
v0.1.0
0 findings · 9.3s
v0.71.0
47 findings · 0.2s
v2.3.8
47 findings · 7.9s
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 21, 2026 | Flagged47 | — | 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 105 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.
4 DATA_EXFIL_JS_NETWORK
Files: /repo/src/politician-trades-scraper.ts, /repo/src/web-scraper.ts · reported by cisco-skill-scanner
2 GHSA-42h9-826w-cgv3
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-7q8q-rj6j-mhjq
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-jqh4-m9w3-8hp9
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-mmx7-hfxf-jppx
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-pmv8-rq9r-6j72
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-r4q5-vmmm-2653
Files: package-lock.json, /repo/package-lock.json · reported by trivy, 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-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-2025-62718
Files: package-lock.json · reported by trivy
1 CVE-2025-66414
Files: package-lock.json · reported by trivy
1 CVE-2026-12143
Files: package-lock.json · reported by trivy
1 CVE-2026-12151
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-15157
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-25639
Files: package-lock.json · reported by trivy
1 CVE-2026-40175
Files: package-lock.json · reported by trivy
1 CVE-2026-42033
Files: package-lock.json · reported by trivy
1 CVE-2026-42034
Files: package-lock.json · reported by trivy
1 CVE-2026-42035
Files: package-lock.json · reported by trivy
1 CVE-2026-42036
Files: package-lock.json · reported by trivy
1 CVE-2026-42037
Files: package-lock.json · reported by trivy
1 CVE-2026-42038
Files: package-lock.json · reported by trivy
1 CVE-2026-42039
Files: package-lock.json · reported by trivy
1 CVE-2026-42040
Files: package-lock.json · reported by trivy
1 CVE-2026-42041
Files: package-lock.json · reported by trivy
1 CVE-2026-42042
Files: package-lock.json · reported by trivy
1 CVE-2026-42043
Files: package-lock.json · reported by trivy
1 CVE-2026-42044
Files: package-lock.json · reported by trivy
1 CVE-2026-42264
Files: package-lock.json · reported by trivy
1 CVE-2026-44486
Files: package-lock.json · reported by trivy
1 CVE-2026-44487
Files: package-lock.json · reported by trivy
1 CVE-2026-44488
Files: package-lock.json · reported by trivy
1 CVE-2026-44490
Files: package-lock.json · reported by trivy
1 CVE-2026-44494
Files: package-lock.json · reported by trivy
1 CVE-2026-44495
Files: package-lock.json · reported by trivy
1 CVE-2026-44496
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-2mjp-6q6p-2qxm
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-35jp-ww65-95wh
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-3g43-6gmg-66jw
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3p68-rc4w-qgx5
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3w6x-2g7m-8v23
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-43fc-jf86-j433
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-445q-vr5w-6q77
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-5c9x-8gcm-mpgx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-62hf-57xw-28j9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-6chq-wfr3-2hj9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-777c-7fjr-54vf
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-898c-q2cr-xwhg
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-f269-vfmq-vjvj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-fvcv-3m26-pcqx
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-hfxv-24rg-xrqf
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-hmw2-7cc7-3qxx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-j5f8-grm9-p9fc
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-m7pr-hjqh-92cm
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-p88m-4jfj-68fv
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-p92q-9vqr-4j8v
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-pf86-5x62-jrwf
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-pmwg-cvhr-8vh7
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-q8qp-cvcw-x6jj
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-v9p9-hfj2-hcw8
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-vf2m-468p-8v99
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 GHSA-w9j2-pvgh-6h63
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xhjh-pmcv-23jw
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xx6v-rp6x-q39c
Files: /repo/package-lock.json · 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-11525
Files: package-lock.json · reported by trivy
Multiple high-severity vulnerabilities and risky capabilities detected.
The artifact contains numerous high-severity vulnerabilities in its dependencies, identified across various `package-lock.json` files. Additionally, it exhibits risky capabilities, including potential for DNS rebinding via `package.json` and the use of the Anthropic SDK in `src/index.ts`, which implies network egress and credential access. These findings warrant careful review before installation.
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.
Showing 25 of 39; the rest are in the per-scanner reports above.