Gzuuus on Nostr: Here are some updates on the progress of DVMCP. Last week, I implemented all the new ...

Here are some updates on the progress of DVMCP. Last week, I implemented all the new functionality into the discovery package, which can now handle more capabilities from MCP servers, including tools, resources and prompts. For those unfamiliar with the discovery package, it essentially acts as a client-side MCP server, discovering DVMCP servers on Nostr and making them accessible for use.

The newly introduced capabilities, resources, and prompts open up a wealth of possibilities as they are quite versatile and can facilitate interesting use cases such as agentic workflows and remote control through MCP. The best thing about all this is that Nostr is the transport layer, adding significant value and filling gaps in the MCP protocol, such as providing robust cryptographic authentication and enabling payments. We're also using WebSockets instead of SSE or more exotic solutions such as 'streamable HTTP', as WebSockets feel like a more natural fit for a protocol primarily designed for stdio.

Now it's time to polish some details. Prompts also introduce the 'auto-complete' feature, which I hadn't initially accounted for. Apart from that, the next step is to update dvmcp.fun to the new specification so that you can discover, test and use DVMCP servers on Nostr. I think it's reasonable to expect another two weeks until I can make this happen.

I'll share new updates soon, stay tuned! 🚀