Sato Check · MCP server

@veilnet/mcp-server

mcp:npm:@veilnet/mcp-server · v0.5.2 · sha256:c0e7eed3d00b · as of 2026-09-26

Does it take your key?: It asks for a private key or seed phrase in its setup.; Our static read of the published artifact found it.
Does your key leave?: Not yet run — we have not run this version with planted test keys.; No evidence line on file for this question yet.
Can it move funds on its own?: Unknown — we could not read what it exposes.; No evidence line on file for this question yet.
What changed?: First profile of this subject — nothing to compare yet.; No evidence line on file for this question yet.

Hosts contacted

Host	When	Role	Evidence
app.veilnet.to	code	vendor	traced
basescan.org	code	other	traced
mainnet.base.org	code	rpc	traced

Evidence (5 lines)

tracedT-hosts2026-09-26
app.veilnet.to appears in shipped code (vendor).
dist/keys.js
tracedT-hosts2026-09-26
basescan.org appears in shipped code (other).
dist/tools/x402PayerInfo.js
tracedT-hosts2026-09-26
mainnet.base.org appears in shipped code (rpc).
dist/x402Payer.js
tracedT-key-handling2026-09-26
Turns key material it is GIVEN into an account or signer (privateKeyToAccount()); no read of a key from the environment or a key file was found. A signing library does this.
dist/x402Payer.js:53
declaredD-env-key2026-09-26
Setup names session.json + master.key files at ~/.veilnet/ downloaded fr as something to provide.
deploy_spec.requires

The observed lane has not run on this version: not yet run on this version
Traced analysis follows flows inside one module only; a key handed from one module to another is not followed.
The observed lane has not run on this version.
No tool inventory was available, so fund actions were not read.

A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".

sato.custody/v1 · custody-1

Maintain this project? Respond to this reading

Loading sign-in…