Next free-source huntWe check for new free data every weekday.
FinancialCrypto & DeFiOSINT & web intelligenceMCP serverFirst audited Nov 13, 2026

Web3 DNS (CNSLookup)

Read-only lookup of verified crypto wallet addresses for domains, .cns and ENS names.The vendor's description, from its MCP Registry listing.

Not workingAudited Nov 13, 2026
  • Failed: The MCP handshake failed.

The address answers, but the MCP connection or tool listing fails. Public audit: we connect as an AI client would, list the tools and check what they say. We do not run them. How we audit

Does it work?
NoThe address answers, but MCP does not work.
Sign-up?
UnknownWe could not tell.
Can it change things?
UnknownWe could not list its tools.
Endpointhttps://www.cnslookup.com/mcp

Source code Website Streamable HTTP

What we checked, the evidence, and the tools it offers.

Trust Consensus score

Our audit and agent test side by side with public signals, as of 2026-11-17. Missing signals earn no points. A summary of public signals, not a security certification. How the score works

20/100E

Signals agree · data for 85 of 100 points

Signals behind the score
SignalPointsWhat we found
Signal Lab audit0/45Latest result: not-working. (2026-11-13)
Audit reliability0/10Answered in 0 of 1 weekly audits. (2026-11-13)
AI agent test–/15Not tested by an agent yet.
Public repository10/20GitHub: 0 stars, last push 2026-10-23, licence MIT. (2026-11-17)
Registry and endpoint10/10Active in the official MCP Registry; endpoint on the vendor's own website domain.

Run this server? Add the badge to your README

Signal Lab trust score badge
[![Signal Lab trust score](https://signal-lab.qdt.ai/badge/com-cnslookup-web3-dns.svg)](https://signal-lab.qdt.ai/mcp-servers/com-cnslookup-web3-dns)
<a href="https://signal-lab.qdt.ai/mcp-servers/com-cnslookup-web3-dns"><img src="https://signal-lab.qdt.ai/badge/com-cnslookup-web3-dns.svg" alt="Signal Lab trust score" height="20"></a>

What we checked

Security

  • Passed: Connections are encrypted (HTTPS).

Protocol

  • Failed: The MCP handshake failed.

    • HTTP 502

Connection

  • Passed: The server responds.

Audit history

  1. Nov 13Not working

What we sent

Every request in this audit, with the answer and how long it took. We never send credentials and never call a tool.

RequestAnswerTime
initializeHTTP 502543 ms
initializeHTTP 502161 ms

Run this server, or disagree with the result?

Fix the issue and it shows in the next weekly audit, or email us to ask for a re-audit or to dispute a finding. Read how we audit for what each check means.