TLDix MCP server

• Registry namecom.tldix/tldixverified in the MCP registry

The registry name sits under tldix.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-30
• Tools10
• Server calls itselftldix
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-30 the server answered initialize and tools/list without a sign-in. First answer in 593 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 3 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
• Answeredmeasuring3 of the 7 daily checks it takes to print a share
• Median first answer853 ms
• Space in an agent's context≈ 1,436 tokensthe definitions of all its tools (10), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results0 of 10 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• lookup_domain

  Looks up one domain in WHOIS/RDAP and returns whether it is registered, its expiry and registration dates, days until expiry, registrar, status codes and nameservers. Results may be cached for up to 48 hours. Does not need a TLDix account.

• check_domain_expiries

  Checks up to 25 domains at once and returns each one's expiry date, days left and registrar, sorted by what expires first. Domains that time out are marked "pending" and can be checked again. Does not need a TLDix account.

• check_ssl_certificate

  Connects to the domain on port 443 and returns the TLS certificate's issuer, validity dates, days until expiry and the names it covers. Does not need a TLDix account.

• get_account_overview

  Returns the signed-in user's TLDix plan, how many domains, hosting and licence items they track against their plan limits, and the next five renewals.

• list_upcoming_renewals

  Lists the signed-in user's domains, hosting and licence/service renewals that expire within the given number of days (already expired items are included), sorted by date.

• list_tracked_domains

  Lists the domains the signed-in user tracks in TLDix with expiry date, days left, registrar and which alert days are on. Supports a name filter and paging.

• add_domain

  Adds a domain to the signed-in user's TLDix tracking list so they get expiry alerts. Looks the domain up first; fails with a clear message if it is not registered or the plan's domain limit is reached. Adding a domain that is already…

• add_hosting_renewal

  Adds a hosting plan renewal (provider, the site it hosts and its renewal date) to the signed-in user's TLDix list. Alerts go out 30, 7 and 1 days before the date.

• add_license_renewal

  Adds a software licence, plugin, theme, SaaS subscription or other service renewal to the signed-in user's TLDix list. Alerts go out 30, 7 and 1 days before the date.

• remove_tracked_item

  Removes one item from the signed-in user's TLDix list: a domain by name, or a hosting or licence item by the id shown in list_upcoming_renewals. Its alerts stop.