INDIVIDUAL MCP TOOL

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.

zbang.netnone authenticationAvailability not checked

LIVE ENDPOINT

https://agent.zbang.net/api/mcp

No auth detected

Connect to this endpoint to inspect the live schema for list_watched_contracts and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

zbang.net

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.contract-powers]
url = "https://agent.zbang.net/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "contract-powers": {
      "type": "http",
      "url": "https://agent.zbang.net/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: contract-powers
Remote MCP URL: https://agent.zbang.net/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "contract-powers": {
      "url": "https://agent.zbang.net/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "contract-powers": {
      "type": "http",
      "url": "https://agent.zbang.net/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "contract-powers",
  "transport": "streamable-http",
  "url": "https://agent.zbang.net/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

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 / pause / blacklist / 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.
check_any_contract — Free preview for ANY verified EVM contract on base, ethereum or polygon — including addresses not in the registry.
recent_power_changes — What actually changed behind the watched contracts: implementation swapped, owner moved, a power appeared or disappeared, verification lost.