Loading the registry…
MCP server for VK Ads API (ads.vk.com, myTarget v2) — Bun/TypeScript port
The publisher performed an authenticated act of publication — proving control of a namespace in the official MCP registry, or appearing in a first-party catalogue an operator curates. That establishes WHO published it. It is not a security finding, and attested artifacts carry Flagged verdicts too.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- @ai-hub-open/vk-ads-mcp
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
7 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 · 4.0s
v2.0.11
7 findings · 31.0s
v0.3.26
12 findings · 6.7s
v0.1.0
0 findings · 41.7s
v0.1.0
0 findings · 41.7s
v0.1.0
0 findings · 33.6s
v2.3.8
0 findings · 19.2s
v0.71.0
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 1.1s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
No report in this scan: capslock, govulncheck.
2 scans on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Sep 11, 2026 | Pending scan | — | — | failed |
| Jul 30, 2026 | Flagged92 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completenerlo-multi-source: completetrivy ·n/a: not applicableosv-scanner: completetrivy_image ·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 19 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 1 finding 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.
6 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-003, AAK-SSRF-002, AAK-OAUTH-005 and 1 more · Files: tests/tools.test.ts, tests/http.test.ts, tests/client.test.ts · reported by agent-audit-kit
2 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/npm-publish.yml, .github/workflows/ci.yml · 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.
3 DATA_EXFIL_JS_NETWORK
Files: /repo/src/client.ts, /repo/src/transports/http.ts, /repo/src/urlGuard.ts · reported by cisco-skill-scanner
1 AAK-MCP-018
Files: src/transports/http.ts · reported by agent-audit-kit
1 AAK-SEC-MD-001
Files: SECURITY.md · reported by agent-audit-kit
1 AAK-SSRF-002
Files: src/transports/http.ts · reported by agent-audit-kit
1 AAK-SUPPLY-004
Files: package.json · reported by agent-audit-kit
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
1
1 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: HIDDEN_DATA_FILE · Files: /repo/.mcp.json.example · reported by cisco-skill-scanner
Artifact has a high-severity server-side request forgery vulnerability.
The artifact contains a high-severity server-side request forgery (SSRF) vulnerability in `src/transports/http.ts`. This allows the artifact to be coerced into making requests to arbitrary network locations, potentially exposing internal services or data. Additionally, there are medium-severity findings related to supply chain integrity and potential credential access, along with low-severity findings for hidden data files and security misconfigurations. Several informational findings indicate network egress capabilities in JavaScript.
Concern level assessed by the review: High. 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: /repo/SKILL.md · reported by cisco-skill-scanner
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · reported by cisco-skill-scanner