MCP Gateway and Registry • Hacker News Board

Re: MCP Gateway and Registry

#11

Post by tuananh » Mon, Aug 25, 2025, 7:42 AM UTC

I built hyper-mcp[1] as side project with each MCP as a WASM plugin.

The idea is each plugin runs in their own wasm vm with limited network/file system access. Plugins are written in any language, as long as they can compile to WASM and publish to OCI registry (signed & verified with sigstore)

Recently, Microsoft released their own version of hyper-mcp named Wassete[2]

Ideally, I want to make it like a gateway with more security & governance features in this layer.

[1]: https://github.com/tuananh/hyper-mcp [2]: https://github.com/microsoft/wassette

Re: MCP Gateway and Registry

#12

Post by fullstackwife » Mon, Aug 25, 2025, 8:12 AM UTC

tuananh wrote: post #11

I built hyper-mcp[1] as side project with each MCP as a WASM plugin. The idea is each plugin runs in their own wasm vm with limited network/file system access. Plugins are written in any language, as long as they can compile to WASM and publish to OCI registry (signed & verified with sigstore) Recently, Microsoft released their own version of hyper-mcp named Wassete[2] Ideally, I want to make it like a gateway with m…

For many years we were fine with running DLLs, Java .class deps, npm modules, brew packages etc. why do you think we need so much isolation for left-pad class mcp tools?

Re: MCP Gateway and Registry

#13

Post by manojlds » Mon, Aug 25, 2025, 8:24 AM UTC

jumploops wrote: post #3

Does anyone use MCP within their product, or is the MCP ecosystem entirely focused on enabling new workflows within an existing chat/agent framework (a la Cursor or Claude code)? Assuming the latter, are there any viable non-developer MCP clients?

Claude.ai and Claude Desktop are the main non developer MCP clients.

ChatGPT has limited MCP support as of now (read only use cases with deep research) but the expectation is that full MCP support might be dropping soon.

Re: MCP Gateway and Registry

#14

Post by dalemhurley » Mon, Aug 25, 2025, 9:02 AM UTC

jumploops wrote: post #3

Does anyone use MCP within their product, or is the MCP ecosystem entirely focused on enabling new workflows within an existing chat/agent framework (a la Cursor or Claude code)? Assuming the latter, are there any viable non-developer MCP clients?

MCP is one of the most powerful ways for app-to-app communication. Instead of having to hardcode against an API, the LLM can just request the latest API spec and request what it needs. As a developer you could completely skip the LLM.

MCP, is just a really good M2M documentation.

Re: MCP Gateway and Registry

#15

Post by pmig » Mon, Aug 25, 2025, 9:02 AM UTC

These kind of gateways showcase that larger organizations will equip their employees with tools the same way employees are currently granted access to specific SaaS applications.

One of the bigger challenges we are currently observing is missing authorization for MCP servers.

We actually also just released a mcp-gateway[1] initially focusing on adding OAuth authorization to streamable HTTP MCP servers.

[1]: https://github.com/hyprmcp/mcp-gateway

Re: MCP Gateway and Registry

#16

Post by pmig » Mon, Aug 25, 2025, 9:03 AM UTC

tuananh wrote: post #11

I built hyper-mcp[1] as side project with each MCP as a WASM plugin. The idea is each plugin runs in their own wasm vm with limited network/file system access. Plugins are written in any language, as long as they can compile to WASM and publish to OCI registry (signed & verified with sigstore) Recently, Microsoft released their own version of hyper-mcp named Wassete[2] Ideally, I want to make it like a gateway with m…

Interesting we also just released our mcp gateway project under the name Hypr MCP[1].

[1]: https://github.com/hyprmcp/mcp-gateway

Re: MCP Gateway and Registry

#17

Post by pylotlight » Mon, Aug 25, 2025, 9:19 AM UTC

jumploops wrote: post #3

Does anyone use MCP within their product, or is the MCP ecosystem entirely focused on enabling new workflows within an existing chat/agent framework (a la Cursor or Claude code)? Assuming the latter, are there any viable non-developer MCP clients?

I was really hoping this would take off. https://github.com/universal-tool-calling-protocol

Re: MCP Gateway and Registry

#18

Post by pylotlight » Mon, Aug 25, 2025, 9:20 AM UTC

If only IBM supported something more structured and sensible than the mess that is MCP: https://github.com/universal-tool-calling-protocol

Re: MCP Gateway and Registry

#19

Post by pmig » Mon, Aug 25, 2025, 9:31 AM UTC

manojlds wrote: post #13

jumploops wrote: post #3

Does anyone use MCP within their product, or is the MCP ecosystem entirely focused on enabling new workflows within an existing chat/agent framework (a la Cursor or Claude code)? Assuming the latter, are there any viable non-developer MCP clients?

Claude.ai and Claude Desktop are the main non developer MCP clients. ChatGPT has limited MCP support as of now (read only use cases with deep research) but the expectation is that full MCP support might be dropping soon.

ChatGPT launching MCP support would dramatically improve adoption, but MCP server installation must become way easier to find non coding use case adoption.

Re: MCP Gateway and Registry

#20

Post by sublimefire » Mon, Aug 25, 2025, 9:35 AM UTC

thecopy wrote: post #2

Many Gateways popping up now, im also doing my own gateway ( https://mcp-boss.com/ ) but im starting to worry its hard to compete with Docker, Microsoft, now IBM...

mcp is not the future IMO, agent2agent is, e.g. a2aproject/A2A

The problem with MCP is that it cannot reliably scale, so some abstraction is helpful, i.e. separate “agent” with its own instructions and a predefined set of tools.