# ContractLens (remote · contractlens-api.appin60.com)

EVM token risk checks, x402 payability check for sellers, address classifier and live gas.

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

## Components

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

## Channel facts

- Endpoint: `https://contractlens-api.appin60.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.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**: 46/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 5 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - 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**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 584 tokens (~116/item across 5 items; 5 tools + 0 resources), lean.
  - 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 5 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the ContractLens MCP server?

ContractLens is a hosted endpoint at https://contractlens-api.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-contractlens-api-contractlens 'https://contractlens-api.appin60.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-appin60-contractlens-api-contractlens": {
      "url": "https://contractlens-api.appin60.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-appin60-contractlens-api-contractlens:
    url: "https://contractlens-api.appin60.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-appin60-contractlens-api-contractlens": {
      "type": "http",
      "url": "https://contractlens-api.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-15 (score 62, +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-10-14 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

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

First indexed and scored.

## MCP tools (5)

### `scan_contract` (~155 tokens)

Security scan of a verified EVM smart contract: who controls it now (owner / proxy admin: renounced, single-key EOA or Safe multisig), every owner/role-gated function (mint, pause, blacklist, upgrade, fees), proxy status, and Slither static-analysis findings ranked by impact. Use before approving, depositing into or buying a token. Chains: 1 Ethereum, 8453 Base, 42161 Arbitrum, 10 Optimism, 137 Polygon, 56 BNB.

Input parameters:

- `address` (string, required): 0x contract address (must be verified on Sourcify)
- `chainId` (string, required): EVM chain id, e.g. 8453 for Base

### `check_token` (~152 tokens)

Fast (1-3 s) risk verdict for an ERC-20 token before buying it: LOW/MEDIUM/HIGH with reasons. Who controls it (renounced, single key, Safe multisig, timelock), upgradeable proxy, admin powers in the bytecode (mint, blacklist, pause, adjustable tax, trading switch), source verification, DEX liquidity and pair age. Chains: 1 Ethereum, 8453 Base, 42161 Arbitrum, 10 Optimism, 137 Polygon, 56 BNB.

Input parameters:

- `address` (string, required): 0x token address
- `chainId` (string, required): EVM chain id, e.g. 8453 for Base

### `gas_now` (~84 tokens)

Live EIP-1559 gas for a chain: base fee, slow/standard/fast tips, maxFeePerGas values and the cost of common actions. Chains: 1, 8453, 42161, 10, 137, 56.

Input parameters:

- `chainId` (string, required): EVM chain id, e.g. 8453 for Base

### `address_info` (~83 tokens)

What is this address? EOA, EIP-7702 delegated EOA, Safe multisig (threshold, owners), timelock, ERC-20 token, proxy or contract, with native balance. Use before sending funds to or trusting an address.

Input parameters:

- `address` (string, required): 0x address
- `chainId` (string, required): EVM chain id

### `check_x402_payability` (~110 tokens)

For x402 sellers: can a real buyer actually pay this endpoint? Sends one payment signed by a fresh unfunded key through the endpoint's server and facilitator. Payable endpoints fail only on balance; anything else is reported with the exact reason (schema, description over 500 chars, EIP-712 domain, price over the $1 default client cap, paywall not enforcing).

Input parameters:

- `url` (string, required): Full https URL of the x402 endpoint, with any query params it needs

## Diagnostics

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

## Score history

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

## Common questions

### What is the ContractLens MCP server?

ContractLens is an MCP server listed in the public MCP registry as com.appin60.contractlens-api/contractlens. EVM token risk checks, x402 payability check for sellers, address classifier and live gas. This page covers its hosted endpoint (https://contractlens-api.appin60.com/mcp).

### Is the ContractLens MCP server safe to use?

ContractLens scores 62 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 ContractLens MCP server expose?

ContractLens exposes 5 tools: scan_contract, check_token, gas_now, address_info, check_x402_payability. Their descriptions and schemas cost roughly 584 tokens of context every time the server is loaded.

### Does the ContractLens MCP server require authentication?

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

### Is the ContractLens MCP server still maintained?

ContractLens 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://contractlens-api.appin60.com/mcp
- Website: https://contractlens.appin60.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-appin60-contractlens-api-contractlens/contractlens-api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-appin60-contractlens-api-contractlens/contractlens-api.json
- HTML version of this page: https://verifymcp.io/servers/com-appin60-contractlens-api-contractlens/contractlens-api