How exactly does one add a new registry using the Web UI?

[S4GU4R0]

https://raw.githubusercontent.com/fleuristes/app-registry/refs/heads/main/apps.json is the url for the Fleur registry's json for example. It works; it's not down. And yet I still get: No results — fleurmcp-com: Failed to search servers: failed to search registry: failed to fetch servers from fleurmcp-com: failed to fetch servers: registry query returned 404 Not Found in the UI. The official registry doesn't work either. I tried adding LobeHub.

It seems like the app is appending routes and queries to the url added even though it says it needs a json response and each registry uses different routing?

Has anyone successfully added routing via the web UI?

[Dumbris]

You found a real bug, and your diagnosis was exactly right — MCPProxy was appending its own route to whatever URL you pasted. Sorry it took so long to get a reply.

Here is what was happening. deriveServersURL glued /v0.1/servers onto any URL that did not already contain /servers, so your URL was fetched as:

https://raw.githubusercontent.com/fleuristes/app-registry/refs/heads/main/apps.json/v0.1/servers

which 404s, while the URL you actually pasted returns 200. On top of that, every added registry was assumed to speak the official modelcontextprotocol/registry v0.1 protocol, so official query params (version/limit/search/cursor) were appended too — and the failure only surfaced later, at search time, as the opaque error you saw.

Fixed in #846: the URL you paste is used as-is, and it is now fetched when you add it and checked. If it is not a v0.1 registry you get a clear refusal right there, naming the reason, instead of a registry that saves fine and then 404s on every search.

About Fleur specifically — the honest answer is that it will not work, and not because of us. Fleur is abandoned:

• apps.json has not changed since 2025-03-29 (~16 months).
• The Fleur client repo has not had a commit on main since the same day; last release was v0.2.18 in March 2025.
• 15 app-submission PRs are open and unmerged, including ones from this month — nobody is merging them.
• fleurmcp.com is now a generic WordPress/Elementor marketing template — no download, no GitHub link.
• There is no /v0.1/servers mirror of the catalog anywhere, and no migration to the official protocol was ever announced (the official MCP registry launched in September 2025, months after Fleur went quiet).

You are right that we used to ship Fleur as a built-in registry — we removed it in #572 when we standardized on the official protocol, and we did not give you a way to add it back. That is on us. But rather than reintroduce a bespoke parser for a dead 12-app catalog, we are keeping to the one protocol: modelcontextprotocol/registry v0.1. Everything in the Fleur list except mcp-hn and @getrember/mcp is already in the official registry, and four of its entries point at npm packages that are now formally deprecated (server-github, server-slack, server-puppeteer, server-brave-search).

The official registry does work — I checked https://registry.modelcontextprotocol.io/v0.1/servers and it returns 200 with ~9.6k servers, and it ships enabled by default. If it is showing you no results, that is a separate bug and I would genuinely like to see it: could you open an issue with what you searched for and what mcpproxy registry list prints?

For LobeHub: it does not publish a v0.1 registry endpoint either, so it cannot be added today. If you know of one that does, paste the URL and it should just work after #846.