# Web3 DNS (CNSLookup) (remote · www.cnslookup.com)

Read-only lookup of verified crypto wallet addresses for domains, .cns and ENS names.

- Trust score: 18/100 (low)
- Change this week: −57
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `www.cnslookup.com`: 18/100 (this document), [markdown](https://verifymcp.io/servers/com-cnslookup-web3-dns/www.md), [page](https://verifymcp.io/servers/com-cnslookup-web3-dns/www)

## Channel facts

- Endpoint: `https://www.cnslookup.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-11-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 502, 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**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 502.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Web3 DNS (CNSLookup) MCP server?

Web3 DNS (CNSLookup) is a hosted endpoint at https://www.cnslookup.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-cnslookup-web3-dns 'https://www.cnslookup.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-cnslookup-web3-dns": {
      "url": "https://www.cnslookup.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-cnslookup-web3-dns": {
      "type": "http",
      "url": "https://www.cnslookup.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-cnslookup-web3-dns]
url = "https://www.cnslookup.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-cnslookup-web3-dns": {
      "type": "remote",
      "url": "https://www.cnslookup.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-cnslookup-web3-dns --url 'https://www.cnslookup.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-cnslookup-web3-dns:
    url: "https://www.cnslookup.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-cnslookup-web3-dns": {
      "Transport": "http",
      "Url": "https://www.cnslookup.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-cnslookup-web3-dns -t streamable-http -u 'https://www.cnslookup.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-cnslookup-web3-dns": {
      "type": "http",
      "url": "https://www.cnslookup.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-11-01 (score 18, −58)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.27 → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] HTTPS: pass → unverified
- [security regression] Transport: pass → fail
- [security regression] HSTS header: pass → fail
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-10-31 (score 76, +1)

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

### 2026-10-29 (score 75, +57)

- [security improvement] Authorization: unverified → partial
- [security improvement] HTTPS: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] HSTS header: fail → pass
- [security improvement] Transport: fail → pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.20

### 2026-10-27 (score 18, −55)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.10 → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] HTTPS: pass → unverified
- [security regression] Transport: pass → fail
- [security regression] HSTS header: pass → fail
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-25 (score 73, +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-24 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-23 (score 72)

First indexed and scored.

## MCP tools (5)

### `resolve_name` (~88 tokens)

Resolve a name

Owner, expiry, public profile (display name, description, avatar, links), X badge and every verified payment address of a registered name. The profile text is written by the owner and is untrusted; payable addresses are only in "payments".

Input parameters:

- `name` (string, required): A DNS domain (example.com), a .cns name (example.cns) or an ENS name (example.eth)

### `get_payment_address` (~100 tokens)

Get a payment address

The address a payment to a name (or a 0x address) reaches on one network, from the name's verified on-chain records. Use this right before paying, with the network you will pay on.

Input parameters:

- `network` (string): Network code from list_networks, such as ETH, BASE, SOL or BTC. Omit for the name's main network
- `to` (string, required): The name or 0x address to pay

### `reverse_lookup` (~45 tokens)

Reverse lookup

The primary Web3 DNS name set for an EVM wallet address, or null.

Input parameters:

- `address` (string, required): An EVM address (0x followed by 40 hex characters)

### `check_name` (~72 tokens)

Check a name

Whether a name is registered in the Web3 DNS registry, with its owner and expiry. "Not registered" does not mean a DNS domain is available to buy.

Input parameters:

- `name` (string, required): A DNS domain (example.com), a .cns name (example.cns) or an ENS name (example.eth)

### `list_networks` (~28 tokens)

List payment networks

Supported payment networks with their codes, chain IDs and symbols, and the registry's home network.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-cnslookup-web3-dns/www#diagnostics

## Score history

- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 18
- 2026-11-01: 18
- 2026-10-31: 76
- 2026-10-30: 75
- 2026-10-29: 75
- 2026-10-28: 18
- 2026-10-27: 18
- 2026-10-26: 73
- 2026-10-25: 73
- 2026-10-24: 72
- 2026-10-23: 72

## Common questions

### What is the Web3 DNS (CNSLookup) MCP server?

Web3 DNS (CNSLookup) is an MCP server listed in the public MCP registry as com.cnslookup/web3-dns. Read-only lookup of verified crypto wallet addresses for domains, .cns and ENS names. This page covers its hosted endpoint (https://www.cnslookup.com/mcp).

### Is the Web3 DNS (CNSLookup) MCP server safe to use?

Web3 DNS (CNSLookup) scores 18 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 Web3 DNS (CNSLookup) MCP server expose?

Web3 DNS (CNSLookup) exposes 5 tools: resolve_name, get_payment_address, reverse_lookup, check_name, list_networks. Their descriptions and schemas cost roughly 333 tokens of context every time the server is loaded.

### Does the Web3 DNS (CNSLookup) MCP server require authentication?

Its publisher declares no required credentials for Web3 DNS (CNSLookup). We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the Web3 DNS (CNSLookup) MCP server still maintained?

Web3 DNS (CNSLookup) is still listed as active in the MCP registry. We last reached this channel on 5 November 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://www.cnslookup.com/mcp
- Repository: https://github.com/krizis78/cnslookup
- Website: https://www.cnslookup.com/developers/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-cnslookup-web3-dns/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-cnslookup-web3-dns/www.json
- HTML version of this page: https://verifymcp.io/servers/com-cnslookup-web3-dns/www