Web3 DNS (CNSLookup) MCP Server

by cnslookup Your server? Claim it

answering

Web3 DNS (CNSLookup) is answering right now. Last checked 8 min ago. It exposes 5 tools. Last commit 24 Oct 2026.

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

Uptime history 57 hours of history · worst hour 75%

57 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

269 ms

Response time

average over 24h

Stars

last commit 24 Oct 2026

Web3 DNS (CNSLookup) missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add web3-dns --transport http https://www.cnslookup.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://www.cnslookup.com/mcp

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

name

check_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.

networks

list_networks

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

payment

get_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.

resolve

resolve_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".

reverse

reverse_lookup

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

Endpoints

URL	Transport	State	Latency	Checked
https://www.cnslookup.com/mcp	streamable-http	answering	224 ms	8 min ago

Alternatives to Web3 DNS (CNSLookup)

same job, measured the same way

Referral Codes

by cryptoexchange

Verified referral and discount codes for crypto exchanges, wallets and trading tools. Read-only.

3 tools answering

osint.foundation

by osint

OSINT lookups: usernames, social profiles, phones, domains, IPs, crypto wallets and companies.

51 tools answering

Realopengroup

by realopengroup

Verify crypto wallets and generate proof of funds letters for buying real estate with crypto.

26 tools answering

BITHOT

by ifcode

Read-only MCP for curated crypto, Web3, and memecoin picks and reports.

7 tools answering

SaveSaveSaveSave

by stefantsezarov

Check messages, npm packages and crypto addresses before acting. Read-only scanner tools.

57 installs/wk local only

Cryptominium

by cryptominium

What a crypto position would really sell for: measured exit costs, address and transaction lookups.

8 tools answering

Crypto Intelligence

by tompeezy

Read-only crypto claim discovery and unsigned readiness; no wallets, quotes or payments.

local only

Vice City Hub

by vicecityhub

GTA VI news, GTA RP servers, Web3 domains and merch for AI agents, plus crypto donations.

25 tools answering

Web3 DNS (CNSLookup) — questions

Answers built from our own checks of this server.

What can Web3 DNS (CNSLookup) do?

It exposes 5 tools, read directly from the server on our last check. Among them: check_name, get_payment_address, list_networks, resolve_name, reverse_lookup. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Web3 DNS (CNSLookup) working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 269 ms. The bar chart above shows every period we have measured.

How do I connect Web3 DNS (CNSLookup)?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Web3 DNS (CNSLookup) need an API key?

No. Web3 DNS (CNSLookup) completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Web3 DNS (CNSLookup)?

It answers our handshake in 269 ms on average, which is faster than 63% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Web3 DNS (CNSLookup) open source?

The code is open source: it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at cnslookup.com, which runs on its operator's own terms.