Show HN: mcp.hosting – The easiest way to install MCP servers | Hacker News Reader

Show HN: mcp.hosting – The easiest way to install MCP servers

mcp.hosting

4 pointsjeffyaw4 comments

Hey HN, adding new mcp servers by hand-editing JSON across Claude Code, Claude Desktop, and Cursor is annoying. So I built mcp.hosting, the easiest way to install MCP servers.

Add mcp servers by clicking to add from the Explore page. Or click on github repo badges. Or manually add as well. It's easy to add a bunch in your online account and then they're immediately available in your mcp client of choice. There is also Smart Routing built in to make sure it's fast and uses the best mcp tool for the job.

Free tier covers 3 active servers, Pro is $9/mo for unlimited, and self-host is available if you want to run the whole stack.

Happy to answer questions about the compliance suite (coming soon), the registry, or the stack (Fastify + Postgres + Caddy on EKS).

Open articleView on HN

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.

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

Quick question on the Smart Routing layer: when an upstream MCP server returns HTTP 402 (x402 payment required), does your proxy pass that status through so the client can run its own payment handler, or is it caught and flattened into a generic error upstream of Claude Code? The answer decides whether paid third-party MCP servers can negotiate through mcp.hosting at all, or whether everything has to be prepaid inside the account.

Good question, the answer is simpler than the setup suggests, because for most servers mcp.hosting isn't actually in the data path.

When you install a server, your client (Claude Code, Cursor, etc.) ends up with the upstream's endpoint written into its own config and talks to it directly. No proxy, no status rewriting, x402 is whatever the upstream sends, unmodified, and your client-side payment handler runs natively.

So paid third-party MCP servers can absolutely negotiate through mcp.hosting-installed configs, and the hosted-proxy path doesn't break x402.

Reply on news.ycombinator.com