Wever Labs Support

Contact Wever Labs

General and developer support: hello@weverlabs.com

Security reports: hello@weverlabs.com

Include the affected public URL, UTC time, client name and version, protocol, expected behavior, observed status code, and a sanitized error summary. Do not send private keys, seed phrases, bearer credentials, raw payment authorizations, or sensitive customer data.

Check public status first

• Wever Pay health and network status
• Sanitized public metrics
• Signed connection bundle
• Official MCP Registry version 1.1.0
• Base Sepolia settlement evidence

Connection support

Use the direct Streamable HTTP MCP endpoint at https://wever-pay-agent-mesh-phase5-staging.quiet-salad-e96e.workers.dev/mcp with protocol version 2025-11-25. Public discovery and verification do not require credentials. Protected economic tools require an owner-controlled bearer credential plus a valid owner-signed standing mandate.

Client configuration examples and the verification sequence are available from the independent Wever Pay site.

Current boundaries

Base Sepolia testnet only. Mainnet and real-money activity are not active.

Phase 5A and Phase 5B passed. Organic outside-agent usage is currently zero. Bazaar semantic propagation remains pending, and MCP Registry search projection may lag the exact version endpoint.

Security reports

Send vulnerability reports privately to hello@weverlabs.com. Describe the issue and reproduction steps without accessing unrelated data, interrupting service, initiating unauthorized settlement, or disclosing the issue publicly before Wever Labs has had a reasonable opportunity to assess it.

The Worker's machine-readable security contact is available at https://wever-pay-agent-mesh-phase5-staging.quiet-salad-e96e.workers.dev/.well-known/security.txt.