Loading the registry…
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.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- Rule-MCP-Server
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
5 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.
v2.0.11
20 findings · 10.7s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·!: incompletenerlo-multi-source ·n/a: not applicable | rejected |
Per-scanner history:
v0.3.74
23 findings · 5.0s
v0.1.0
0 findings · 6.0s
v0.1.0
0 findings · 6.0s
vv0.3.2
Incomplete run
0 findings · 3.2s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 0.9s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
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 43 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 43 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
42 The review call did not complete.
Rules: AAK-MCP-STDIO-LAUNCHER-INJECT-001, AAK-SECRET-004, AAK-MCP-003 and 12 more · Files: config/standard-mcp-config.json, config/docker-mcp-config.template.json, config/simple-mcp-config.json and 21 more · reported by agent-audit-kit, cisco-skill-scanner
1 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: BINARY_FILE_DETECTED · Files: /repo/frontend/src/stories/assets/avif-test-image.avif · reported by cisco-skill-scanner
Critical vulnerability, shell execution, and credential exposure detected.
A critical vulnerability is present in `/repo/cmd/server/main.go`. Multiple high-severity findings indicate potential shell execution via `AAK-MCP-STDIO-LAUNCHER-INJECT-001` in several `config/*.json` files. Credential exposure is possible through `AAK-SECRET-004` in `frontend/src/i18n/locales/*.json`. Additional high-severity findings are noted in `config/mcp-client-config.json` and `/repo/internal/usecase/project_detection.go`.
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.