X402 (algo-wallet) MCP Server
@algo-wallet/x402-mcp
npm
v0.4.0
Published by @algo-wallet — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
x402 Algorand payment SDK — buyer MCP server, aggregator MCP (The Bazaar), seller middleware
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 2 = 98. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 0
Tools 4
Each tool and what it can reach — statically extracted from the published source.
check_balanceno sensitive capabilitycheck_mandatesno sensitive capabilityget_weatherno sensitive capabilitypay_with_x402no sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (4 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.4.0 latest |
A 98/100 | 0 | 1.13.0 | 2026-09-07 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @algo-wallet/x402-mcp --onlineOther implementations of X402 16
Independent packages implementing the same tool, scanned with the same engine. Compare all 17 side by side →
x402 Payment Protocol
MCP server for agents with autonomous USDC/RLUSD payments. x402 pay-per-call · 43+ trading + federal tools · no API keys. Free sml_discover demo. Remote: https://mcp-x402.onrender.com/mcp
MCP server for AI agents to purchase VPS/Node products via Easy Node's x402 API with USDC on Base
[Learn more](https://vercel.com/blog/introducing-x402-mcp-open-protocol-payments-for-mcp-tools)
x402 Payment Protocol
x402 payment protocol — pay-per-call for AI agents via USDC on Base. No signup, no API keys.
More in API Development
Adapters for the FrontMCP framework
Transcend MCP Server — Admin tools.
Transcend MCP Server — Assessments tools.
MCP Server for Bling
MCP Server for Blogger API
Official MCP server for Brilliant Directories — manage members, posts, leads, reviews, and more.