whois_as
Looksup whois information about the Autonomous System Number (ASN)
Answer who owns a domain, an IP, a TLD or an autonomous system in the conversation that raised the question.
LABSCO SUMMARY
Four lookups cover the chain from a top-level domain down to a single address, and the ASN lookup turns an IP in a log into the network that announces it. It is a small surface on purpose: nothing to authorise, nothing to configure, and the answers are the registry's own records.
Four WHOIS lookups: a domain name, a top-level domain, an IP address, and an autonomous system number.
npx on your PATH. No account, no key.
One command — npx -y @bharathvaj/whois-mcp@latest
USE CASES
The domain lookup answers whether it is registered and by whom, and the TLD lookup covers the registry behind the extension when the question is about a suffix rather than a name.
An IP lookup gives the registration for the address itself; the ASN lookup names the autonomous system that announces it, which is the level at which "who is this traffic" is usually answerable.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
whois_asLooksup whois information about the Autonomous System Number (ASN)
whois_domainLooksup whois information about the domain
whois_ipLooksup whois information about the IP
whois_tldLooksup whois information about the Top Level Domain (TLD)
BEFORE YOU INSTALL
4 tools when we connected.
npx on PATH
CONTEXT COST
Rated by the size of the 4 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Add the block to your client, or run the command directly.
{
"mcpServers": {
"whois-mcp": {
"command": "npx",
"args": [
"-y",
"@bharathvaj/whois-mcp@latest"
]
}
}
}npx -y @bharathvaj/whois-mcp@latest