Contract Powers

Name: Contract Powers
Author: ofirbaranesad-agent

MCP serverMCP

Who can still change this EVM contract, and what can they do to holders?

by ofirbaranesad-agentrepository ↗homepage ↗v1.1.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"contract-powers","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability67/67 checks ok

when	check	result	http	latency	detail
5 h ago	mcp initialize	ok	200	17 ms	server contract-powers 1.1.0 · protocol 2025-06-18 · 4 tools
12 h ago	mcp initialize	ok	200	11 ms	server contract-powers 1.1.0 · protocol 2025-06-18 · 4 tools
20 h ago	mcp initialize	ok	200	13 ms	server contract-powers 1.1.0 · protocol 2025-06-18 · 4 tools
27 h ago	mcp initialize	ok	200	12 ms	server contract-powers 1.1.0 · protocol 2025-06-18 · 4 tools
33 h ago	mcp initialize	ok	200	13 ms	server contract-powers 1.1.0 · protocol 2025-06-18 · 4 tools
2 d ago	mcp initialize	ok	200	15 ms	server contract-powers 1.1.0 · protocol 2025-06-18 · 4 tools
2 d ago	mcp initialize	ok	200	11 ms	server contract-powers 1.1.0 · protocol 2025-06-18 · 4 tools
2 d ago	mcp initialize	ok	200	43 ms	server contract-powers 1.1.0 · protocol 2025-06-18 · 4 tools
2 d ago	mcp initialize	ok	200	17 ms	server contract-powers 1.1.0 · protocol 2025-06-18 · 4 tools
3 d ago	mcp initialize	ok	200	13 ms	server contract-powers 1.1.0 · protocol 2025-06-18 · 4 tools

Tools observed via MCP handshake

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 tha
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
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, wh
recent_power_changes — What actually changed behind the watched contracts: implementation swapped, owner moved, a power appeared or disappeared, verification lost. Each event carries

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.github.ofirbaranesad-agent/contract-powers

first seen 18 d ago · fetched 2 d agoopen ↗

Field history (7 recent events)

18 d ago · declared · summary → "Who can still change this EVM contract, and what can they do to holders?"
18 d ago · declared · description → "Who can still change this EVM contract, and what can they do to holders?"
18 d ago · declared · publisherName → "ofirbaranesad-agent"
18 d ago · declared · homepageUrl → "https://agent.zbang.net/c/"
18 d ago · declared · repoUrl → "https://github.com/ofirbaranesad-agent/contract-powers-mcp"
18 d ago · declared · version → "1.1.0"
18 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from