Find out who controls an EVM smart contract or protocol. Use when the user asks who owns, who controls, who can upgrade, who can mint or pause, or who holds the admin roles on an Ethereum, Base, Arbitrum, Optimism, Polygon, BSC or other EVM contract; whether an admin is an EOA or a multisig; whether a Safe is 1-of-N; whether privileged calls go through a timelock; to audit a protocol's admin surface or control graph; to produce a monitoring config for owner/role/upgrade changes; or to verify an ERC-8241 control disclosure against the chain. Read-only: no key, no wallet, nothing is ever sent on-chain.
cp -r cryptoskill/skills/mcp-servers/imal1ice-evm-contract-control-audit .claude/skills/clawhub install imal1ice-evm-contract-control-auditCapabilities below are detected automatically by an open-source scanner that reads the skill's text and scripts (see how this is computed). Not measured means the scanner couldn't make a confident call — it is NOT a green check, and you should treat it as a possible red flag until a human or a stronger scanner has measured it.
unknown
We did not find any well-known hosted services in this skill's text or scripts. This does NOT mean the skill is local-only — it might use services we don't yet recognize, or talk to them through code paths our scanner can't reach. A complete dependency list (every package, library, and binary, with integrity hashes) is on the roadmap; today we only show recognized hosts.
No one has audited this skill yet. That is different from “audited and clean” — it just means no professional reviewer (a security firm, the CryptoSkill team, or a verified independent researcher) has signed off on it. There are no audit reports to read. How reviewer levels work →
SKILL.md → SOURCE.md → TRUST.auto.yaml → Browse directory →
Auto-generated by cryptoskill/extract-capabilities/0.3.1 · hosted-service list version 2026-09-06 · how this is computed