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-22.
- Answered from live data2026-10-22
The four steps are Sato Check's own, the same as the FAQ on /check. The questions it answers are: Does it take your key? Does your key leave? Can it move funds on its own? What changed? 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".
| Step | What to do | Where |
|---|---|---|
| 1 | Paste the package name, MCP endpoint or install command into Sato Check, or call the onchain_agent_check_install tool. | Sato Check at /check, or the onchain_agent_check_install MCP tool |
| 2 | Read the four answers: does it take your key, does your key leave, can it move funds on its own, and what changed since the last version. | The four answers every check returns |
| 3 | Read the evidence type on each answer (declared, traced or observed), and the version and date it was read. | The evidence type printed beside each answer |
| 4 | Treat unknown as unknown. "Not observed" means no planted key left during install and start-up, under our test conditions — code paths that only run later, or only on a trigger, are not covered. | The limits printed beside each answer |
| Already read | 180 listings have a published Sato Check reading of one version, 87 of them MCP servers. A listing with no reading is unknown, not clear. A reading where a planted test key was seen leaving is not counted here (the maintainer is told privately first). | Each listing page, and /lists/what-mcp-servers-do-with-your-keys |
How this was answeredShowHide
The four steps are CHECK_YOURSELF_STEPS in lib/custody/wording.ts, the same text as the FAQ on /check. The count of listings with a published reading is publicCustodyReading() in lib/custodyListing.ts over every non-deprecated listing. The page answers while the keys list is published. The rule "what-mcp-servers-do-with-your-keys" in lib/listicles.ts (an MCP listing with a Sato Score and a published Sato Check reading), read through publicCustodyReading() in lib/custodyListing.ts: the reading already public on the listing's own page, of one concrete version, never one that recorded a planted key leaving. Counted per reading by keyReadingCounts(), keyReadingProvenance() and keyReadingFunds() in lib/listicles.ts, the same folds the list's own opening uses. Describes what was read and run, with dates; not a rating, an audit or an endorsement.
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
More questions
- What does an MCP server do with my wallet key?
- Should you give an MCP server your wallet private key?
- Which crypto MCP servers have had their installation independently verified?
- What should I check before installing @raydium-io/raydium-sdk-v2?
- What should I check before installing @blockrun/mcp?
- What should I check before installing @goat-sdk/core?
Reference
QuestionsWhat people ask about this pageShowHide
SourcesWhere the data comes fromShowHide
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "How can I check what an MCP server or npm package can do with my keys before I install it?." Sato Hub, updated 2026-10-22, accessed 2026-10-22. https://satohub.ai/answers/how-can-i-check-what-an-mcp-server-or-npm-package-can-do-with-my-keysData last refreshed 2026-10-22; 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.