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.
1 critical finding reported by agent-audit-kit. The composite score alone does not reflect this — read the per-scanner reports below.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- hubble-mcp-servers
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.
v1.4.0
0 findings · 0.6s
v2.0.11
5 findings · 7.8s
v0.3.74
7 findings · 1.5s
v0.1.0
0 findings · 3.9s
v0.1.0
0 findings · 3.9s
vv0.3.2
No Go packages 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 · 1.0s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
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: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicable | rejected |
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 12 findings across every scanner that examined this package. None of the 1 finding rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 6 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
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.
1 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/fly-preview.yml · reported by agent-audit-kit
The model could have called any of these a false positive and did not.
2 AAK-LOGINJ-001
Files: motherduck/mcp_server/server.py · reported by agent-audit-kit
1 AAK-DNS-REBIND-001
Files: motherduck/mcp_server/__init__.py · reported by agent-audit-kit
1 AAK-IPI-WILD-CORPUS-001
Files: motherduck/mcp_server/prompt.py · reported by agent-audit-kit
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
6 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-SEC-MD-001, HIDDEN_DATA_FILE, SOCIAL_ENG_VAGUE_DESCRIPTION and 1 more · Files: SECURITY.md, /repo/.prettierrc.json, /repo/SKILL.md and 1 more · reported by agent-audit-kit, cisco-skill-scanner
Critical DNS rebind vulnerability and insecure process invocation.
The artifact exhibits a critical DNS rebind vulnerability in `motherduck/mcp_server/__init__.py`, which could enable unauthorized network access or bypass internal network controls. A high-severity finding in `motherduck/mcp_server/prompt.py` indicates potential for insecure process invocation or handling of untrusted data. These issues collectively point to risks involving network egress and potential shell execution.
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.