dev.domainee/domainee
dev.domainee/domainee · 1.0.2
Custom domains API for SaaS: connect, verify, and manage customer domains, SSL, and DNS
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 60 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 15 of 15 | The registry entry declares a key or a token. |
| Latest connection test reached it | 20 of 20 | The latest test had its handshake answered. |
Where it answers
https://mcp.domainee.dev/mcpstreamable-httpAuthorizationoptional, secret: Optional. Bearer token using a Domainee API key, e.g. `Bearer sk_live_...`. Without it the 18 free diagnostic tools still work and tools/list enumerates them; with it you also get the 12 workspace too
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 18 tools.
- Protocol
- 2025-06-18
- Calls itself
- domainee 0.3.0
- Handshake time
- 139 ms
- HTTP status
- 200
The tools it lists (18, as of 3 hours ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
tools_ssl_checkFree public API. Check the TLS certificate of any public hostname. Returns issuer, subject, validity dates, days until expiry, full chain, cipher, protocol, and SAN list. No Bearer required.
tools_dns_provider_lookupFree public API. Identify which DNS provider actually serves a domain, fingerprinted from its public NS records. Returns the record name written the way that provider's form expects it (providers disagree about whether the apex is '@', blank, or the full domain, and getting it wrong is the most common way a correct record lands in the wrong place), whether the provider can point a zone apex at a hostname, where its record editor lives, and the provider-specific settings that silently break custom domain setups. Use this before telling someone what DNS record to add. No Bearer required.
tools_domain_connect_checkerFree public API. Check whether a domain's DNS provider implements the Domain Connect protocol, read live from the _domainconnect TXT record and the provider's settings endpoint. Reports the provider and whether it offers the synchronous flow (a signed redirect with no token exchanged, the one that works in practice) or only the asynchronous OAuth flow. Note that provider support is necessary but not sufficient for one-click setup: the service being connected must also have a template the provider has synced and enabled, which many providers do only after a per-service onboarding. No Bearer req
tools_dns_record_lookupFree public API. Look up DNS records (A, AAAA, CNAME, MX, TXT, NS, SOA) for any domain.
tools_whois_lookupFree public API. WHOIS / RDAP lookup for a domain — registrar, status, created/updated/expires dates, nameservers.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
dev.domainee/domainee, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 27 days ago. The registry entry · domainee.dev