DNSSEC included
Every zone is automatically signed with NSEC3. Validation-safe out of the box — no key management, no expiry surprises.
Free · DNSSEC signed · MCP native · Live in minutes
Ask your AI assistant — it claims your free subdomain, sets the records, and hands you the keys. No signup forms, no dashboards — just a conversation.
Security and convenience are the defaults, not add-ons.
Every zone is automatically signed with NSEC3. Validation-safe out of the box — no key management, no expiry surprises.
MCP is an open protocol — bring the client you use today and whatever you prefer tomorrow. No vendor lock on either side.
One server URL from your operator, added to your favourite MCP client — Codex, Claude Code, Cursor, OpenCode or anything that speaks MCP.
"Claim the subdomain iris for me." Your assistant checks availability, verifies you, and does the rest — no forms, no dashboards.
A, AAAA, CNAME and TXT — set, update or remove them by simply asking. Need more? Delegate the whole subdomain to a third-party nameserver of your choice.
Delegate your whole subdomain to third-party nameservers whenever you outgrow the operator's zone — one sentence, handled.
You get a one-time login token and an optional recovery key, shown exactly once. The server never echoes them back.
From idea to resolving name in minutes.
Your operator gives you one URL. Add it to your MCP client once — Codex, Claude Code, Cursor, OpenCode or any other.
"Claim the subdomain iris for me" is all it takes. Your assistant checks availability and runs a one-time verification.
You receive a one-time login token — keep it safe. Later sessions reuse it (or your recovery key) to manage records and delegation.
Yes — claiming and using your subdomain costs nothing. Free is the whole point, not a trial.
MCP (Model Context Protocol) is the standard way AI clients connect to external tools. mcp-semeion is a remote MCP server: once your client knows its URL, your assistant can claim and manage subdomains for you — you never call it directly.
Anything that speaks MCP: Codex, Claude Code, Cursor, OpenCode and most others. Add it as a remote server with the URL your operator gave you — the connect dialog has copy-paste snippets.
mcps.my is a specialized subdomain registry designed for the Model Context Protocol ecosystem and beyond. We provide developers with standardized subdomains to act as unique identifiers for their distributed services.
Our subdomains are ideal for:
Then it's gone — subdomains are first come, first served. Pick another label; short and memorable beats clever and long.
Yes. Set NS records for your subdomain to delegate it elsewhere. If the other operator doesn't support DNSSEC, simply don't publish a DS record — the delegation is then provably insecure and keeps resolving everywhere.
Your records are yours — set, change or delegate them at any time. The name itself isn't transferable, but you can release it when you no longer need it. No lock-in.
Set up a recovery key while you still have access — it reconnects you to the same subdomain. Both secrets are shown exactly once; the server never echoes them back.
Nothing, basically. This page is static — no cookies, no trackers, no analytics — and DNS gets answered without keeping a log of who asked. The registry holds your records and your login secrets, and that's the whole file.
Yes — and the EU agrees that's worth saying plainly. Copy, canvas and code, all of it came out of AI sessions, directed by an AI agent from first prompt to final pixel. Welcome to the future. Want one like it? Ask your code agent — that's how this one was made.
No. Keys are generated, rotated and published automatically, and every answer your visitors receive is cryptographically signed. It just works.
It's a subdomain. It's going to give your MCP server a professional-looking URL. It won't solve your relationship problems or fix your broken code. Next question.
Curated by Ox Alpha — in his free time, as all lasting things are.
Your name is still available — probably.
Your operator gives you a server URL. Add mcp-semeion as a remote MCP server with that URL — pick your client:
Run this in your terminal, or add it to ~/.codex/config.toml:
codex mcp add mcp-semeion --url https://semeion.mcps.my/mcp[mcp_servers.mcp-semeion]
url = "https://semeion.mcps.my/mcp"Run this in your terminal, or add it to .mcp.json:
claude mcp add --transport http mcp-semeion https://semeion.mcps.my/mcp{ "mcpServers": { "mcp-semeion": { "url": "https://semeion.mcps.my/mcp" } } }Add it to the .mcp.json of your project:
{ "mcpServers": { "mcp-semeion": { "url": "https://semeion.mcps.my/mcp" } } }Add it to opencode.json — project file or ~/.config/opencode/opencode.json:
{
"mcp": {
"mcp-semeion": {
"type": "remote",
"url": "https://semeion.mcps.my/mcp",
"enabled": true,
"oauth": false
}
}
}Add mcp-semeion as a remote / URL-type MCP server and paste the URL your operator gave you — most clients have an "Add MCP server → URL" option. Generic config:
{ "mcpServers": { "mcp-semeion": { "url": "https://semeion.mcps.my/mcp" } } }After adding, restart your client and confirm mcp-semeion appears in its connected-server list.
Then just ask in plain language — "claim the subdomain iris for me", "point my subdomain at 1.2.3.4".
First time, your assistant runs a quick verification and hands you a one-time login token — shown once, so save it. A recovery key can be set up for later sessions.