MCP registry
Submit public MCP endpoint, descriptor, supported tools, rails, and package metadata.
Agents, clients, and registries can inspect the distribution plan, target surfaces, required files, verification checks, weekly cadence, and success markers for external discovery.
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.