Web3 DNS (CNSLookup)
REMOTE · WWW.CNSLOOKUP.COM
Read-only lookup of verified crypto wallet addresses for domains, .cns and ENS names.
Available components
Last scanned (7 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 502, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 502. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
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.
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.
- 1 Nov 26 −58
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.27 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +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.
- 29 Oct 26 +57
- Authorization: unverified → partial ▲ security
- HTTPS: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- HSTS header: fail → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.20 ▲ functional
- 27 Oct 26 −55
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.10 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 25 Oct 26 +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.
- 24 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 23 Oct 26 72
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 5 Nov 2026 · Probed https://www.cnslookup.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cnslookup.com | CN=WE1,O=Google Trust Services,C=US | 6 Oct 2026 | 4 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | dcfe4760b056d9020e535f3dddc29335 |
| SANs: cnslookup.com, *.cnslookup.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 www.cnslookup.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| cnslookup.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 502 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.cnslookup.com/mcp | HTTP error | 502 | |
| http (plaintext) | http://www.cnslookup.com/mcp | Inconclusive | 502 |
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 →
check_name Check a name ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | A DNS domain (example.com), a .cns name (example.cns) or an ENS name (example.eth) |
No output schema declared.
No examples provided.
get_payment_address Get a payment address ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | Network code from list_networks, such as ETH, BASE, SOL or BTC. Omit for the name's main network |
| to | string | yes | The name or 0x address to pay |
No output schema declared.
No examples provided.
list_networks List payment networks ~28
Supported payment networks with their codes, chain IDs and symbols, and the registry's home network.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
resolve_name Resolve a name ~88
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".
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | A DNS domain (example.com), a .cns name (example.cns) or an ENS name (example.eth) |
No output schema declared.
No examples provided.
reverse_lookup Reverse lookup ~45
The primary Web3 DNS name set for an EVM wallet address, or null.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | An EVM address (0x followed by 40 hex characters) |
No output schema declared.
No examples provided.
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.
remote · www.cnslookup.com
claude mcp add --transport http com-cnslookup-web3-dns 'https://www.cnslookup.com/mcp'
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.