Skills/npm/x402-mcp

x402-mcp@1.8.1

VERIFIED

Publisher claims: "Search 48 live data feeds and settle HTTP 402 unlocks in ~350ms via feeless Nano (XNO)." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server) · listed in the official MCP RegistryPublisher withsilex · publishing for 4 daysInstalls 0Last detonated 3d ago
$claude mcp add x402-mcp -- npx -y @withsilex/x402-mcp
WatchReport an issue

Coverage

Server started and answered tools/list.
Tested
MCP initialize and tools/list · every tool description, for hidden instructions · every file read, file written and host contacted by what ran
Not tested
what the tools do when called with real credentials

Before you give it your token

It will ask for
NANO_PRIVATE_KEYConfiguration, not credentials: SILEX_BASE_URL, SILEX_MAX_AUTO_USD
Where it talks to
withsilex.com (its own)Also nano.to, rainstorm.city, nanswap.com — not the publisher's domain; check what for before connecting.
What we saw when it ran
no credential files read · no network
What we could not test
what the tools do when called with real credentials

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names nano.to, rainstorm.city, nanswap.com as well as its own vendor. The guard injects NANO_PRIVATE_KEY only into requests to withsilex.com (and its subdomains) and refuses the rest.

$vet-skills run --secrets NANO_PRIVATE_KEY=withsilex.com -- npx -y @withsilex/x402-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-11-19 and scored it 90/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 25 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
4.7sprocessdependency install exit 0
25sclaimed6 tools: silex_hyper_search, silex_suggest_entities, silex_live_pulse, silex_inspect_402_challenge, silex_unlock_with_tx_hash, silex_auto_pay_and_unlock
25stools1ce3a71027bd6606
25stools98278f76efebad66
25stools4b8e0736f6e253ec
25stoolsb32e271cdaf9ea65
25stools36d56170f696642a
25stools404ea73031186cbd
25sprocessscript backend runs setup only
25sprocessno install scripts to re-run

Static findings

No findings across 348 lines in 9 files.

Cost to the agent

Instructions loaded
≈75 tok
1 file · 9 in bundle
Tool list per prompt
≈774 tok
6 tools · 129 per tool
Handshake
354 ms
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 177

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for @withsilex/x402-mcp@1.8.1 as of 3d ago. This is the package itself, not its dependencies.

x402-mcp@1.8.1 safety verdict: Verified — KillerSkills