onchain_agent_check_install

shallow

ai.satohub/onchain-agents · Verify this server

USE WHEN you are about to install a crypto package, MCP server or skill and want to know what it can do with your keys and funds: before npm/pnpm/yarn/bun add, npx -y, pip install, uvx or `claude mcp add`, or before pasting an {"mcpServers": …} config. NOT FOR a token, repo, endpoint or agent you were handed (use onchain_agent_preflight instead), install steps for a stack pick (use onchain_agent_get_deploy_spec), or an agent skill's disclosure (use onchain_agent_search_skills). RETURNS a Sato Check custody summary for every target in the command or config you pass, answering four questions: does it take your key, does your key leave, can it move funds on its own, what changed. Each answer rests on evidence of one class — declared (the project says so), traced (our static read of the published artifact) or observed (a sandbox run with planted test keys). A stored profile answers first; an unstored target is read live within a bounded budget. Targets that could not be profiled are listed in `unresolved` with the reason. `has_observed_key_egress` is true only when a planted test key was seen leaving — the one fact to stop on. RULE ENFORCED: a profile describes what was read and run, with dates. It is not a safety rating, an audit or an endorsement; "unknown" means we could not look, and "none found" is not "not there". Local signing is what a wallet does. RETURNS (json): { schema: "sato.custody/v1", subjects: [{ subject, summary: { key_access, key_egress, fund_action_count, notable, version, as_of, check_url }, answers: { key_access, key_egress, fund_actions, changes }, solana_receipt }], unresolved: [{ input, reason }], has_observed_key_egress }. `solana_receipt` is where that version's reading is recorded on Solana ({ attestation_address, explorer_url, cluster, as_of, digest_hex }), or null when none is. install/cmd/package/text are read as `command`, mcp/mcpServers as `config` (labelled); `{}` checks nothing and answers needs_input. Read-only. Example: { command: "npm i viem @goat-sdk/core" } · { config: "{\"mcpServers\":{\"wallet\":{\"command\":\"npx\",\"args\":[\"-y\",\"some-wallet-mcp\"]}}}" }

100.0/100

1 trials · measured 2 days ago

onchain_agent_check_install scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against ai.satohub/onchain-agents, measured 20 Oct 2026 under methodology v0.2.0. Every measured component scored 100.

Component breakdown

ComponentWeightValue
Reliability35%not applicable
Schema integrity25%100.0
Failure behaviour15%not applicable
Latency15%not applicable
Concurrency10%not applicable

Tool details

Transport
remote + stdio
Credential class
self-provisionable
Input schema
not declared
Output schema
not declared
Side-effect classification
unclassified

Score history

DayScoreTierMethodology
2026-10-20100.0shallowv0.2.0

Probe evidence

ProbeOutcomes
schema_integritypass: 1

Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.

Embed this score

Available for every tool, scored or not — not a verification perk. Always links back to this page.

Vouch score: onchain_agent_check_install
[![Vouch score](https://vouch.tools/api/tools/704bc7c6-a1e3-4715-9c59-51b351aa0c53/badge.svg)](https://vouch.tools/tools/704bc7c6-a1e3-4715-9c59-51b351aa0c53)
onchain_agent_check_install — Vouch