Domain Availability Checker: Bulk WHOIS Lookup & Domain Age

io.github.Nero-EnginePublished by GitHub account Nero-Enginev0.1.1Updated Oct 29, 2026

Is each domain or name idea available or taken? Plus registration date, expiry, age and registrar.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

Remote Apify-hosted MCP server that lets an assistant check whether domain names are available or taken, with registration date, expiry, age and registrar.

What you can do
  • Check availability of one or more domain or name ideas, including bulk lookups.
  • Retrieve WHOIS details for each domain: registration date, expiry date, domain age and registrar.
  • Compare candidate names side by side to see which are taken and which are free.
When to use it
Useful when brainstorming or shortlisting domain names and you want the assistant to verify availability and age in bulk instead of checking each one by hand.
Requirements
Remote streamable HTTP endpoint at mcp.apify.com with OAuth sign-in; an Apify account and an Apify API token sent as a Bearer token in the Authorization header. Network access required.
Before you install
The Authorization header carries your Apify API token, a secret. Runs are billed per event to your Apify account, so bulk lookups can incur charges. Lookup queries are sent to Apify's hosted service.

Installation

In SourceWeft

  1. Open Domain Availability Checker: Bulk WHOIS Lookup & Domain Age 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.Nero-Engine%2Fdomain-whois-checker/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": {
    "domain-availability-checker-bulk-whois-l": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=nerolabs/domain-whois-checker"
    }
  }
}

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

2
  1. v0.1.1LatestOct 29, 2026
  2. v0.1.0Oct 1, 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.