WHOIS & Domain Availability (RDAP)

io.github.winters-works-coPublished by GitHub account winters-works-cov1.0.0Updated Oct 24, 2026

Domain WHOIS via official RDAP: registrar, expiry dates, nameservers, availability. Winters Works.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Lets an assistant look up domain registration details via RDAP: registrar, expiry dates, nameservers, and availability.

What you can do
This remote server exposes domain WHOIS-style lookups through official RDAP data. An assistant can query a domain to retrieve its registrar, registration and expiry dates, nameservers, and whether the domain appears to be available. It is a read-only lookup service rather than a management tool.
When to use it
Useful when checking who owns or manages a domain, when a registration is due to expire, which nameservers it uses, or whether a name is still available before registering it.
Requirements
A remote MCP endpoint at mcp.apify.com. Authentication is required: either an Apify API token sent as a Bearer value in the Authorization header, or OAuth sign-in with Apify for clients that support it. Network access to the endpoint is needed.
Before you install
The server requires an Apify credential: an API token in the Authorization header or an OAuth sign-in. Treat that token as a secret and check your Apify plan, since usage may be billed through the Apify platform. Lookup queries are sent to Apify and to public RDAP services.

Installation

In SourceWeft

  1. Open WHOIS & Domain Availability (RDAP) in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.winters-works-co%2Fdomain-whois/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "whois-domain-availability-rdap": {
      "type": "http",
      "url": "https://mcp.apify.com/?actors=wintersworks/domain-whois-mcp-server"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 13, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.