Ahh it's cool, but built specifically for MCPs
Discussion
Yes, MCP is the underlying protocol. You can do with this anything that a DVM can do and more. At the beginning, I started following the same pattern introduced by DVMs, with one kind for requests and another for responses, but I switched to a more simple approach using just one kind as a 'socket'. Its also more simple to implement as you code the functionality as mcp server and then you use contextvm for the nostr transport. Feel free to ask anything 🤙
Hmm I'm specifically looking for a replacement for http over nostr so we can build backends and run them without needing a public IP, I guess I'll have to build it myself.
it's the Evolution of DVMCP