- How can I check what an MCP server or npm package can do with my keys before I install it?
- 1. Paste the package name, MCP endpoint or install command into Sato Check, or call the onchain_agent_check_install 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. 3. Read the evidence type on each answer (declared, traced or observed), and the version and date it was read. 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.
- What does Sato Check show?
- Sato Check reads what an agent's code can do with its keys and money — before it is installed, and every time it changes.
- What do declared, traced and observed mean?
- Declared: The project says so — README, config, env list or tool description. Traced: Our static read of the published artifact found it. Observed: We ran it with planted test keys and saw it.
- What does unknown mean in a check?
- Unknown means we could not look, not that something is wrong.
- Is a check a rating or an audit?
- 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".
- How many MCP servers have a published Sato Check reading?
- 87 MCP servers in the directory have a published Sato Check reading, each of one version. The newest reading is dated 2026-11-11. Each row of https://satohub.ai/lists/what-mcp-servers-do-with-your-keys shows the version read, the date and whether a person reviewed it. A server with no reading is unknown, not clear.
- Is there a fuller read of one project before I connect or pay?
- Preflight, at https://satohub.ai/preflight, lays out every evidence line on a project with its date and its own gaps. It describes what is on record and is not a verdict.