Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Domain RDAP MCP

REMOTE · ADS.GETLULU.DEV

Free, keyless domain registration lookup via RDAP: registered, available, registrar, expiration.

Available components

0 this week 23 Trust /100

Last scanned (19 hours ago)

Scores higher than 7% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (5)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (6)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Oct 26 23
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Schema quality: 0 → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 17 Sept 26 0
    • Stability: 0.97 → pass security
  • 13 Sept 26 0
    • Stability: pass → 0.87 functional
  • 6 Sept 26 0
    • Stability: 0.97 → pass security
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://ads.getlulu.dev/domain/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=ads.getlulu.dev CN=WR3,O=Google Trust Services,C=US 29 Oct 2026 27 Jan 2027 RSA 2048 SHA256-RSA a5dba8999a7cdb5709baaa79d5cfb432
SANs: ads.getlulu.dev
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of ads.getlulu.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
getlulu.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 502
Header Value
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ads.getlulu.dev/domain/mcp HTTP error 502
http (plaintext) http://ads.getlulu.dev/domain/mcp HTTPS enforced 301 https://ads.getlulu.dev:443/domain/mcp
MCP tools · 1 exposed · ~271 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_domain ~271

Check whether a domain name is registered, using real-time RDAP data (the IETF-standardized successor to WHOIS). Use for "is domain-x.com available/registered", "who is domain-x.com registered with", or "when does domain-x.com expire" style questions. `domain` is a bare domain like "example.com" -- no protocol prefix, no path, no spaces. If the domain is NOT registered, returns `{"domain": ..., "registered": false}` -- this is a normal, meaningful answer (the domain is available), not an error. If the domain IS registered, returns `{"domain", "registered": true, "status", "registered_date", "expiration_date", "last_changed_date", "registrar"}`. `status` is a list of RDAP status codes (e.g. "active", "client transfer prohibited"). Dates are ISO 8601. `registrar` is the registrar's name, or null if the registry redacts it for privacy. For obviously malformed input (not a domain -- e.g. missing a dot, has spaces, or includes a protocol like "https://"), returns a clean `{"error": ...}` instead of calling the API.

NameTypeReqDescription
domainstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Domain RDAP MCP server?

Domain RDAP MCP is a hosted endpoint at https://ads.getlulu.dev/domain/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · ads.getlulu.dev

# add to Claude Code
claude mcp add --transport http lulu-the-narwhal-domain-rdap-mcp 'https://ads.getlulu.dev/domain/mcp'
Common questions

What is the Domain RDAP MCP server?

Domain RDAP MCP is listed in the public MCP registry as io.github.Lulu-The-Narwhal/domain-rdap-mcp. Free, keyless domain registration lookup via RDAP: registered, available, registrar, expiration. This page covers its hosted endpoint (https://ads.getlulu.dev/domain/mcp).

Is the Domain RDAP MCP server safe to use?

Domain RDAP MCP scores 23 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Domain RDAP MCP server expose?

Domain RDAP MCP exposes 1 tool: check_domain. Their descriptions and schemas cost roughly 271 tokens of context every time the server is loaded.

Does the Domain RDAP MCP server require authentication?

Its publisher declares no required credentials for Domain RDAP MCP. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Domain RDAP MCP server still maintained?

Domain RDAP MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Domain RDAP MCP server?

VerifyMCP ran 5 checks on Domain RDAP MCP, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Domain RDAP MCP: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.