io.github.ofirbaranesad-agent/contract-powers · v1.1.0 · crypto-web3
Contract Powers is healthy: it completed an MCP handshake in 1913 ms and exposes 4 tools.
Who can still change this EVM contract, and what can they do to holders?
Endpoint: https://agent.zbang.net/api/mcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 4 |
| Latency | 1913 ms |
| Last checked (UTC) | 2026-10-15T06:15:43.971Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-15T06:15:43.971Z | Healthy | 1913 |
list_watched_contracts | List the EVM contracts in the Contract Powers registry, with a one-line risk shape for each: is the code upgradeable, is the admin a single key (EOA) rather than a contract, how many powers are declared, and is it covered by a bug bounty. Use this to see what is already analysed before spending a lo |
get_contract_powers | Full free analysis of one contract that is in the registry: verification, proxy pattern and implementation address, who the admin is and whether it is a single key, every retained power (upgrade / mint / grant-minter / pause / blacklist / seize / fees / sweep / burn-from / ownership transfer / limit |
check_any_contract | Free preview for ANY verified EVM contract on base, ethereum or polygon — including addresses not in the registry. Returns contract type, verification, name, whether it is a proxy, how many powers were found, how many owner-only functions went uncategorised, and whether an owner was found. The decis |
recent_power_changes | What actually changed behind the watched contracts: implementation swapped, owner moved, a power appeared or disappeared, verification lost. Each event carries the before and after value and the window it was detected in. Severity is one of critical / material / low. Use this to answer "has anything |