WHOIS domain MCP server that query the WHOIS information using IP2WHOIS API.
WHOIS domain MCP server that query the WHOIS information using IP2WHOIS API. The mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 2 defined tools rather than through you.
A Model Context Protocol (MCP) server that provides comprehensive WHOIS lookup capabilities using the IP2WHOIS API. This server allows AI agents to query domain registration details, including expiry dates, registrar information, and registrant data. This server also supports query on hosted domains by IP address.
Everything the assistant can do here goes through one of these:
get_whois — The get_whois tool exposed by this serverget_hosted_domains — The get_hosted_domains tool exposed by this serverYou will need one environment variable: IP2WHOIS_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Plenty of payments and commerce servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP's toolset — get_whois, get_hosted_domains — is a fair guide to whether it matches your workflow. It is maintained by ip2whois; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| get_whois | The get_whois tool exposed by this server. |
| get_hosted_domains | The get_hosted_domains tool exposed by this server. |
{
"mcpServers": {
"ip2whois": {
"command": "uvx",
"args": ["mcp-ip2whois"],
"env": {
"IP2WHOIS_API_KEY": "<YOUR API key HERE>"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| IP2WHOIS_API_KEY | Credential the server authenticates with. | Yes |
Payments infrastructure meets AI — customers, invoices, subscriptions and current API docs from Stripe's server.
Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.
Give your AI assistant a supervised window into your Interactive Brokers account — balances, positions, live quotes and orders.
Invoices, payments and disputes through PayPal's official server — commerce operations by conversation.
Enables querying and listing Azure resources and costs directly from an MCP client.
Empowers LLMs with Bitcoin Lightning Network payment capabilities via the ZBD API.