Skip to main content
Glama
ip2whois

mcp-ip2whois

Official
by ip2whois
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
IP2WHOIS_API_KEYYesThe IP2WHOIS API key, which allows you to query up to 500 per month for free and more details of the IP address. You can sign up for a free API key, or subscribe to a plan to enjoy more benefits.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_whoisA
Lookup WHOIS data for a domain name. Use this tool when the user asks about 
domain registration details, registrar names, expiry dates, domain ownership, 
or nameservers for a specific website (e.g., 'google.com').

Args:
    domain: The domain name to look up (e.g., 'example.com').

Returns:
    A JSON string result includes domain age, update and expiry date, assiociated nameservers, registrar and registrant information, and admin, tech and billing information.
get_hosted_domainsA
Lookup for the list of hosted domain names by IP address.

Args:
    ip: The ip address (IPv4 or IPv6) to look up.

Returns:
    A JSON string result includes the domains hosted on the ip address, and the 
    total number of hosted domains found.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.1/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one resolves IP addresses to hosted domains, the other retrieves WHOIS data for domain names. There is no functional overlap.

Naming Consistency5/5

Both tools follow the consistent verb_noun pattern (get_hosted_domains, get_whois), making the naming predictable and easy to understand.

Tool Count3/5

With only two tools, the server feels minimal for the domain of IP and domain information. While the tools cover core functionalities, the count is at the lower boundary of what's reasonable.

Completeness3/5

The tools cover hosted domains and WHOIS lookups, but common related operations like IP geolocation, domain availability checks, or reverse IP lookups are missing. The surface is functional but not comprehensive.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources