# Contract Powers (remote · agent.zbang.net)

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

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `agent.zbang.net`: 65/100 (this document), [markdown](https://verifymcp.io/servers/ofirbaranesad-agent-contract-powers/api-mcp.md), [page](https://verifymcp.io/servers/ofirbaranesad-agent-contract-powers/api-mcp)

## Channel facts

- Endpoint: `https://agent.zbang.net/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 686 tokens (~171/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Contract Powers MCP server?

Contract Powers is a hosted endpoint at https://agent.zbang.net/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ofirbaranesad-agent-contract-powers 'https://agent.zbang.net/api/mcp'
```

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.ofirbaranesad-agent-contract-powers]
url = "https://agent.zbang.net/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ofirbaranesad-agent-contract-powers": {
      "type": "remote",
      "url": "https://agent.zbang.net/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ofirbaranesad-agent-contract-powers --url 'https://agent.zbang.net/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ofirbaranesad-agent-contract-powers:
    url: "https://agent.zbang.net/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ofirbaranesad-agent-contract-powers": {
      "Transport": "http",
      "Url": "https://agent.zbang.net/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ofirbaranesad-agent-contract-powers -t streamable-http -u 'https://agent.zbang.net/api/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 65, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 64, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-21 (score 64)

First indexed and scored.

## MCP tools (4)

### `list_watched_contracts` (~162 tokens)

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.

Input parameters:

- `chain` (string): Restrict to one chain.
- `limit` (integer): Default 200.
- `single_key_admin` (boolean): true = only contracts whose admin is a plain wallet (EOA), not a contract/multisig/timelock.
- `upgradeable` (boolean): true = only contracts whose code can still be replaced.

### `get_contract_powers` (~157 tokens)

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. Accepts an address or a symbol such as USDC or AERO.

Input parameters:

- `chain` (string): Required if a symbol is ambiguous.
- `contract` (string, required): A 0x address, or a symbol such as USDC.

### `check_any_contract` (~138 tokens)

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.

Input parameters:

- `address` (string, required): 0x-prefixed 20-byte address.
- `chain` (string): Default base.

### `recent_power_changes` (~106 tokens)

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?".

Input parameters:

- `contract` (string): Filter to one address or symbol.
- `limit` (integer): Default 25.
- `severity` (string): Minimum severity to return.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ofirbaranesad-agent-contract-powers/api-mcp#diagnostics

## Score history

- 2026-09-25: 65
- 2026-09-24: 65
- 2026-09-23: 65
- 2026-09-22: 64
- 2026-09-21: 64

## Common questions

### What is the Contract Powers MCP server?

Contract Powers is an MCP server listed in the public MCP registry as io.github.ofirbaranesad-agent/contract-powers. Who can still change this EVM contract, and what can they do to holders? This page covers its hosted endpoint (https://agent.zbang.net/api/mcp).

### Is the Contract Powers MCP server safe to use?

Contract Powers scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Contract Powers MCP server expose?

Contract Powers exposes 4 tools: list_watched_contracts, get_contract_powers, check_any_contract, recent_power_changes. Their descriptions and schemas cost roughly 563 tokens of context every time the server is loaded.

### Does the Contract Powers MCP server require authentication?

No. We connected to Contract Powers without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Contract Powers MCP server still maintained?

Contract Powers is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://agent.zbang.net/api/mcp
- Repository: https://github.com/ofirbaranesad-agent/contract-powers-mcp
- Website: https://agent.zbang.net/c/
- Changelog RSS feed: https://verifymcp.io/servers/ofirbaranesad-agent-contract-powers/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ofirbaranesad-agent-contract-powers/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ofirbaranesad-agent-contract-powers/api-mcp