Web3 DNS (CNSLookup)
by cnslookup.com in Onchain & crypto
Read-only lookup of verified crypto wallet addresses for domains, .cns and ENS names.
https://www.cnslookup.com/mcp- Tools
- 5
- open to any client
- Uptime
- 47.8%
- last 30 days
- Response time
- 255 ms
- 328 ms slowest 5%
- Last check
- Failed
- 17 h ago, next in 6 h
Reliability
Latest check failed 17 h ago: initialize returned HTTP 502
Status and outage history · Atom feed · Watch with other listings
How to connect
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"web3-dns-cnslookup": {
"type": "http",
"url": "https://www.cnslookup.com/mcp"
}
}
}5 tools
- 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".
- 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.
- reverse_lookup
The primary Web3 DNS name set for an EVM wallet address, or null.
- 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.
- list_networks
Supported payment networks with their codes, chain IDs and symbols, and the registry's home network.
Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 17 h ago | initialize returned HTTP 502 | 502 | 249 ms |
| 45 h ago | initialize returned HTTP 502 | 502 | 253 ms |
| 3 days ago | initialize returned HTTP 502 | 502 | 241 ms |
| 4 days ago | initialize returned HTTP 502 | 502 | 287 ms |
| 6 days ago | initialize returned HTTP 502 | 502 | 233 ms |
Show 10 older checks
| 7 days ago | initialize returned HTTP 502 | 502 | 278 ms |
| 9 days ago | initialize returned HTTP 502 | 502 | 280 ms |
| 9 days ago | initialize returned HTTP 502 | 502 | 253 ms |
| 10 days ago | initialize returned HTTP 502 | 502 | 318 ms |
| 10 days ago | Passed | 200 | 256 ms |
| 11 days ago | Passed | 200 | 294 ms |
| 11 days ago | Passed | 200 | 257 ms |
| 12 days ago | Passed | 200 | 208 ms |
| 13 days ago | initialize returned HTTP 502 | 502 | 224 ms |
| 14 days ago | initialize returned HTTP 502 | 502 | 216 ms |