Loading the registry…
Last9 MCP Server - Model Context Protocol server implementation for Last9
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.
4 critical findings reported by cisco-skill-scanner. The composite score alone does not reflect this — read the per-scanner reports below.
github_release: https://github.com/last9/last9-mcp-server, 0 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- @last9/mcp-server
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
10 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.8s
v2.0.11
20 findings · 9.7s
v0.3.74
7 findings · 6.2s
v0.2.0
2 findings · 6.4s
v0.2.0
1 finding · 6.5s
vv0.3.2
Incomplete run
0 findings · 3.4s
v0.1.0
0 findings · 20.2s
v0.71.0
1 finding · 0.3s
v2.3.8
47 findings · 0.9s
vv1.6.0
Incomplete run
0 findings · 2.4s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
8 scans on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Sep 22, 2026 | Flagged78 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·!: incompletenerlo-multi-source: completetrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·!: incomplete | completed |
| Aug 2, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completenerlo-multi-source: complete | rejected |
| Jul 30, 2026 | Scan Halted | — | cisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completenerlo-multi-source: complete | rejected |
| Jul 21, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: complete | rejected |
| Jul 20, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: complete | rejected |
| Jul 20, 2026 | Scan Halted | Clean → Flagged | agentshield: completecisco-skill-scanner: completeagent-audit-kit: complete | rejected |
| Jul 20, 2026 | Clean100 | — | agentshield ·n/a: not applicablecisco-skill-scanner ·n/a: not applicableagent-audit-kit: completetrivy: completeosv-scanner ·n/a: not applicable | completed |
| Jul 20, 2026 | Clean100 | — | agentshield ·n/a: not applicablecisco-skill-scanner ·n/a: not applicableagent-audit-kit: completetrivy: completeosv-scanner ·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 78 findings across every scanner that examined this package. None of the 4 findings rated critical by their scanner were dismissed.
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.
3 Agent instruction file — The match is in a file that instructs an AI coding agent — a CLAUDE.md or similar. It is documentation of intent, and our own check confirmed it is not part of what gets installed.
Rules: AAK-AGENT-002, FILE_MAGIC_MISMATCH, opt.nerlo-rules.nerlo-install-run-bundled-artifact · Files: AGENTS.md, /repo/CLAUDE.md, /repo/AGENTS.md · reported by agent-audit-kit, cisco-skill-scanner, nerlo-install-instruction
3 CI or editor configuration — The match is in build, CI or editor configuration, confirmed by our own check to be outside the installed artifact.
Rules: AAK-GHA-IMMUTABLE-001 · Files: .github/workflows/release.yaml · reported by agent-audit-kit
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.
5 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/contracts/SKILL.md, /repo/internal/prompts/descriptions/SKILL.md and 2 more · reported by cisco-skill-scanner
5 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/contracts/SKILL.md, /repo/internal/prompts/descriptions/SKILL.md and 2 more · reported by cisco-skill-scanner
4 COMMAND_INJECTION_JS_CHILD_PROCESS
Files: /repo/bin/cli.js, /repo/bin/download-binary.js · reported by cisco-skill-scanner
2 FILE_MAGIC_MISMATCH
Files: /repo/internal/prompts/workflows/on_call_runbook.md · reported by cisco-skill-scanner
2 opt.nerlo-rules.nerlo-dynamic-exec
Files: /repo/bin/download-binary.js · reported by nerlo-behavioral
1 AAK-SEC-MD-001
Files: SECURITY.md · reported by agent-audit-kit
1 AAK-SECRET-004
Files: internal/telemetry/logs/attributes_for_pipeline.go · reported by agent-audit-kit
1 AAK-SUPPLY-004
Files: package.json · reported by agent-audit-kit
1 CVE-2026-39882
Files: go.mod · reported by trivy
1 DATA_EXFIL_JS_NETWORK
Files: /repo/bin/download-binary.js · reported by cisco-skill-scanner
1 EXCESSIVE_FILE_COUNT
Files: /repo/. · reported by cisco-skill-scanner
1 GO-2025-3955
Files: /repo/go.mod · reported by osv-scanner
1 GO-2025-4006
Files: /repo/go.mod · reported by osv-scanner
1 GO-2025-4007
Files: /repo/go.mod · reported by osv-scanner
1 GO-2025-4008
Files: /repo/go.mod · reported by osv-scanner
1 GO-2025-4009
Files: /repo/go.mod · reported by osv-scanner
1 GO-2025-4010
Files: /repo/go.mod · reported by osv-scanner
1 GO-2025-4011
Files: /repo/go.mod · reported by osv-scanner
1 GO-2025-4012
Files: /repo/go.mod · reported by osv-scanner
1 GO-2025-4013
Files: /repo/go.mod · reported by osv-scanner
1 GO-2025-4014
Files: /repo/go.mod · reported by osv-scanner
1 GO-2025-4015
Files: /repo/go.mod · reported by osv-scanner
1 GO-2025-4155
Files: /repo/go.mod · reported by osv-scanner
1 GO-2025-4175
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4337
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4340
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4341
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4342
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4601
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4602
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4603
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4864
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4865
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4869
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4870
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4918
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4946
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4947
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4970
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4971
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4976
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4977
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4980
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4981
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4982
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4985
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4986
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-5026
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-5037
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-5038
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-5039
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-5856
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-5972
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-6088
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-6089
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-6090
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-6091
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-6218
Files: /repo/go.mod · reported by osv-scanner
1 OVERSIZED_FILE
Files: /repo/mcp-demo.gif · reported by cisco-skill-scanner
Critical command injection and dynamic execution capabilities detected.
Critical command injection vulnerabilities are present in `/repo/bin/cli.js` and `/repo/bin/download-binary.js`, enabling shell execution. Dynamic code execution capabilities are also identified in `/repo/bin/download-binary.js`. A high-severity finding indicates potential credential access via `internal/telemetry/logs/attributes_for_pipeline.go`. Additionally, multiple medium-severity findings include file magic mismatches and known vulnerabilities in dependencies.
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.