UluP Nexus is the public index of indie projects that you explore on a node map and that AI assistants can query through an MCP server. Since last night that server is also in the official MCP Registry, under the name `com.ulupstudio/nexus`. This post explains what that means, what it doesn't, and how I did it, mistake included.
What the MCP Registry is
It's a public list of MCP servers. It holds metadata (name, description, address), not code. Anyone building an MCP client, or another directory, can read it to find out which servers exist. Today the registry is in preview: its own documentation warns that the format may change.
What the Nexus listing contains
- the name `com.ulupstudio/nexus`, version 1.0.0;
- a description: search an index of indie software and games, verified by hand, by keyword, category, language and pricing model;
- the server address, `https://nexus.ulupstudio.com/mcp`, over HTTP;
- the website, `nexus.ulupstudio.com`.
The server is public and needs no account. Its status in the registry is active.
How I published it
1. The name. To use a domain-based name (`com.ulupstudio/…`) the registry wants proof that the domain is mine. The alternative was a GitHub-based name, but the domain is cleaner. 2. First attempt, failed. I put a verification file at `/.well-known/mcp-registry-auth` on the website. The registry answered with a 308 error: `ulupstudio.com` redirects visitors to `www.ulupstudio.com`, and the registry doesn't follow redirects, so it never saw the file. 3. The fix. I used DNS verification instead: a TXT record with the public key on the domain, which doesn't go through the website and so isn't affected by the redirect. 4. Publishing. A `server.json` file and the `mcp-publisher publish` command. Then I checked the registry's API to confirm the listing showed up with status active.
About a quarter of an hour in total. The slow part was the redirect: if your site redirects from one address to the other, pick DNS from the start.
What it means and what it doesn't
- It means that people searching the registry, or directories that copy it, can find Nexus.
- It isn't a quality stamp. As the documentation describes it, the registry checks that the name belongs to whoever publishes it; it doesn't assess the server.
- It doesn't mean assistants will use it on their own. A person has to connect Nexus as a connector, and few people do today.
- It doesn't change the number of projects: there are 6, all mine.
What's still missing
These things are planned, but not there yet:
- Category pages with their own address, and more specific text for each project.
- An alternative to the meta tag for verification, for people who can't edit their site's HTML.
- More projects, added only with their authors' consent, starting from a single category.
How you can be part of it
- Add your project at nexus.ulupstudio.com/submit: one address, a prefilled listing, one line on your homepage, approved by hand.
- Connect an assistant with `https://nexus.ulupstudio.com/mcp`, explained on For AI.
- Tell me what doesn't work or what's missing. The first readers' comments already changed three things in the first update.
*Status: UluP Nexus is live at nexus.ulupstudio.com and its MCP server is in the official MCP Registry as com.ulupstudio/nexus. It holds 6 projects, all by UluP Studio. Other projects are added only with their authors' consent.*