tx402
NPM · TX402-MCP
Explain Algorand transactions, groups, batches, and account activity with x402.
Available components
Last scanned (22 hours ago)
Scores higher than 41% of npm servers
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 39 of 119 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 92 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability51
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 204 tokens (~51/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 −1
- Stability: pass → 0.93 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/tx402-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 119 packages
| Packages resolved | 119 |
|---|---|
| Stale | 39 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
explain_algorand_atomic_group Explain Algorand atomic group ~42
Explain every outer and inner transaction in the atomic group containing a transaction ID.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | – |
| txid | string | yes | – |
No output schema declared.
No examples provided.
explain_algorand_transaction Explain Algorand transaction ~59
Explain one Algorand transaction in plain English using tx402. Returns payment requirements if the endpoint requires x402 payment and payments are not enabled in this MCP wrapper.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | – |
| txid | string | yes | – |
No output schema declared.
No examples provided.
explain_algorand_transaction_batch Explain Algorand transaction batch ~47
Explain 1 to 10 Algorand transaction IDs in one request, with per-item results.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | – |
| txids | array | yes | – |
No output schema declared.
No examples provided.
summarize_algorand_account_activity Summarize Algorand account activity ~56
Summarize recent asset flows, fees, counterparties, and verified protocol interactions for an Algorand account.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| limit | integer | – | – |
| network | string | – | – |
No output schema declared.
No examples provided.
How do I install the tx402 MCP server?
tx402 runs locally as an npm package, launched with npx -y tx402-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · tx402-mcp
claude mcp add mahesvannan-tx402 -- npx -y tx402-mcp
What is the tx402 MCP server?
tx402 is an MCP server listed in the public MCP registry as io.github.Mahesvannan/tx402. Explain Algorand transactions, groups, batches, and account activity with x402. This page covers its npm package (tx402-mcp).
Is the tx402 MCP server safe to use?
tx402 scores 71 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the tx402 MCP server expose?
tx402 exposes 4 tools: explain_algorand_transaction, explain_algorand_atomic_group, explain_algorand_transaction_batch, summarize_algorand_account_activity. Their descriptions and schemas cost roughly 204 tokens of context every time the server is loaded.
Is the tx402 MCP server still maintained?
tx402 is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the tx402 MCP server under?
tx402 declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.