Skip to content

Contract Powers MCP server

io.github.ofirbaranesad-agent/contract-powersofirbaranesad-agentstreamable-httpv1.1.0Scanned

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

4 tools: 2 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Contract Powers MCP server can do

The Contract Powers MCP server is published by the GitHub account ofirbaranesad-agent. It has 4 tools. It can create or change data (2 tools: check_any_contract and recent_power_changes), but cannot delete data. 2 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 1.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 2Claude Code: ask
  • check_any_contractFree preview for ANY verified EVM contract on base, ethereum or polygon — including addresses not in the registry.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • recent_power_changesWhat actually changed behind the watched contracts: implementation swapped, owner moved, a power appeared or disappeared, verification lost.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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?".
Only reads 2Show 2 read-only tools
  • get_contract_powersFull 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 …No findings

    Why it is in this group

    • The name "get_contract_powers" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • list_watched_contractsList 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 ma…No findings

    Why it is in this group

    • The name "list_watched_contracts" says "list": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:09 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://agent.zbang.net/api/mcp: tools/list returned 4 tools to an anonymous client, including check_any_contract (write), recent_power_changes (write)

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • HTTP status of an anonymous initialize: 526 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 2
    • Protocol version: none to 2025-06-18
  2. Nov 13, 2026
    • HTTP status of an anonymous initialize: 200 to 526
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 526 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 2 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 526 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 2
    • Protocol version: none to 2025-06-18
  2. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 526; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 2 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 526
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__contract-powers__list_watched_contracts",
      "mcp__contract-powers__get_contract_powers"
    ],
    "ask": [
      "mcp__contract-powers__check_any_contract",
      "mcp__contract-powers__recent_power_changes"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as contract-powers. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.ofirbaranesad-agent/contract-powers/verify?hash=be864fdc0fdb611999ad2a89556bae9f850bdbd654eb64b21a794ae4eaba299f" | jq -e '.changed == false'

Pinned hash be864fdc0fdb, from Nov 20, 2026, 06:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.ofirbaranesad-agent/contract-powers/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.ofirbaranesad-agent/contract-powers
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.ofirbaranesad-agent/contract-powers.svg)](https://radar.anlyon.com/servers/io.github.ofirbaranesad-agent/contract-powers)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:42 UTC.

Contract Powers MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Contract Powers MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Contract Powers MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Contract Powers MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Contract Powers MCP server have?

4 tools: 2 write, 2 read. check_any_contract, recent_power_changes, list_watched_contracts and get_contract_powers.

Does the Contract Powers MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Contract Powers MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Contract Powers MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.