_ registry / mcp streamable-http · checked 1h ago

tldix

https://tldix.com

Registry code: 045ee535fb47c169

api record

TLDix tracks domain, hosting and licence/service renewals. lookup_domain, check_domain_expiries and check_ssl_certificate work without an account. The other tools read or change the signed-in user's TLDix list. Dates are YYYY-MM-DD; days_until_expiry is negative for items that already expired.

endpoint
https://tldix.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is tldix live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is tldix free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does tldix have?
10 tools: lookup_domain, check_domain_expiries, add_domain, add_hosting_renewal, add_license_renewal, remove_tracked_item, list_tracked_domains, check_ssl_certificate, ….
Is tldix safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
362ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 10 tools
10 auth-required 10 of 10 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • lookup_domain auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "Domain name, e.g. example.com. A URL or www. prefix is accepted and stripped."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • check_domain_expiries auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domains"
  ],
  "properties": {
    "domains": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 25,
      "minItems": 1,
      "description": "Domain names to check (1 to 25)."
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • add_domain auth-required never probed

    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 tracked changes nothing.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "Domain name, e.g. example.com. A URL or www. prefix is accepted and stripped."
    },
    "alert_days": {
      "type": "array",
      "items": {
        "enum": [
          60,
          30,
          14,
          7,
          3,
          1
        ],
        "type": "integer"
      },
      "description": "Days before expiry to send email alerts. Defaults to all of 60, 30, 14, 7, 3 and 1."
    }
  },
  "additionalProperties": false
}
    arguments 28 lines
  • add_hosting_renewal auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "provider",
    "domain",
    "renewal_date"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "Domain name, e.g. example.com. A URL or www. prefix is accepted and stripped."
    },
    "provider": {
      "type": "string",
      "description": "Hosting company, e.g. SiteGround."
    },
    "renewal_date": {
      "type": "string",
      "description": "Renewal or expiry date in YYYY-MM-DD format."
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • add_license_renewal auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name",
    "renewal_date"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "What renews, e.g. \"Elementor Pro\"."
    },
    "notes": {
      "type": "string",
      "description": "Free-text notes (optional, up to 1000 characters)."
    },
    "client": {
      "type": "string",
      "description": "Client or reference this item belongs to (optional)."
    },
    "category": {
      "type": "string",
      "description": "Category such as plugin, theme, saas, email (optional)."
    },
    "provider": {
      "type": "string",
      "description": "Vendor (optional)."
    },
    "renewal_date": {
      "type": "string",
      "description": "Renewal or expiry date in YYYY-MM-DD format."
    }
  },
  "additionalProperties": false
}
    arguments 34 lines
  • remove_tracked_item auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "type"
  ],
  "properties": {
    "id": {
      "type": "integer",
      "description": "Item id, for type \"hosting\" or \"license\"."
    },
    "type": {
      "enum": [
        "domain",
        "hosting",
        "license"
      ],
      "type": "string",
      "description": "Kind of item."
    },
    "domain": {
      "type": "string",
      "description": "Domain name, for type \"domain\"."
    }
  },
  "additionalProperties": false
}
    arguments 26 lines
  • list_tracked_domains auth-required 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "sort": {
      "enum": [
        "expiry",
        "name"
      ],
      "type": "string",
      "description": "Sort by soonest expiry (default) or by name."
    },
    "limit": {
      "type": "integer",
      "maximum": 200,
      "minimum": 1,
      "description": "Page size. Default 50."
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "description": "Items to skip. Default 0."
    },
    "search": {
      "type": "string",
      "description": "Only domains containing this text."
    }
  },
  "additionalProperties": false
}
    arguments 29 lines
  • check_ssl_certificate auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "Domain name, e.g. example.com. A URL or www. prefix is accepted and stripped."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • get_account_overview auth-required 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • list_upcoming_renewals auth-required 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "days": {
      "type": "integer",
      "maximum": 730,
      "minimum": 1,
      "description": "Look-ahead window in days. Default 60."
    },
    "type": {
      "enum": [
        "all",
        "domain",
        "hosting",
        "license"
      ],
      "type": "string",
      "description": "Which kind of item to include. Default all."
    },
    "limit": {
      "type": "integer",
      "maximum": 200,
      "minimum": 1,
      "description": "Maximum items to return. Default 50."
    }
  },
  "additionalProperties": false
}
    arguments 28 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 045ee535fb47c169.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/045ee535fb47c169/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/045ee535fb47c169/badge.svg)](https://brick.blue/agent/045ee535fb47c169?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.