# Sitey — free subdomains (remote · sitey.my)

Claim a working subdomain in one call — A, CNAME and TXT records. No domain to buy, no account.

- Trust score: 68/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `sitey.my`: 68/100 (this document), [markdown](https://verifymcp.io/servers/my-sitey-subdomains/sitey.md), [page](https://verifymcp.io/servers/my-sitey-subdomains/sitey)

## Channel facts

- Endpoint: `https://sitey.my/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http my-sitey-subdomains 'https://sitey.my/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "my-sitey-subdomains": {
      "url": "https://sitey.my/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "my-sitey-subdomains": {
      "type": "http",
      "url": "https://sitey.my/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.my-sitey-subdomains]
url = "https://sitey.my/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "my-sitey-subdomains": {
      "type": "remote",
      "url": "https://sitey.my/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add my-sitey-subdomains --url 'https://sitey.my/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  my-sitey-subdomains:
    url: "https://sitey.my/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "my-sitey-subdomains": {
      "Transport": "http",
      "Url": "https://sitey.my/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add my-sitey-subdomains -t streamable-http -u 'https://sitey.my/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 68, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 67, +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.

### 2026-09-25 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 66, +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.

### 2026-09-22 (score 65, +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.

### 2026-09-20 (score 64, +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.

### 2026-09-17 (score 63, +1)

- [security] 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
- [cosmetic] “create_subdomain” reworded the description of “type”
- [cosmetic] “create_subdomain” reworded the description of “value”

### 2026-09-16 (score 62, −1)

- [security] 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
- [functional regression] Schema quality: pass → fail
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “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”

## MCP tools (9)

### `list_domains` (~42 tokens)

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.

### `check_availability` (~69 tokens)

Check if a specific subdomain name is available for registration under a given domain. Returns true if the name is free to claim.

Input parameters:

- `domain` (string, required): Root domain (e.g. 'sitey.my')
- `subdomain` (string, required): Subdomain name (e.g. 'demo')

### `create_subdomain` (~335 tokens)

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.

Input parameters:

- `domain` (string, required): 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, required): Subdomain name (e.g. 'demo')
- `type` (string, required): Record type. REDIRECT answers every visit with a 301 to the URL in value.
- `value` (string, required): 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).

### `list_subdomains` (~155 tokens)

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.

Input parameters:

- `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…

### `renew_subdomain` (~192 tokens)

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.

Input parameters:

- `domain` (string, required): 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, required): Subdomain name (e.g. 'demo')

### `update_subdomain` (~172 tokens)

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.

Input parameters:

- `domain` (string, required): 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, required): Subdomain name (e.g. 'demo')
- `value` (string, required): New record value

### `delete_subdomain` (~126 tokens)

Permanently delete a subdomain DNS record you own. The subdomain will stop resolving immediately.

Input parameters:

- `domain` (string, required): 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, required): Subdomain name (e.g. 'demo')

### `create_txt_record` (~252 tokens)

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.

Input parameters:

- `domain` (string, required): Root domain (e.g. 'sitey.my')
- `host_prefix` (string, required): 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, required): Subdomain name (e.g. 'demo')
- `value` (string, required): TXT record value (the verification token)

### `delete_txt_record` (~138 tokens)

Delete a TXT verification record from a subdomain you own.

Input parameters:

- `domain` (string, required): Root domain (e.g. 'sitey.my')
- `host_prefix` (string, required): 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, required): Subdomain name (e.g. 'demo')

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/my-sitey-subdomains/sitey#diagnostics

## Score history

- 2026-09-28: 68
- 2026-09-27: 67
- 2026-09-26: 67
- 2026-09-25: 66
- 2026-09-24: 66
- 2026-09-23: 65
- 2026-09-22: 65
- 2026-09-21: 64
- 2026-09-20: 64
- 2026-09-19: 63
- 2026-09-18: 63
- 2026-09-17: 63
- 2026-09-16: 62
- 2026-09-15: 63

## Common questions

### 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.

## Links

- Remote endpoint: https://sitey.my/mcp
- Repository: https://github.com/jaejeonglee/sitey-free-domain
- Website: https://sitey.my/
- Changelog RSS feed: https://verifymcp.io/servers/my-sitey-subdomains/sitey.xml
- Changelog JSON feed: https://verifymcp.io/servers/my-sitey-subdomains/sitey.json
- HTML version of this page: https://verifymcp.io/servers/my-sitey-subdomains/sitey