You can find juudd without being handed its address. It is listed in the official MCP registry as com.juudd/juudd, a machine-readable entry that names the connector URL, and the name is ours because we proved we own the domain, not because we asked nicely.
That is the decision. The rest of this post is why the first channel we built was not the one that mattered, how a name gets proven, and the narrow thing the listing does and does not do.
Every other channel starts after the choice
We had already worked out the most official installable thing for each assistant app that has one: a plugin for one, install links for two others, an honest block where an app has nothing. Every row of that list ends the same way. A person has already chosen juudd, and then installs it.
That leaves a question the list never asked. How does an assistant that has never heard of juudd come across it? A person reading a setup guide is not the only reader a connector has, and the second reader does not read guides.
When we looked on 3 September 2026, a search of the official registry for juudd returned an empty list. That was not a decision. Nobody had looked at that row.
A name you prove, not a name you are given
The registry hands out names in two shapes. One starts with io.github. and belongs to whoever signs in with a GitHub login. The other starts with com. followed by a domain, and belongs to whoever can prove they hold the domain.
We took the second. There is no public repository to point the first at, and the domain is the thing this platform actually owns. A personal login is not a durable identity for a product.
The proof is a key pair. The public half sits in a TXT record on the apex of juudd.com, and the registry checks it before it accepts a write under com.juudd. Two details are worth passing on because they fail quietly:
- the record goes on the apex, in the same place a mail-sender record goes, not under a selector name, and the registry's own guide warns that a misplaced record produces a generic signature error that never says where it looked
- when the key is rotated the old record has to be removed, because a stale one is tried first and fails
Three things we left out on purpose
There is no repository field. The schema offers one. We have no public repository, so filling it would mean publishing a URL that answers 404 to everyone who follows it, which is the same mistake as listing a connector address that does not work.
The description is cut, not rewritten. The schema allows 100 characters and the plugin's description is longer. The listing carries the same claim, shortened, so the two cannot drift into saying different things about one product.
The version has to go up on every publish. The registry refuses a repeat. It is kept in the file that describes the connector rather than derived from a package that was never versioned, so the number you see is one a person chose.
The signing key is not in the repository either. It authorises writes to our namespace, which makes it a credential and not a file. Losing it costs a new key and a new record, not the name.
What the listing buys
A machine can now find this connector without a person copying a string. It is the first channel we have that is not a copy and paste, and a copied configuration is exactly the kind whose failures show up on neither end.
It buys nothing else. It is not a listing in Anthropic's connector directory or in ChatGPT's, and it does not shorten the road to either. Those are the larger audiences and neither is reachable by writing code on our side, but treating them as the whole answer is what left the one reachable list empty for as long as it was.
Submitting to aggregators one by one was rejected too. Most of them mirror the official registry, so one publish reaches them, and a form each would be five more places to keep in step.
The rule, once
A connector that only exists in the setup guide can be used only by people who already know it exists. juudd is listed in the official MCP registry under a name proven by DNS, so that a client that has never heard of it can find it unaided. What each tool does is listed in the docs.