Loading the registry…
Model Context Protocol server for Slack integration
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: slack-mcp @ 1.0.0, 0 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- slack-mcp
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.6s
v2.0.11
5 findings · 7.3s
v0.3.74
8 findings · 1.2s
v0.1.0
0 findings · 4.2s
v0.1.0
0 findings · 4.2s
v0.1.0
0 findings · 8.3s
v0.71.0
95 findings · 0.3s
v2.3.8
95 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 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 203 findings across every scanner that examined this package.
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: AAK-MCP-003, AAK-MCP-ATTEST-001, AAK-SECRET-007 and 2 more · Files: examples/mcp-config.json, /repo/examples/SKILL.md · reported by agent-audit-kit, cisco-skill-scanner
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 CVE-2025-15284
Files: package-lock.json, yarn.lock · reported by trivy
4 CVE-2026-12590
Files: package-lock.json, yarn.lock · reported by trivy
4 CVE-2026-2391
Files: package-lock.json, yarn.lock · reported by trivy
4 CVE-2026-8723
Files: package-lock.json, yarn.lock · reported by trivy
4 GHSA-42h9-826w-cgv3
Files: /repo/package-lock.json, /repo/yarn.lock, package-lock.json and 1 more · reported by osv-scanner, trivy
4 GHSA-6rw7-vpxm-498p
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
4 GHSA-7q8q-rj6j-mhjq
Files: /repo/package-lock.json, /repo/yarn.lock, package-lock.json and 1 more · reported by osv-scanner, trivy
Multiple high-severity vulnerabilities in dependencies
This artifact contains numerous high-severity vulnerabilities primarily within its dependencies, as identified by `osv-scanner` and `trivy`. These vulnerabilities could lead to various impacts, including remote code execution, denial of service, or information disclosure. Reviewing the specific findings is essential to understand the full scope of potential 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.
4 GHSA-jqh4-m9w3-8hp9
Files: package-lock.json, yarn.lock, /repo/package-lock.json and 1 more · reported by trivy, osv-scanner
4 GHSA-mmx7-hfxf-jppx
Files: package-lock.json, yarn.lock, /repo/package-lock.json and 1 more · reported by trivy, osv-scanner
4 GHSA-pmv8-rq9r-6j72
Files: /repo/package-lock.json, /repo/yarn.lock, package-lock.json and 1 more · reported by osv-scanner, trivy
4 GHSA-q8mj-m7cp-5q26
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
4 GHSA-r4q5-vmmm-2653
Files: package-lock.json, yarn.lock, /repo/package-lock.json and 1 more · reported by trivy, osv-scanner
4 GHSA-v422-hmwv-36x6
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
4 GHSA-w7fw-mjwx-w883
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
3 CVE-2026-12143
Files: package-lock.json, yarn.lock · reported by trivy
3 GHSA-hmw2-7cc7-3qxx
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 CVE-2025-13466
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2025-62718
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2025-66414
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2025-69873
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-0621
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-25536
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-25639
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-40175
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-42033
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-42034
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-42035
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-42036
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-42037
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-42038
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-42039
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-42040
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-42041
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-42042
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-42043
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-42044
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-42264
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-44486
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-44487
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-44488
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-44490
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-44494
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-44495
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-44496
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-4867
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-4923
Files: package-lock.json, yarn.lock · reported by trivy
2 CVE-2026-4926
Files: package-lock.json, yarn.lock · reported by trivy
2 GHSA-27v5-c462-wpq7
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-2g4f-4pwh-qvx6
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-345p-7cg4-v4c7
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-35jp-ww65-95wh
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-37ch-88jc-xwx2
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-3g43-6gmg-66jw
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-3p68-rc4w-qgx5
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-3w6x-2g7m-8v23
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-43fc-jf86-j433
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-445q-vr5w-6q77
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-5c9x-8gcm-mpgx
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-62hf-57xw-28j9
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-6chq-wfr3-2hj9
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-777c-7fjr-54vf
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-898c-q2cr-xwhg
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-8r9q-7v3j-jr4g
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-fvcv-3m26-pcqx
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-hfxv-24rg-xrqf
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-j3q9-mxjg-w52f
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-j5f8-grm9-p9fc
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-m7pr-hjqh-92cm
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-p92q-9vqr-4j8v
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-pf86-5x62-jrwf
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-pmwg-cvhr-8vh7
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-q8qp-cvcw-x6jj
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-vf2m-468p-8v99
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-w48q-cv73-mx4w
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-w9j2-pvgh-6h63
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-wqch-xfxh-vrr4
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-xhjh-pmcv-23jw
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
2 GHSA-xx6v-rp6x-q39c
Files: /repo/package-lock.json, /repo/yarn.lock · reported by osv-scanner
1 AAK-DNS-REBIND-002
Files: package.json · reported by agent-audit-kit
1 AAK-MCP-018
Files: src/server.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 AAK-SUPPLY-005
Files: package-lock.json · reported by agent-audit-kit
1 CVE-2025-65945
Files: yarn.lock · reported by trivy
1 CVE-2026-48779
Files: yarn.lock · reported by trivy
1 GHSA-869p-cjfg-cm3x
Files: /repo/yarn.lock · reported by osv-scanner
1 GHSA-96hv-2xvq-fx4p
Files: /repo/yarn.lock · 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
Showing 25 of 77; the rest are in the per-scanner reports above.