← Sato Check
Sato Check · MCP server
@usenami/funding-mcp
mcp:npm:@usenami/funding-mcp · v0.4.0 · sha256:5c45cdd00cc1 · as of 2026-09-29
- Does it take your key? traced
- Yes — it reads private-key material. Local signing is what a wallet does; question 2 says whether the key leaves.
- Our static read of the published artifact found it.
- Does your key leave? no evidence
- 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? no evidence
- Unknown — we could not read what it exposes.
- No evidence line on file for this question yet.
- What changed? no evidence
- First profile of this subject — nothing to compare yet.
- No evidence line on file for this question yet.
Is this your project? Respond →Dispute this reading
Hosts contacted
| Host | When | Role | Evidence |
|---|---|---|---|
| api.usenami.io | code | vendor | traced |
Evidence (5 lines)
- tracedT-key-read2026-09-29
Reads process.env.X402_PRIVATE_KEY.
dist/index.js:17
- tracedT-key-read2026-09-29
Reads privateKeyToAccount() on a value read from key material (PRIVATE_KEY).
dist/index.js:70
- tracedT-hosts2026-09-29
api.usenami.io appears in shipped code (vendor).
dist/index.js
- tracedT-key-named2026-09-29
The shipped code names X402_PRIVATE_KEY in a message to the user.
dist/index.js
- declaredD-env-key2026-09-29
Setup names X402_PRIVATE_KEY as something to provide.
deploy_spec.requires
Limits
- 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…