How can I check what an MCP server or npm package can do with my keys before I install it?

Paste the package, MCP endpoint or install command into Sato Check (/check) or call onchain_agent_check_install; it reports key access, key egress and fund actions, as of 2026-10-28.

What does an MCP server do with my wallet key?

Of 88 MCP servers with a published Sato Check reading, 16 read private-key material in code (signing locally is what a wallet does), 14 ask for a key in setup and 58 show no key read found, as of 2026-10-28.

Should you give an MCP server your wallet private key?

Of 88 MCP servers with a published Sato Check reading, 30 take a key (16 read it, 14 ask in setup); 11 have a planted-key run with none seen leaving; 4 list an action that can sign or send funds, as of 2026-10-28.

What should I check before installing @raydium-io/raydium-sdk-v2?

Sato Hub's record for Raydium documents npm install @raydium-io/raydium-sdk-v2. The install was reproduced in a container. No security review was performed, as of 2026-10-28.

Answer

What should I check before installing @trustwallet/cli?

Sato Hub's record for Trust Wallet Agent Kit (TWAK) documents npm install @trustwallet/cli. The install was reproduced in a container. No security review was performed, as of 2026-10-28.

Answered from live data2026-10-28

Every reading Sato Hub holds for Trust Wallet Agent Kit (TWAK), with the field it came from. These are the same checks /preflight runs live against a package name — nothing here describes the package's behaviour once it runs.

Check	Reading	Where it comes from
Documented install	npm install @trustwallet/cli	the project's own deploy spec on its Sato Hub record
Install reproduced by Sato Hub	yes, 2026-10-26	container run of that install line
Latest commit or release	2026-06-11	the later of the last commit and last release
Liveness label	Quiet	derived from that commit or release date
Source availability	Partial	declared licence and repository
Sato Score	72 (High)	openness, activity, verifiability
Verification status	Verified	self-reported unless an earned check is named
What Sato Hub has NOT done	no security review, no dependency audit, no runtime analysis	stated so it is never inferred

How this was answeredShowHide

Every reading on the "trust-wallet-agent-kit" record — the documented install line, whether Sato Hub reproduced it in a container, activity, openness and score — laid out as the checks lib/preflight.ts runs live. It names what was NOT done as explicitly as what was.

Every answer on this page is produced by one named function over Sato Hub's live records on the date shown. Nothing is typed by hand, no figure is carried over from a previous day, and an answer with nothing behind it says unknown rather than zero. The Sato Score measures how open, active and verifiable a project is — it is not a safety, quality or returns grade.

Go deeper

Trust Wallet Agent Kit (TWAK) on Sato Hub →Trust Wallet Agent Kit (TWAK) Sato Score report →Run these checks on any package, repo or endpoint →

Cite this page

Sato Hub. "What should I check before installing @trustwallet/cli?." Sato Hub, updated 2026-10-28, accessed 2026-10-28. https://satohub.ai/answers/what-to-check-before-installing-trustwallet-cli

Data last refreshed 2026-10-28; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0 and the machine-readable copy is linked in the page's Dataset metadata.

What should I check before installing @trustwallet/cli?

Go deeper

More questions

Related questions, answered

Sources — the projects' own repositories and docs

Cite this page