Power your agent
The publisher's own command. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
npx -y [email protected]Claude Code has no install link for a local command. Copy the command below and run it in a terminal.
claude mcp add io.github.mahesvannan-tx402 -- npx -y tx402-mcp@0.2.0Run in a terminal.
{ "mcpServers": { "io.github.mahesvannan-tx402": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher
Plain-English explanations of Algorand transactions, sold as a pay-per-call API with x402 on Algorand.
Live service:
https://tx402-production.up.railway.app
Explain one transaction, every leg of an atomic group, a batch of IDs, or recent account activity. Responses include scaled amounts, inner transactions, asset names, fees, timestamps, counterparties, and source-verified protocol labels.
Explain Algorand transactions, groups, batches, and account activity with x402.
Try the free fixed-transaction demo without a wallet:
https://tx402-production.up.railway.app/demo?example=algo
GET /explain?txid=YRSG7IKDPCK4XMKFFTFFFYMIHF6SJOMHUOIE4FFUWNLEQ4WG2ZOQ
Example response after payment:
{
"txid": "YRSG7IKDPCK4XMKFFTFFFYMIHF6SJOMHUOIE4FFUWNLEQ4WG2ZOQ",
"network": "mainnet",
"summary": "On June 16, 2019, wallet VCINCV...JPMIPM sent 1 ALGO to CRBMB5...QLXZOY. Paid 0.001 ALGO in fees.",
"details": {
"type": "pay",
"sender": "VCINCVUX2DBKQ6WP63NOGPEAQAYGHGSGQX7TSH4M5LI5NBPVAGIHJPMIPM",
"transfer": {
"amount": "1",
"assetId": 0,
"unit": "ALGO"
}
}
}
Raw Algorand indexer JSON is optimized for machines doing bookkeeping: amounts are base units, assets are numeric IDs, and notes are base64. tx402 is the translation layer for agents and applications that need to explain a transaction to a person.
Public routes:
GET / - landing page with service metadata linksGET /health - process livenessGET /health?deep=1&network=mainnet - readiness check for upstream servicesGET /discovery - machine-readable service description and pricing metadataGET /openapi.json - OpenAPI 3.1 specificationGET /.well-known/agent.json - agent marketplace manifestGET /.well-known/x402 - x402 resource manifestGET /llms.txt - agent-readable documentationGET /demo?example=algo|usdc - free allowlisted Mainnet examplesGET /explain?txid=...&network=mainnet - paid transaction explanationGET /group?txid=...&network=mainnet - paid atomic-group explanationPOST /batch - paid batch of 1 to 10 transaction IDsGET /account/activity?address=...&limit=25 - paid activity summaryGET /analytics - free aggregate adoption countersDefault prices are $0.005 for /explain, $0.01 for /group, $0.02 for
/batch, and $0.01 for /account/activity. Production accepts Mainnet USDC:
algorand:wGHE2Pwdvd7S12BL5FaOP20EGYesN73ktiC1qzkkit8=315667046RK3U3OF2B4Q773L4KC7OVFHQGU5I74NHRZ36QN6CVF527CKXAL62YR754tx402 has a small deterministic core and a thin serving shell.
Core:
Serving shell:
The server never stores private keys. Buyer signing happens client-side. The resource server only advertises a price, validates payment, and settles through the facilitator after a successful product-route response.
npm install
npm start
npm test
Local endpoints:
curl "http://localhost:4021/health"
curl "http://localhost:4021/discovery"
curl "http://localhost:4021/explain?txid=SOME_REAL_MAINNET_TXID"
curl "http://localhost:4021/group?txid=SOME_REAL_MAINNET_TXID"
The app reads .env when present. Leave USDC_ASSET_ID unset unless you need a
non-standard asset; the code derives the canonical USDC asset from NETWORK.
Read-only example client:
npm run example:client
npm run example:catalog
The default client prints discovery metadata and the x402 payment challenge
without spending funds. To make it pay, configure a funded buyer wallet and set
TX402_EXAMPLE_PAY=1 plus CONFIRM_MAINNET_PAYMENT=1.
OpenAPI:
https://tx402-production.up.railway.app/openapi.jsonAgent marketplace metadata:
https://tx402-production.up.railway.app/.well-known/agent.jsonhttps://tx402-production.up.railway.app/.well-known/x402https://tx402-production.up.railway.app/llms.txtCopy-paste integrations and distribution assets:
The paid route also declares the standard x402 Bazaar extension, including its input/output schemas, service metadata, and example request. Facilitators can index that metadata after a successful settlement.
MCP wrapper:
npm run mcp
After the public npm package is published, agents can install it without cloning this repository:
npx tx402-mcp
By default the MCP wrapper is read-only and returns x402 payment requirements
for paid calls. To let it pay from a local wallet, set
TX402_MCP_ENABLE_PAYMENTS=1 and CONFIRM_MAINNET_PAYMENT=1.
The six-part adoption roadmap is tracked in PLAN.md.
txid input is rejected before indexer access and before payment./analytics, /discovery, and deep health checks are rate-limited.verified: true.First Mainnet settlement:
XA7HMRPUV4X2GWI4AAGUT5FKAVTNCQJ5ZMUNTVTBKG3GZMES27LA0.005000 USDCImplementation runbooks, deployment commands, phase evidence, and operational cautions live in CLAUDE.md.
© 2026 MCP Directory.
Explain Algorand transactions, groups, batches, and account activity with x402.
{ "mcpServers": { "io.github.mahesvannan-tx402": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
Tx402 runs locally over stdio.
Last checked 2026-11-09. Explain Algorand transactions, groups, batches, and account activity with x402.