WhoisLookup

io.github.therealMrFunGuyPublished by GitHub account therealMrFunGuyv1.0.0Updated Oct 24, 2026

Domain WHOIS, DNS records, SSL certificates, and availability checks.

VerifiedSSEWeb executableWeb Search & Scraping

Overview

AI-generated overview

A remote MCP server that lets an assistant look up domain WHOIS data, DNS records, SSL certificates, and domain availability.

What you can do
It exposes domain research lookups to an assistant: WHOIS registration details, DNS records, SSL certificate information, and checks on whether a domain is available. It runs as a hosted remote endpoint, so the assistant connects to it rather than running anything locally. The manifest does not list individual tool names or parameters.
When to use it
Useful when you need to check who owns a domain, inspect its DNS or certificate setup, or see whether a name is free before registering it. Suited to quick domain due-diligence and troubleshooting rather than bulk data collection.
Requirements
A remote MCP client that supports SSE transport, pointed at the provider's hosted endpoint. An API key is required and must be sent in the X-API-Key header; the key is obtained from the provider's authentication dashboard. Network access to the provider's service is needed.
Before you install
The API key is a secret sent in the X-API-Key header, so keep it out of logs and shared configs. Lookup queries, including the domains you check, are sent to a third-party service. WHOIS and availability results can be stale or incomplete, so verify before acting on them.

Installation

In SourceWeft

  1. Open WhoisLookup in the dashboard and add it to a workspace.
  2. Connect X-API-Key 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 SSE. 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.therealMrFunGuy%2Fwhois-lookup/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.

{
  "mcpServers": {
    "whoislookup": {
      "type": "sse",
      "url": "https://whois.rjctdlabs.xyz/sse",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 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 listedRequired15 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.