Loading the registry…
Plain-English explanations of Algorand transactions, as a pay-per-call 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.
149 critical findings reported by agent-audit-kit, 0 of them in the installed artifact. The composite score alone does not reflect this — read the per-scanner reports below.
github: https://github.com/Mahesvannan/tx402, 236 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- tx402
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
4 findings · 1.0s
v2.0.11
23 findings · 7.3s
v0.3.26
161 findings · 1.2s
v0.1.0
7 findings · 27.3s
v0.1.0
0 findings · 27.3s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 11.9s
No report in this scan: capslock, 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 4, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completenerlo-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 195 findings across every scanner that examined this package. 149 of 149 findings rated critical by their scanner were 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.
156 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-001, AAK-AGENT-002 · Files: CLAUDE.md · reported by agent-audit-kit
3 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: opt.nerlo-rules.nerlo-js-secret-to-network-egress, SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: /repo/examples/node-client.mjs, /repo/docs/SKILL.md · reported by nerlo-behavioral, cisco-skill-scanner
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.
8 DATA_EXFIL_JS_NETWORK
Files: /repo/scripts/check-phase4-mainnet.mjs, /repo/scripts/check-phase5-buyer.mjs, /repo/scripts/smoke-phase3.mjs and 2 more · reported by cisco-skill-scanner
6 opt.nerlo-rules.nerlo-js-secret-to-network-egress
Files: /repo/scripts/check-phase4-mainnet.mjs, /repo/scripts/check-phase5-buyer.mjs, /repo/scripts/smoke-phase3.mjs and 2 more · reported by nerlo-behavioral
4 DATA_EXFIL_JS_FS_ACCESS
Files: /repo/packages/tx402-mcp/bin/tx402-mcp.mjs, /repo/scripts/check-phase5-buyer.mjs, /repo/scripts/pay-and-explain.mjs · reported by cisco-skill-scanner
3 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/submission/SKILL.md, /repo/packages/tx402-mcp/SKILL.md · reported by cisco-skill-scanner
3 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/submission/SKILL.md, /repo/packages/tx402-mcp/SKILL.md · reported by cisco-skill-scanner
Potential credential exposure via network egress
The artifact may expose credentials through network egress, specifically in `packages/tx402-mcp/bin/tx402-mcp.mjs` and several scripts under `/repo/scripts/`. Additionally, secrets could be sent over the network from `src/index.js` and `src/payments.js`. The artifact also has broad permissions and lacks pre-tool use hooks, which warrants attention.
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.
2 AAK-MCP-OPENAPI-LAZY-DESCRIPTION-001
Files: openapi.json · reported by agent-audit-kit
2 hooks-no-pretooluse
Files: settings.json, .claude/settings.json · reported by agentshield
2 LOW_ANALYZABILITY
Files: /repo/packages/tx402-mcp, /repo · reported by cisco-skill-scanner
2 permissions-no-block
Files: settings.json, .claude/settings.json · reported by agentshield
1 AAK-ANTHROPIC-SDK-001
Files: packages/tx402-mcp/bin/tx402-mcp.mjs · reported by agent-audit-kit
1 AAK-MCP-018
Files: packages/tx402-mcp/bin/tx402-mcp.mjs · reported by agent-audit-kit
1 AAK-OAUTH-3P-001
Files: package.json · reported by agent-audit-kit
1 FILE_MAGIC_MISMATCH
Files: /repo/src/payments.js · reported by cisco-skill-scanner