Sitey — free subdomains
REMOTE · SITEY.MY · SCANNED SEP 28
Claim a working subdomain in one call — A, CNAME and TXT records. No domain to buy, no account.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1481 tokens (~164/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_subdomain" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 9 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 Sitey — free subdomains MCP server?
Sitey — free subdomains is a hosted endpoint at https://sitey.my/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 · sitey.my
claude mcp add --transport http my-sitey-subdomains 'https://sitey.my/mcp'
{
"mcpServers": {
"my-sitey-subdomains": {
"url": "https://sitey.my/mcp"
}
}
} {
"servers": {
"my-sitey-subdomains": {
"type": "http",
"url": "https://sitey.my/mcp"
}
}
} [mcp_servers.my-sitey-subdomains] url = "https://sitey.my/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"my-sitey-subdomains": {
"type": "remote",
"url": "https://sitey.my/mcp",
"enabled": true
}
}
} openclaw mcp add my-sitey-subdomains --url 'https://sitey.my/mcp' --transport streamable-http
mcp_servers:
my-sitey-subdomains:
url: "https://sitey.my/mcp" {
"McpServers": {
"my-sitey-subdomains": {
"Transport": "http",
"Url": "https://sitey.my/mcp"
}
}
} assistant mcp add my-sitey-subdomains -t streamable-http -u 'https://sitey.my/mcp'
{
"mcpServers": {
"my-sitey-subdomains": {
"type": "http",
"url": "https://sitey.my/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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 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
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
- Tool “create_subdomain” rewrote its description, which is the text the model reads security
- Tool “list_subdomains” rewrote its description, which is the text the model reads security
- “create_subdomain” reworded the description of “type” cosmetic
- “create_subdomain” reworded the description of “value” cosmetic
- 16 Sept 26 −1
- The server changed its declared name: sitey.one → sitey security
- Tool “create_subdomain” rewrote its description, which is the text the model reads security
- Tool “list_domains” rewrote its description, which is the text the model reads security
- Tool “list_subdomains” rewrote its description, which is the text the model reads security
- Tool “update_subdomain” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- “create_subdomain” added an optional parameter “owner_token” cosmetic
- “create_txt_record” added an optional parameter “owner_token” cosmetic
- “delete_subdomain” added an optional parameter “owner_token” cosmetic
- “delete_txt_record” added an optional parameter “owner_token” cosmetic
- “list_subdomains” added an optional parameter “owner_token” cosmetic
- “renew_subdomain” added an optional parameter “owner_token” cosmetic
- “update_subdomain” added an optional parameter “owner_token” cosmetic
- “check_availability” reworded the description of “domain” cosmetic
- “create_subdomain” reworded the description of “domain” cosmetic
- “create_txt_record” reworded the description of “domain” cosmetic
- “delete_subdomain” reworded the description of “domain” cosmetic
- “delete_txt_record” reworded the description of “domain” cosmetic
- “renew_subdomain” reworded the description of “domain” cosmetic
- “update_subdomain” reworded the description of “domain” cosmetic
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 28 Sept 2026 · Probed https://sitey.my/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sitey.my | CN=YE1,O=Let's Encrypt,C=US | 28 Aug 2026 | 26 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 633d2a150e34dba19d4aaeb8e815f4ab23b |
| SANs: sitey.my | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sitey.my. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| my. | present | 47187 | 13 | Verified |
| sitey.my. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sitey.my/mcp | Verified | 200 | |
| http (plaintext) | http://sitey.my/mcp | HTTPS enforced | 308 | https://sitey.my/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 →
check_availability ~69
Check if a specific subdomain name is available for registration under a given domain. Returns true if the name is free to claim.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Root domain (e.g. 'sitey.my') |
| subdomain | string | yes | Subdomain name (e.g. 'demo') |
No output schema declared.
No examples provided.
create_subdomain ~335
Create a new DNS record for a subdomain. Supports A records (IP address), CNAME records (hostname) and REDIRECT records (an https:// URL — visitors to the name are sent there with a 301). Example: create demo.sitey.my pointing to 1.2.3.4. No account, API key or signup is needed. The target does not have to be serving yet: claim the name first and deploy to it second if that is your order. The result carries reachable:false when nothing answered, and the record is created either way. If you send no owner_token, the result carries a new one under 'owner_token' — save it, it is shown once and is the only way to change or delete this record later.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Root domain (e.g. 'sitey.my') |
| owner_token | string | – | The owner token you were given when you created the record (starts with anon_). Omit it only if you have an API key, or if the record predates tokens and was claimed from this same IP address. Creati… |
| subdomain | string | yes | Subdomain name (e.g. 'demo') |
| type | string | yes | Record type. REDIRECT answers every visit with a 301 to the URL in value. |
| value | string | yes | Record value: an IPv4 address for A, a hostname for CNAME, an absolute https:// URL for REDIRECT (http:// is refused, and so is a URL under one of this service's own roots). |
No output schema declared.
No examples provided.
create_txt_record ~252
Create or update a TXT record for domain verification. Used for services like Vercel (_vercel) and Netlify that require DNS-based ownership proof. The record is placed at the root domain under the prefix you give (e.g. _vercel.sitey.my), alongside the other owners' values — that is the name Vercel reads for a subdomain of sitey.my.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Root domain (e.g. 'sitey.my') |
| host_prefix | string | yes | TXT record host prefix (e.g. '_vercel' for Vercel verification) |
| owner_token | string | – | The owner token you were given when you created the record (starts with anon_). Omit it only if you have an API key, or if the record predates tokens and was claimed from this same IP address. Creati… |
| root_level | boolean | – | No longer supported — TXT records are always written at the root domain. Passing true returns an error. |
| subdomain | string | yes | Subdomain name (e.g. 'demo') |
| value | string | yes | TXT record value (the verification token) |
No output schema declared.
No examples provided.
delete_subdomain ~126
Permanently delete a subdomain DNS record you own. The subdomain will stop resolving immediately.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Root domain (e.g. 'sitey.my') |
| owner_token | string | – | The owner token you were given when you created the record (starts with anon_). Omit it only if you have an API key, or if the record predates tokens and was claimed from this same IP address. Creati… |
| subdomain | string | yes | Subdomain name (e.g. 'demo') |
No output schema declared.
No examples provided.
delete_txt_record ~138
Delete a TXT verification record from a subdomain you own.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Root domain (e.g. 'sitey.my') |
| host_prefix | string | yes | TXT record host prefix (e.g. '_vercel') |
| owner_token | string | – | The owner token you were given when you created the record (starts with anon_). Omit it only if you have an API key, or if the record predates tokens and was claimed from this same IP address. Creati… |
| subdomain | string | yes | Subdomain name (e.g. 'demo') |
No output schema declared.
No examples provided.
list_domains ~42
List available root domains (e.g. sitey.my, sitey.one) that you can create subdomains under. Call this first to know which domains are available.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_subdomains ~155
List all subdomains you own. Returns subdomain name, domain, record type, value, and creation date. A REDIRECT record also carries hits: how many visits it has answered in total, how many this calendar month, and when the last one was. Filtered by your API key, or by the owner_token you pass, or — for records made before tokens existed — by your IP address.
| Name | Type | Req | Description |
|---|---|---|---|
| owner_token | string | – | The owner token you were given when you created the record (starts with anon_). Omit it only if you have an API key, or if the record predates tokens and was claimed from this same IP address. Creati… |
No output schema declared.
No examples provided.
renew_subdomain ~192
Extend a subdomain you own before it expires. Subdomains are lent for a period, not given: agent-created records last one month and user records three. Nothing emails an agent, so read expires_at from list_subdomains and call this before that date. One call resets the clock from today. Renewal only opens in the last two weeks before expires_at — an earlier call is refused and tells you the date it opens.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Root domain (e.g. 'sitey.my') |
| owner_token | string | – | The owner token you were given when you created the record (starts with anon_). Omit it only if you have an API key, or if the record predates tokens and was claimed from this same IP address. Creati… |
| subdomain | string | yes | Subdomain name (e.g. 'demo') |
No output schema declared.
No examples provided.
update_subdomain ~172
Update the DNS record value of a subdomain you own. For example, change the IP address that demo.sitey.my points to. The new target does not have to be serving yet; the result carries reachable:false when nothing answered, and the record is moved either way.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Root domain (e.g. 'sitey.my') |
| owner_token | string | – | The owner token you were given when you created the record (starts with anon_). Omit it only if you have an API key, or if the record predates tokens and was claimed from this same IP address. Creati… |
| subdomain | string | yes | Subdomain name (e.g. 'demo') |
| value | string | yes | New record value |
No output schema declared.
No examples provided.
What is the Sitey — free subdomains MCP server?
Sitey — free subdomains is an MCP server listed in the public MCP registry as my.sitey/subdomains. Claim a working subdomain in one call, A, CNAME and TXT records. No domain to buy, no account. This page covers its hosted endpoint (https://sitey.my/mcp).
Is the Sitey — free subdomains MCP server safe to use?
Sitey — free subdomains scores 68 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 Sitey — free subdomains MCP server expose?
Sitey — free subdomains exposes 9 tools: list_domains, check_availability, create_subdomain, list_subdomains, renew_subdomain, and 4 more. Their descriptions and schemas cost roughly 1,481 tokens of context every time the server is loaded.
Does the Sitey — free subdomains MCP server require authentication?
No. We connected to Sitey — free subdomains without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Sitey — free subdomains MCP server still maintained?
Sitey — free subdomains is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.