# OneKeyAway: who controls this contract (remote · onekeyaway.appin60.com)

Who can change an EVM contract or Safe: proxy admin, owner, Safe signers, timelock. Free alerts.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `onekeyaway.appin60.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/com-appin60-onekeyaway-control/onekeyaway.md), [page](https://verifymcp.io/servers/com-appin60-onekeyaway-control/onekeyaway)

## Channel facts

- Endpoint: `https://onekeyaway.appin60.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-10-17.

- **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 1 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**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 437 tokens (~218/item across 2 items; 2 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**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 60% 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the OneKeyAway: who controls this contract MCP server?

OneKeyAway: who controls this contract is a hosted endpoint at https://onekeyaway.appin60.com/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 com-appin60-onekeyaway-control 'https://onekeyaway.appin60.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-appin60-onekeyaway-control": {
      "url": "https://onekeyaway.appin60.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-appin60-onekeyaway-control": {
      "type": "http",
      "url": "https://onekeyaway.appin60.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-appin60-onekeyaway-control]
url = "https://onekeyaway.appin60.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-appin60-onekeyaway-control": {
      "type": "remote",
      "url": "https://onekeyaway.appin60.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-appin60-onekeyaway-control --url 'https://onekeyaway.appin60.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-appin60-onekeyaway-control:
    url: "https://onekeyaway.appin60.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-appin60-onekeyaway-control": {
      "Transport": "http",
      "Url": "https://onekeyaway.appin60.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-appin60-onekeyaway-control -t streamable-http -u 'https://onekeyaway.appin60.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-appin60-onekeyaway-control": {
      "type": "http",
      "url": "https://onekeyaway.appin60.com/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-10-16 (score 63, +1)

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

### 2026-10-14 (score 62, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-13 (score 61)

First indexed and scored.

## MCP tools (2)

### `control_map` (~251 tokens)

Who controls this contract

On-chain control path of an EVM contract or Safe: proxy type and implementation; proxy admin, beacon owner, owner(), DEFAULT_ADMIN_ROLE holders, Aave PoolAddressesProvider owner, Morpho vault curator/guardian/timelock; each resolved through ProxyAdmin, Safe threshold and signers, timelock delay or Avocado wallet; plus a verdict (SINGLE KEY, MULTISIG NO TIMELOCK, TIMELOCKED, UNRESOLVED). For a Safe address: signers, threshold, modules, guard, fallback handler, singleton. Chains: ethereum (1), optimism (10), bsc (56), unichain (130), polygon (137), sonic (146), zksync (324), hyperevm (999), base (8453), arbitrum (42161), avalanche (43114), linea (59144), berachain (80094), blast (81457), katana (747474). Free, 100 calls/day.

Input parameters:

- `address` (string, required): Contract or Safe address, 0x + 40 hex
- `chain` (string, required): Chain name or id, e.g. base, ethereum, arbitrum, 8453

### `watch_contract` (~110 tokens)

Email me if control of this contract changes

Free alerts (up to 3 contracts per email): sends a confirmation email, then an alert when the implementation, proxy admin, owner, DEFAULT_ADMIN_ROLE holders, Safe signers/threshold/modules/guard or Morpho vault timelock change. Checked about every 15 minutes. Only use with the user's own email address and their explicit consent.

Input parameters:

- `address` (string, required)
- `chain` (string, required)
- `email` (string, required): The user's own email address (they must confirm by link)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-appin60-onekeyaway-control/onekeyaway#diagnostics

## Score history

- 2026-10-17: 63
- 2026-10-16: 63
- 2026-10-15: 62
- 2026-10-14: 62
- 2026-10-13: 61

## Common questions

### What is the OneKeyAway: who controls this contract MCP server?

OneKeyAway: who controls this contract is an MCP server listed in the public MCP registry as com.appin60.onekeyaway/control. Who can change an EVM contract or Safe: proxy admin, owner, Safe signers, timelock. Free alerts. This page covers its hosted endpoint (https://onekeyaway.appin60.com/mcp).

### Is the OneKeyAway: who controls this contract MCP server safe to use?

OneKeyAway: who controls this contract scores 63 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 OneKeyAway: who controls this contract MCP server expose?

OneKeyAway: who controls this contract exposes 2 tools: control_map, watch_contract. Their descriptions and schemas cost roughly 361 tokens of context every time the server is loaded.

### Does the OneKeyAway: who controls this contract MCP server require authentication?

No. We connected to OneKeyAway: who controls this contract without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the OneKeyAway: who controls this contract MCP server still maintained?

OneKeyAway: who controls this contract is still listed as active in the MCP registry. We last reached this channel on 17 October 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://onekeyaway.appin60.com/mcp
- Website: https://onekeyaway.appin60.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-appin60-onekeyaway-control/onekeyaway.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-appin60-onekeyaway-control/onekeyaway.json
- HTML version of this page: https://verifymcp.io/servers/com-appin60-onekeyaway-control/onekeyaway