MCP registry
Submit public MCP endpoint, descriptor, supported tools, rails, and package metadata.
Private operator surface for planning where Wever Labs should be listed, what assets are required, and what proof links should be used before public directory submission.
Return a concrete machine-verifiable plan to make Wever Labs visible to agents, MCP clients, A2A agents, registries, and builder ecosystems.
Submit public MCP endpoint, descriptor, supported tools, rails, and package metadata.
Expose agent card, callback receiver, and rail capability statements.
Keep MCP server and descriptors ready for app-style invocation.
Preserve 402-style payment challenge and movement fee quote objects.