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.
3 critical findings reported by agent-audit-kit, 2 of them in the installed artifact. 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 -- ascend-mcp
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.5s
v2.0.11
4 findings · 6.8s
v0.3.74
19 findings · 1.2s
v0.1.0
1 finding · 2.9s
v0.1.0
0 findings · 2.9s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.9s
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 21, 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 24 findings across every scanner that examined this package. 1 of 3 findings rated critical by their scanner was among the dismissals.
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.
4 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/docker-build.yml · reported by agent-audit-kit
2 Test or fixture file — The match is in a test or fixture. Our own check confirmed the file is not part of what gets installed.
Rules: AAK-TAINT-001, AAK-MCPFRAME-001 · Files: src/tests/integration/mcp-protocol.test.ts · 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.
2 AAK-MCP-ATTEST-001
Files: mcp_config.json, mcp_config_sse.json · reported by agent-audit-kit
1 AAK-ANTHROPIC-SDK-001
Files: src/index.ts · reported by agent-audit-kit
1 AAK-DNS-REBIND-001
Files: src/index.ts · reported by agent-audit-kit
1 AAK-MCP-001
Files: mcp_config_sse.json · reported by agent-audit-kit
1 AAK-MCP-003
Files: mcp_config.json · reported by agent-audit-kit
1 AAK-MCP-009
Files: mcp_config_sse.json · reported by agent-audit-kit
1
Critical DNS rebind and MCP configuration issues, with secret network egress.
The artifact contains critical DNS rebind vulnerabilities in `src/index.ts` and critical Multi-Cloud Platform (MCP) configuration issues in `mcp_config_sse.json`. High-severity findings include potential for secret data to egress over the network from `/repo/src/api-client.ts`. Additionally, an unauthenticated HTTP server is present in `src/index.ts`, alongside further high-severity MCP configuration issues in `mcp_config.json` and `mcp_config_sse.json`.
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.
Files: src/index.ts · reported by agent-audit-kit
1 AAK-MCP-STATELESS-001
Files: src/index.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-SECRET-007
Files: mcp_config.json · reported by agent-audit-kit
1 AAK-TRANSPORT-003
Files: mcp_config_sse.json · reported by agent-audit-kit
1 DATA_EXFIL_JS_NETWORK
Files: /repo/src/api-client.ts · reported by cisco-skill-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 opt.nerlo-rules.nerlo-js-secret-to-network-egress
Files: /repo/src/api-client.ts · reported by nerlo-behavioral
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · reported by cisco-skill-scanner