Loading the registry…
X402 payment integration for Model Context Protocol (MCP)
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.
7 critical findings reported by cisco-skill-scanner, agent-audit-kit, 3 of them in the installed artifact. The composite score alone does not reflect this — read the per-scanner reports below.
This artifact ships from 2 sources and their verdicts differ. The worst is github (Flagged). Installing from a cleaner source does not mean the others are safe — check the source you actually install from.
github: https://github.com/civicteam/x402-mcp, 60 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- @civic/x402-mcp
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
6 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
8 findings · 7.4s
v0.3.74
18 findings · 1.8s
v0.1.0
0 findings · 3.2s
v0.1.0
0 findings · 3.2s
v0.1.0
0 findings · 7.7s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
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: complete | 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 26 findings across every scanner that examined this package. 4 of 7 findings rated critical by their scanner were among the dismissals.
Not reviewed is not the same as clean. Those 2 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.
5 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: AAK-MCP-HTTP-NOAUTH-SERVER-001, AAK-MCP-018, LOW_ANALYZABILITY and 2 more · Files: example/server.ts, /repo/example/proxy, /repo/example/proxy/SKILL.md · reported by agent-audit-kit, cisco-skill-scanner
4 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-DNS-REBIND-001, YARA_credential_harvesting_generic · Files: src/server.test.ts, src/client.test.ts, example/proxy/client.ts and 1 more · reported by agent-audit-kit, cisco-skill-scanner
3 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/ci.yml, .github/workflows/release.yml · reported by agent-audit-kit
2 Agent instruction file — The match is in a file that instructs an AI coding agent — a CLAUDE.md or similar. It is documentation of intent, and our own check confirmed it is not part of what gets installed.
Rules: AAK-AGENT-002 · Files: CLAUDE.md · reported by agent-audit-kit
The model could have called any of these a false positive and did not.
3 AAK-DNS-REBIND-001
Files: src/client.ts, src/server.ts, src/proxy/server.ts · reported by agent-audit-kit
2 AAK-DNS-REBIND-002
Files: package.json · reported by agent-audit-kit
1 AAK-LEGAL-002
Files: package.json · 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 FILE_MAGIC_MISMATCH
Files: /repo/src/scripts/analyzePayment.ts · reported by cisco-skill-scanner
1 LOW_ANALYZABILITY
1 The model did not answer for these findings.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION · Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: MANIFEST_MISSING_LICENSE · Files: /repo/SKILL.md · reported by cisco-skill-scanner
Critical DNS rebinding risks identified
The artifact contains critical DNS rebinding vulnerabilities in `src/client.ts`, `src/proxy/server.ts`, and `src/server.ts`, which could allow network egress to arbitrary hosts. High severity DNS rebinding risks are also present in `package.json`. These findings indicate the artifact may perform network operations that could be redirected to unintended destinations.
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.