X402 (easynodexyz) MCP Server

@easynodexyz/mcp-x402 npm v0.1.3 Source verified

Published by easynodexyz — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

MCP server for AI agents to purchase VPS/Node products via Easy Node's x402 API with USDC on Base

View on npm ↗ Repository ↗ Raw report (JSON) ↗

Trust grade

100/100

Last scanned 2026-09-07 get badge →

Trust

A · 100/100

Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.

Capability

Minimal

Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.

Coverage

Source

How much the scan could actually inspect. Shallow coverage is stated, never hidden.

A Why this grade threat 100 − adoption risk = 100/100

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 − 0 = 100. 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:

✓ No adoption-risk deductions — minimal blast radius, verified enough, and fully inspected.

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

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 7

Each tool and what it can reach — statically extracted from the published source.

create_orderno sensitive capability
get_instanceno sensitive capability
get_orderno sensitive capability
list_instancesno sensitive capability
list_productsno sensitive capability
renew_instanceno sensitive capability
update_custom_nameno sensitive capability

What this scan could not see

Tools were statically extracted from the published source (7 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.1.3` latest	A 100/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.

Markdown (GitHub README)

[![MCP Trust Score](https://mcptrustchecker.com/registry/easynodexyz-mcp-x402/badge.svg)](https://mcptrustchecker.com/registry/easynodexyz-mcp-x402)

HTML

<a href="https://mcptrustchecker.com/registry/easynodexyz-mcp-x402"><img src="https://mcptrustchecker.com/registry/easynodexyz-mcp-x402/badge.svg" alt="MCP Trust Score" height="20"></a>

Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/easynodexyz-mcp-x402/badge.json via https://img.shields.io/endpoint?url=…

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 @easynodexyz/mcp-x402 --online

Use the free API → How scoring works

Other implementations of X402 16

Independent packages implementing the same tool, scanned with the same engine. Compare all 17 side by side →

X402 Source verified npm

@x402/mcp

x402 Payment Protocol

Finance & Commerce Score 100/100 0 findings 4.6k/wk Cap. Minimal

X402 (scriptmasterlabs) Source verified npm

@scriptmasterlabs/mcp-x402

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

Finance & Commerce Score 100/100 0 findings 35/wk Cap. Minimal

X402 (ethanniser) npm

x402-mcp

[Learn more](https://vercel.com/blog/introducing-x402-mcp-open-protocol-payments-for-mcp-tools)

Other Score 99/100 0 findings 428/wk Cap. Minimal

X402 (bankofai) npm

@bankofai/x402-mcp

x402 Payment Protocol

Finance & Commerce Score 99/100 0 findings 233/wk Cap. Minimal

X402 (gadgethumans) npm

@gadgethumans/x402

x402 payment protocol — pay-per-call for AI agents via USDC on Base. No signup, no API keys.

Business & CRM Score 99/100 0 findings 160/wk Cap. Minimal

X402 (carbon-cashmere) npm

@carbon-cashmere/x402-mcp

MCP server that exposes Carbon & Cashmere's 177 crypto market intelligence endpoints with automatic x402 micropayments. Buy crypto signals, on-chain data, and trading intelligence directly from your AI agent's wallet.

Finance & Commerce Score 99/100 0 findings 80/wk Cap. Minimal