
Domainee MCP server
Which MCP servers are Domainee's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-18
- Registry namedev.domainee/domaineeverified in the MCP registry
The registry name sits under domainee.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-18
- Tools18
- Server calls itselfdomainee
- Server version0.3.0
- Protocol version2025-06-18
On 2026-10-18 the server answered initialize and tools/list without a sign-in. First answer in 118 ms.
- Its tools do none of the product's use cases we checked: let customers point their own domain at the product; issue and renew SSL for customer hostnames automatically; get notified when customer DNS records change.
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 score72 of 100answers 100 · does the job 0 · definitions 100 · context 100 · connects 100
- What an agent can do with it0 of 3 use cases
- Answered100% of days10 of 10 daily checks
- Median first answer250 ms
- Space in an agent's context≈ 2,253 tokensthe definitions of all its tools (18), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results18 of 18 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
What an agent can do with it
- cannot · let customers point their own domain at the product
- cannot · issue and renew SSL for customer hostnames automatically
- cannot · get notified when customer DNS records change
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
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 →
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 '@'…
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…
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.
tools_cname_lookupFree public API. Resolve a hostname's CNAME chain. Useful for debugging custom-domain CNAME setups.
tools_http_header_checkerFree public API. Fetch a URL and return its response headers + security grade based on common security headers.
tools_dns_propagation_checkerFree public API. Query the same hostname across ~10 public DNS resolvers worldwide and report which ones return the same answer. Useful right after a DNS change.
tools_redirect_checkerFree public API. Follow a URL's redirect chain and return every hop with status code, response time, final destination.
tools_spf_record_checkerFree public API. Look up and validate the SPF record for a domain. Counts void/total DNS lookups, flags syntax issues, validates against RFC 7208's 10-lookup limit.
tools_domain_age_checkerFree public API. Returns a domain's registration date, age in days + years, last-updated date, and expiration.
tools_subdomain_finderFree public API. Enumerate subdomains for a target domain via Certificate Transparency logs + DNS resolution.
tools_reverse_ip_lookupFree public API. Reverse-DNS (PTR) lookup for an IP address. Returns one or more hostnames if configured.
tools_dmarc_record_checkerFree public API. Look up the DMARC record at _dmarc.<domain>, parse policy/alignment/reporting tags, flag missing or too-permissive settings.
tools_txt_record_lookupFree public API. Fetch all TXT records on a domain, classifying each as SPF, DKIM, DMARC, BIMI, verification token, or general.
tools_website_status_checkerFree public API. Check if a website is up or down. Returns HTTP status, response time, final URL after redirects, basic SSL info.
tools_dkim_record_checkerFree public API. Look up the DKIM record at <selector>._domainkey.<domain>, parse the public key, flag issues.
tools_domain_availability_checkerFree public API. Check availability of a name across one or more TLDs. Pass a `name` (no TLD) and an optional `tlds` array.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"domainee": {
"type": "http",
"url": "https://mcp.domainee.dev/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http domainee https://mcp.domainee.dev/mcpclaude.ai, ChatGPT and other clients: add https://mcp.domainee.dev/mcp as a custom connector in the settings.
OpenAPI spec
40 paths, read 2026-10-18. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.