Name: WHOIS Domain Lookup
Author: Mamba Labs

WHOIS Domain Lookup MCP

Registrar, created and expiry dates, domain age, and nameservers per domain, from RDAP and WHOIS

Grade A Local · stdio API key 1 tool v1.0.0 MIT

No reviews yet by Mamba Labsnpm Runs on your machine, nothing hosted

96/100

trust score

tool declared

local

runs on your machine

—

downloads a day

What it does

Registrar, created and expiry dates, domain age, and nameservers per domain, from RDAP and WHOIS

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --env 'APIFY_TOKEN=${APIFY_TOKEN}' --transport stdio whois-domain-lookup-mcp '--' npx -y @mambalabsdev/mcp-whois-domain-lookup

# 2 — ask your agent for something these tools do
#   lookup_domain_whois

It needs APIFY_TOKEN: this reads it from your environment, so export it first.

WHOIS Domain Lookup costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publisher

Mamba Labs103 servers

11 categories · publishing since 2026

All 103 servers

Installation

Where are you running it?

Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts WHOIS Domain Lookup as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.

Claude Codedeclared by this listing

This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads APIFY_TOKEN (Apify API token from https://console.apify.com/account/integrations) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx APIFY_TOKEN … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.

claude mcp add --scope user --env 'APIFY_TOKEN=${APIFY_TOKEN}' --transport stdio whois-domain-lookup-mcp '--' npx -y @mambalabsdev/mcp-whois-domain-lookup

Reconnect, or start a new session, and the tools appear in the model’s tool list.

Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.

What it asks of you

It reaches a system of yours, so it needs your own credential rather than the publisher’s: APIFY_TOKEN — Apify API token from https://console.apify.com/account/integrations. You set it in your own client’s config, on your machine — this marketplace never holds it.

What it writes

One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.

What you approve

1 tool, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

Read from its source code. A server that builds its tool list when it starts can list more tools than this.

Look up who registered a domain, when, and when it expires. Give domains, website URLs, or email addresses (up to 5,000). For each registrable domain the actor asks the registry's own RDAP server (from the IANA list), or its port 43 WHOIS server where there is no RDAP, and returns one row:…

Parameter	Type	Required	Notes
domains	array	no	Domains, website URLs, or email addresses, up to 5,000. Subdomains are looked up as their registrable domain.
domain	string	no	One domain, URL, or email address, for example stripe.com.
follow_registrar_rdap	string	no	true (default) also reads the registrar's RDAP record for the abuse email and any registrant details it publishes.
include_raw	string	no	true puts the registry's raw RDAP JSON or WHOIS text in raw_response. Default false.
max_charge_usd	string	no	Optional. The run stops before a charge would pass this amount.

Free

$0 forever

Every tool, no call limit
No card, and mcprush charges nothing for it
Source published under MIT
Runs on your machine — nothing of it reaches our gateway
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install WHOIS Domain Lookup or to call it, at any volume.

ATrust score 96 / 100

Release 1.0.0 · scanned 2 Nov 2026

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score96

Findings1 threat · 1 capability

Capabilitymoderate

Coveragesource

Verificationrepo

Surface digest49a7a5f962a335e739340c3b7eadfeab506cf1493e45db39953195d2cc4a9e7c

Score vectorthreat 100 → client 96

Term	Level	What it prices	Points
capability-exposure	moderate	capability blast radius (moderate) — client exposure if the model is manipulated	−3
verification-discount	repo	publisher verification (public source) — no provenance, but the source is public and inspectable	−1
coverage-honesty	source	inspection depth (source) — how much of the target the scan could see	−0

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

Tool surfaceread

Implementation sourceread

Package metadataread

Live transportnot available

Tools were statically extracted from the published source (1 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.

Tool	Capability tags	Why the tag was assigned
lookup_domain_whois	untrusted-inputexternal-sink	untrusted-input: declares openWorldHint: true (interacts with entities outside the server); external-sink: handler sends an HTTP POST (fetch(https://api.apify.com/v2/acts/${actorPath}/runs?timeout=${ACTOR_RUN_TIMEOUT_SECS}) at build/index.js:80

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

flow-1

Untrusted input can drive an external action even though no sensitive source is exposed.

Supply chain and provenance

Integrityfirst-seen

Surface digest49a7a5f962a335e7

Scanned2026-11-02

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.