dev.domainee/domainee
REMOTE · MCP.DOMAINEE.DEV · SCANNED SEP 20
Custom domains API for SaaS: connect, verify, and manage customer domains, SSL, and DNS
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1254 tokens (~69/item across 18 items; 18 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the dev.domainee/domainee MCP server?
dev.domainee/domainee is a hosted endpoint at https://mcp.domainee.dev/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 · mcp.domainee.dev
claude mcp add --transport http dev-domainee-domainee 'https://mcp.domainee.dev/mcp'
{
"mcpServers": {
"dev-domainee-domainee": {
"url": "https://mcp.domainee.dev/mcp"
}
}
} {
"servers": {
"dev-domainee-domainee": {
"type": "http",
"url": "https://mcp.domainee.dev/mcp"
}
}
} [mcp_servers.dev-domainee-domainee] url = "https://mcp.domainee.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-domainee-domainee": {
"type": "remote",
"url": "https://mcp.domainee.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-domainee-domainee --url 'https://mcp.domainee.dev/mcp' --transport streamable-http
mcp_servers:
dev-domainee-domainee:
url: "https://mcp.domainee.dev/mcp" {
"McpServers": {
"dev-domainee-domainee": {
"Transport": "http",
"Url": "https://mcp.domainee.dev/mcp"
}
}
} assistant mcp add dev-domainee-domainee -t streamable-http -u 'https://mcp.domainee.dev/mcp'
{
"mcpServers": {
"dev-domainee-domainee": {
"type": "http",
"url": "https://mcp.domainee.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 18 Sept 26 0
- Tool “tools_domain_connect_checker” rewrote its description, which is the text the model reads security
- 10 Sept 26 +1
- Schema quality: 60 → 69 ▼ functional
- New tool “tools_dns_provider_lookup” functional
- New tool “tools_domain_connect_checker” functional
- 4 Sept 26 0
- Stability: 0.97 → pass security
- 3 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Sept 26 −1
- Stability: pass → 0.93 functional
- 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Probed https://mcp.domainee.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.domainee.dev | CN=YR2,O=Let's Encrypt,C=US | 3 Sept 2026 | 2 Dec 2026 | RSA 2048 | SHA256-RSA | 66c415ac92ebead7241e86bed6f42eac2c3 |
| SANs: mcp.domainee.dev | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.domainee.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| domainee.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.domainee.dev/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://mcp.domainee.dev/.well-known/oauth-protected-resource"Protected resource metadata
| Document | https://mcp.domainee.dev/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.domainee.dev |
| Authorisation server | https://api.domainee.dev |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.domainee.dev/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.domainee.dev/mcp | HTTPS enforced | 301 | https://mcp.domainee.dev/mcp |
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 →
tools_cname_lookup ~49
Free public API. Resolve a hostname's CNAME chain. Useful for debugging custom-domain CNAME setups.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Hostname to resolve, e.g. www.example.com. |
No output schema declared.
No examples provided.
tools_dkim_record_checker ~79
Free public API. Look up the DKIM record at <selector>._domainkey.<domain>, parse the public key, flag issues.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to check DKIM for. |
| selector | string | yes | DKIM selector — `google`, `k1`, `mxvault`, `s1`, etc. |
No output schema declared.
No examples provided.
tools_dmarc_record_checker ~60
Free public API. Look up the DMARC record at _dmarc.<domain>, parse policy/alignment/reporting tags, flag missing or too-permissive settings.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to check DMARC for. |
No output schema declared.
No examples provided.
tools_dns_propagation_checker ~68
Free 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.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Hostname to check. |
| type | string | – | Record type. Default: A. |
No output schema declared.
No examples provided.
tools_dns_provider_lookup ~148
Free 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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain or hostname. Subdomains are walked up to the zone holding the NS records. |
No output schema declared.
No examples provided.
tools_dns_record_lookup ~75
Free public API. Look up DNS records (A, AAAA, CNAME, MX, TXT, NS, SOA) for any domain.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to query, e.g. example.com. |
| type | string | – | Restrict to one record type. Default: all common types. |
No output schema declared.
No examples provided.
tools_domain_age_checker ~45
Free public API. Returns a domain's registration date, age in days + years, last-updated date, and expiration.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to check. |
No output schema declared.
No examples provided.
tools_domain_availability_checker ~102
Free public API. Check availability of a name across one or more TLDs. Pass a `name` (no TLD) and an optional `tlds` array.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Bare name without TLD, e.g. `mybrand`. |
| tlds | array | – | Optional list of TLDs to check, e.g. ['com', 'io', 'dev']. Default: a standard SaaS set. |
No output schema declared.
No examples provided.
tools_domain_connect_checker ~138
Free 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 required.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to check, e.g. example.com. |
No output schema declared.
No examples provided.
tools_http_header_checker ~50
Free public API. Fetch a URL and return its response headers + security grade based on common security headers.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full URL with scheme, e.g. https://example.com. |
No output schema declared.
No examples provided.
tools_redirect_checker ~42
Free public API. Follow a URL's redirect chain and return every hop with status code, response time, final destination.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Starting URL. |
No output schema declared.
No examples provided.
tools_reverse_ip_lookup ~60
Free public API. Reverse-DNS (PTR) lookup for an IP address. Returns one or more hostnames if configured.
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | IPv4 or IPv6 address, e.g. 8.8.8.8. |
No output schema declared.
No examples provided.
tools_spf_record_checker ~63
Free 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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to check SPF for. |
No output schema declared.
No examples provided.
tools_ssl_check ~74
Free 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.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Hostname to check. Optionally with port, e.g. example.com:443. |
No output schema declared.
No examples provided.
tools_subdomain_finder ~42
Free public API. Enumerate subdomains for a target domain via Certificate Transparency logs + DNS resolution.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Apex domain to enumerate. |
No output schema declared.
No examples provided.
tools_txt_record_lookup ~56
Free public API. Fetch all TXT records on a domain, classifying each as SPF, DKIM, DMARC, BIMI, verification token, or general.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to fetch TXT records for. |
No output schema declared.
No examples provided.
tools_website_status_checker ~53
Free public API. Check if a website is up or down. Returns HTTP status, response time, final URL after redirects, basic SSL info.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL to check (include scheme). |
No output schema declared.
No examples provided.
tools_whois_lookup ~50
Free public API. WHOIS / RDAP lookup for a domain — registrar, status, created/updated/expires dates, nameservers.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to look up. |
No output schema declared.
No examples provided.
What is the dev.domainee/domainee MCP server?
dev.domainee/domainee is an MCP server listed in the public MCP registry as dev.domainee/domainee. Custom domains API for SaaS: connect, verify, and manage customer domains, SSL, and DNS. This page covers its hosted endpoint (https://mcp.domainee.dev/mcp).
Is the dev.domainee/domainee MCP server safe to use?
dev.domainee/domainee scores 93 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 dev.domainee/domainee MCP server expose?
dev.domainee/domainee exposes 18 tools: tools_ssl_check, tools_dns_provider_lookup, tools_domain_connect_checker, tools_dns_record_lookup, tools_whois_lookup, and 13 more. Their descriptions and schemas cost roughly 1,254 tokens of context every time the server is loaded.
Does the dev.domainee/domainee MCP server require authentication?
Yes. dev.domainee/domainee asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the dev.domainee/domainee MCP server still maintained?
dev.domainee/domainee is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.