Security & Testing

dc5.tech

Provides domain, IP, ASN, and Web3 target lookups plus homograph detection, email security grading, and data-source inventory for security testing.

1 endpoint4 known toolsFirst detected October 20, 2026Last detected October 20, 2026

ENDPOINT 1

https://whois.dc5.tech/mcp

No auth detected

MCP server metadata

Name: dc5-whois
Version: 2026.10.18-cdf49eb

Capabilities

loggingtools.listChanged

Server instructions

Free WHOIS / RDAP / DNS / network / Web3 lookup service. Start with `lookup_target` for any domain, IP, CIDR, ASN (AS15169) or Web3 name; it returns registration, DNS, routing, cloud, reputation and naming facts plus a link to the full page. Use `check_mail_security` for the full email-authentication breakdown, `check_lookalike` to screen many names offline, and `list_data_sources` to see how fresh the local datasets are. Treat reputation and look-alike results as signals, not verdicts.

Known tools 4

check_lookalike

Check whether one domain or Web3 name is a visual look-alike (homograph): letters from different scripts mixed in one label, or every non-ASCII letter having a Latin twin, so раураl.

Inferred read-only

check_mail_security

Grade one domain's email authentication and list every check: SPF (single record, the 10 DNS-lookup limit across includes, the all qualifier), DMARC (policy, inheritance from the organizational domain, pct, report addresses), MTA-STS, TLS-RPT, BIMI, DANE and null MX.

Potential side effects

list_data_sources

List the local datasets and feeds behind lookup_target (RIR delegations, IANA, Public Suffix List, cloud / CDN ranges, Tor and Private Relay, reputation lists, GeoLite2) with state, record count, generation date and a stale flag.

Inferred read-only

lookup_target

Look up one domain, IP address, CIDR block, ASN (AS15169) or Web3 name (ENS .

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.dc5-whois]
url = "https://whois.dc5.tech/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "dc5-whois": {
      "type": "http",
      "url": "https://whois.dc5.tech/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: dc5-whois
Remote MCP URL: https://whois.dc5.tech/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": {
    "dc5-whois": {
      "url": "https://whois.dc5.tech/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "dc5-whois": {
      "type": "http",
      "url": "https://whois.dc5.tech/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "dc5-whois",
  "transport": "streamable-http",
  "url": "https://whois.dc5.tech/mcp"
}

MCP Inspector

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

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

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