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.
Available components
Last scanned (8 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Crypto and Web3
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 +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.
- 14 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 13 Oct 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://onekeyaway.appin60.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onekeyaway.appin60.com | CN=WE1,O=Google Trust Services,C=US | 12 Oct 2026 | 10 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | ebbb12ee7042acc1342a5f677abbdcc |
| SANs: onekeyaway.appin60.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of onekeyaway.appin60.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| appin60.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://onekeyaway.appin60.com/mcp | Verified | 200 | |
| http (plaintext) | http://onekeyaway.appin60.com/mcp | HTTPS enforced | 301 | https://onekeyaway.appin60.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
control_map Who controls this contract ~251
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Contract or Safe address, 0x + 40 hex |
| chain | string | yes | Chain name or id, e.g. base, ethereum, arbitrum, 8453 |
No output schema declared.
No examples provided.
watch_contract Email me if control of this contract changes ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| chain | string | yes | – |
| string | yes | The user's own email address (they must confirm by link) |
No output schema declared.
No examples provided.
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.
remote · onekeyaway.appin60.com
claude mcp add --transport http com-appin60-onekeyaway-control 'https://onekeyaway.appin60.com/mcp'
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.