Skip to main content
Glama

Server Details

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

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
ofirbaranesad-agent/contract-powers-mcp
GitHub Stars
0
Server Listing
contract-powers-mcp
ChatGPT
–
Claude
–

TDQS

A4.2/5.0

Scored across 4 tools

Disambiguation4/5

The tools are mostly distinct, but check_any_contract and get_contract_powers both provide contract power analysis with the difference being registry status. The descriptions clearly explain when to use each, so an agent can disambiguate, though the overlap might cause occasional misselection.

Naming Consistency4/5

Three tools follow a verb_noun pattern (check_any_contract, get_contract_powers, list_watched_contracts), while recent_power_changes deviates by starting with an adjective. This minor inconsistency is readable and does not reduce comprehension.

Tool Count5/5

With 4 tools, the count is well within the ideal 3-15 range and each tool serves a distinct purpose in the contract powers domain: preview, full analysis, registry overview, and change monitoring. The scope is appropriately sized.

Completeness4/5

The tool surface covers the core workflows: checking any contract, getting full analysis for registry contracts, listing watched contracts, and monitoring changes. A minor gap is the inability to get full analysis for non-registry contracts (only a preview is provided), but this is likely by design and not a blocking omission.

Available Tools

4 tools
check_any_contractAInspect

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 decision fields (which powers, the evidence, the admin address, the implementation) are withheld and listed by name. Use get_contract_powers first if the contract is already in the registry — that is free and complete.

Inputs: address (required), chain.

get_contract_powersAInspect

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 / limits) with the evidence and confidence behind it, reachable DELEGATECALL / SELFDESTRUCT / CREATE2 opcodes, and the owner-only functions the classifier could NOT categorise — which is where the unusual powers hide. Accepts an address or a symbol such as USDC or AERO.

Inputs: contract (required), chain.

list_watched_contractsAInspect

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 lookup. Filters are optional and combine with AND.

Inputs: chain, limit, upgradeable, single_key_admin.

recent_power_changesAInspect

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 changed behind this contract recently?".

Inputs: limit, contract, severity.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to query who controls any EVM contract by tracing owners, proxy upgrade admins, beacons, Safe signers/thresholds/modules, timelocks, and access roles, while flagging EOAs, 1-of-N Safes, and powers held without a timelock. All tools are read-only and return a chain view, not a verdict.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.