Nostr Web Client

Brainstorming how AI agents can contract / negotiate and tip (zap) sub-agents with an MCP that could possibly use Nostr / NWC under the hood. Using an MCP would mean existing agents can have the ability to pay sub-agents without development / changes. The ability to sub-contract could equally apply to us humans too of course.

Has this been conceived already? Any work in progress around this? Any relevant NIPS?

#asknostr #ai #grownostr

René Aaron 2mo ago 💬 2

You are literally describing @getAlby/mcp. Give it a try and share your experience! We're eager to hear about your project and any feedback you might have!

Reply to this note

Please Login to reply.

Discussion

Ben Weeks ⚡ 2mo ago

Will do thank you!

Ben Weeks ⚡ 2mo ago 💬 1

Nice. So the MCP provides knowledge about how to send/receive? Also considered agent discover and job negotiation?

René Aaron 2mo ago 💬 1

Actually you can do a lot more already:

https://github.com/getAlby/mcp/tree/master/src/tools

Not sure about what you mean exactly with agent discover and job negotiation?

If you want to charge agents for using your service you can use

https://github.com/getAlby/paidmcp

The consuming agents will need to be able to pay lightning invoices though 😉

Ben Weeks ⚡ 2mo ago 💬 1

Ah nice. Will look at paidmcp too.

Let’s say Agent A needs a security review of a code base, how does it find Agent B who can do that?

René Aaron 2mo ago 💬 1

Agent B could maybe be just another MCP server? Also look into DVMs on nostr, not sure how far this ecosystem has evolved though.

Ben Weeks ⚡ 2mo ago

The A2A specification actually has a JSON definition for discoverability which could be wrapped into a NIP.

But yeah, could also offer public MCP end points.