← Registry

Developer Tools

enswhois.com

This server provides ENS name lookups and related data for Ethereum addresses.

1 endpoint8 known toolsFirst detected August 20, 2026Last detected August 20, 2026

ENDPOINT 1

https://mcp.enswhois.com/mcp

No auth detected

MCP server metadata

Name
enswhois
Version
1.0.0
Capabilities
tools.listChanged
Server instructions

enswhois.com ENS tools: WHOIS lookups, reverse address→names, namehash/labelhash decoding, ENS text/address records, and ERC-8004 agent identity (ENSIP-25/26). Unauthenticated use is rate-limited to 5 requests/minute per client; set an enswhois API key for higher tiers.

Known tools 8

whois

Look up an ENS name: ownership, resolver, expiry, wrapper status and availability.

Inferred read-only
list_domains

List ENS names associated with an Ethereum address.

Inferred read-only
lookup_namehash

Resolve an ENS namehash (the 0x-prefixed 32-byte node hash) back to its domain, if indexed.

Inferred read-only
lookup_labelhash

Find ENS domains whose label matches a labelhash (the 0x-prefixed keccak256 of a single label).

Inferred read-only
get_text_record

Read a single ENS text record for a name (e.g.

Inferred read-only
list_text_records

List all current resolver records for an ENS name: text records, address records (by coin type) and contenthash.

Inferred read-only
is_erc8004_agent

Check whether an ENS name is an ERC-8004 (Trustless Agent) identity.

Inferred read-only
agent_profile

Read an ENS name's AI-agent profile (ENSIP-26): agent-context plus the agent-endpoint records for MCP, A2A and web, alongside its ERC-8004 registration status.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.enswhois]
url = "https://mcp.enswhois.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "enswhois": {
      "type": "http",
      "url": "https://mcp.enswhois.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: enswhois
Remote MCP URL: https://mcp.enswhois.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "enswhois": {
      "url": "https://mcp.enswhois.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "enswhois": {
      "type": "http",
      "url": "https://mcp.enswhois.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "enswhois",
  "transport": "streamable-http",
  "url": "https://mcp.enswhois.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for enswhois.com was fetched 2026-08-24T07:44:09.264Z.

Trust status Trusted

enswhois.com is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.