2 ms·

I've been building vital-stack.com, a remote MCP server for checking supplement interactions. Claude's desktop app already handles the config side pretty clea

I've been building vital-stack.com, a remote MCP server for checking supplement interactions. Claude's desktop app already handles the config side pretty cleanly for remote servers Name + URL and you're done, no JSON editing required. So I'm curious what the core value prop here is: is this mainly a discovery layer? I.e. users find MCP servers on mcp.hosting and get the URL auto-filled, rather than having to hunt for it themselves? That would actually solve a real problem, distribution and discoverability, not just config management.

jeffyaw 5mo ago
there is a discovery layer (although, not sure if that will be the main draw), and i am vetting that discovery layer to ensure high quality of the mcp servers we have on that discovery layer. the big value prop is only loading the mcp server or set of tools within the mcp server that is required for each prompt. this reduces wasteful context usage and clutter (and wasteful token usage). happy to get vital-stack into the registry. when you're ready message me at support@mcp.hosting