The .mcp Land Grab: 5 Giants Fighting Over a Suffix Its Inventor Didn't Claim

Here's a strange one from ICANN's 2026 new gTLD round: five heavyweights filed applications for the .mcp top-level domain. Google is in. OpenAI is in. Three registry operators are in. The one company that isn't? Anthropic — the company that invented the Model Context Protocol in the first place.

Let that sit for a second. The protocol's creator applied for exactly two strings: .anthropic and .claude. It never filed for .mcp. That's just the fact; I'm not going to speculate about why. But it makes the five-way fight over the string considerably more interesting.

Who filed for .mcp

According to the application list ICANN published on Reveal Day (October 7, 2026), the five applicants for .mcp are:

• Charleston Road Registry Inc. — Google's registry subsidiary
• OPENAI OPCO, LLC — OpenAI
• Radix Technologies Inc SEZC
• ShortDot (Ireland) Limited
• Tidal Case, LLC

Five applicants for one string means one thing under ICANN rules: a contention set. These applications will go through evaluation and, if more than one survives, an auction. Nobody gets to run .mcp until that process resolves — and based on the current timeline, that won't happen before the first half of 2027.

How contention actually resolves is worth understanding, because it shapes the odds. ICANN's process runs in stages: first string evaluation (technical, financial, and background checks on each applicant), then, for strings with multiple surviving applicants, a "last resort" auction where the highest bidder takes the string. Community objections and government advisory input can also knock applicants out before the auction stage. In past rounds, deep-pocketed applicants have sometimes settled privately — one party paid to walk away — but with Google and OpenAI both in the mix for .mcp, a quiet settlement looks unlikely. This one probably goes to the auction floor.

Worth being precise here: these are applications, not registrations. The public cannot register .mcp domains, and won't be able to for a long time. Anyone telling you otherwise is selling something.

OpenAI filed for 15 strings. Google filed for 39.

The .mcp fight is one battle in a much larger land grab. OpenAI's portfolio in this round covers 15 strings: agent, agi, asi, chatgpt, codex, daybreak, deploy, evals, gpt, mcp, model, oai, openai, skill, and voice. That's a company planting flags across the entire AI-agent namespace.

Google, through Charleston Road Registry, filed for 39 strings. Meta, through Meta Registry Holdings, filed for 18 — including .superintelligence and .agent. The pattern is unmistakable: the biggest tech companies on the planet are treating DNS strings as strategic assets, the same way Tether did when it filed for .usdt and .tether as single-applicant brand TLDs. Tether's play was the opposite of a land grab — one applicant, no contention, a closed brand namespace for the world's largest stablecoin issuer. The .mcp race is the mirror image: five applicants, guaranteed contention, and an open question about who the namespace ultimately serves.

For context on what these fights cost: foreign media reporting (btcfans, alfw.ai) puts the ICANN evaluation fee at $227,000 per application — that's the entry ticket before a single domain is ever sold, and before any auction premium. Google famously paid $25 million at auction for .app in an earlier round, per the same press coverage. These are not casual filings.

.agent is even bloodier: 13 applicants

If you think five contenders is a lot, .agent drew 13 applicants, making it one of the most contested strings in the entire 2026 round. The AI-agent namespace — .agent, .mcp, .skill, .model — is where the heaviest fighting is concentrated. Everyone sees the same future: a world where AI agents need addresses, and whoever controls the suffix controls the namespace.

What happens next: the timeline

• October 7, 2026 — Reveal Day: the full applicant list went public.
• October 8–21, 2026 — Replacement period: applicants can still swap their applied-for strings, so the list can shift.
• November 17, 2026 — String Confirmation Day: the final list locks in.
• H1 2027 and beyond — Evaluation, then auctions for surviving contention sets. No .mcp winner before then.

So the five-way race is real, but the finish line is at least half a year out.

While the giants fight over the suffix, we're already in the Registry

Here's where this gets personal for us. While Google, OpenAI, and three registry operators argue over who gets to *own* .mcp, we've been busy building *on* MCP.

Our two MCP servers are already live in the official MCP Registry:

• io.github.sinianchu9/aiyucha-domain-intelligence (v1.0.4) — domain intelligence queries for AI agents
• io.github.sinianchu9/domainroc-domain-advisor (v1.0.1) — domain advisory for AI agents

Both are listed as active. No contention set, no auction, no $227,000 evaluation fee — just servers that AI agents can actually use today.

There's something almost poetic about it. The suffix will take until 2027 to resolve. The protocol it names is already running, already registered, already serving agents. We didn't wait for permission from a contention set. We shipped.

The giants can have their auction. We'll be in the Registry when it's over — we already are.