Loading the registry…
Free MCP server: index a repo's files (free) into the live x402-codesearch Worker so it can be semantically searched. Open funnel twin of the paid x402-gated codesearch HTTP API.
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.
npm: x402-codesearch-mcp @ 0.1.0, 0 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- x402-codesearch-mcp
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
8 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
5 findings · 6.7s
v0.3.26
5 findings · 0.6s
v0.1.0
1 finding · 26.9s
v0.1.0
0 findings · 26.9s
v0.1.0
0 findings · 18.3s
v0.71.0
0 findings · 0.2s
v2.3.8
0 findings · 6.8s
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.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 3, 2026 | Flagged96 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completenerlo-multi-source: completetrivy: completeosv-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 11 findings across every scanner that examined this package.
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-ANTHROPIC-SDK-001
Files: mcp-client-test.mjs, src/index.ts · reported by agent-audit-kit
1 AAK-MCP-018
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 DATA_EXFIL_JS_NETWORK
Files: /repo/src/client.ts · reported by cisco-skill-scanner
1 FILE_MAGIC_MISMATCH
Files: /repo/llms.txt · 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-hardcoded-external-egress
Files: /repo/src/client.ts · reported by nerlo-behavioral
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · reported by cisco-skill-scanner
High-severity findings related to AI SDK usage and potential credential exposure.
The artifact uses an Anthropic SDK, with two high-severity findings indicating potential issues in `mcp-client-test.mjs` and `src/index.ts`. There is also a medium-severity finding for third-party OAuth usage, which could involve credential access. Additionally, a medium-severity finding indicates a file magic mismatch, suggesting a file type discrepancy.
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.