I agree that we will probably move to first-party remote MCP servers in the near future which puts a lot of registries/etc in limbo.
That said, I think there might be a market for MCP servers that do more than the first-party client, it will really depend on what first-party support looks like. Did they implement all of their existing API in MCP or just a few parts?
However, my experience with MCP servers so far (and it’s super early days, I know), has taught me that in a lot of cases it’s better/easier to write your own MCP server/tools. A lot of MCP servers out there are sloppy and/or hard to run/debug. Since most tools are a thin layer over existing API/SDK calls it’s not hard to write (or LLM generate) the needed code which has the added bonus of giving you full control.
Even when an MCP server works 100% and is easy to run, it doesn’t always map 1:1 with the API and so I’ve run into “Yes, you can retrieve data object X but you can’t filter by Y because they didn’t implement that filter in the tool call”.