Home / MCP registry index / io.github.CodeWever/wever-labs-products
Wever Labs Agent Products
io.github.CodeWever/wever-labs-products in the official MCP registry.
Endpoint https://weverlabs.com/mcp. Source: github.com/CodeWever/wever-labs-mcp-registry.
The registry describes it as: Agent commerce: 27 tools, 10 production services, signed authority, planning, Base USDC x402.
We read its 57 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
wever_delegated-authority wever_agent-paid-workflow wever_unified-agent-checkout wever_diligenceops-paid-run wever_receipt-passport wever_return-package-viewer wever_agent-allowance-console wever_callback-health-monitor wever_agent-work-order-exchange wever_agent-budget-guard wever_agent-sla-rail wever_agent-trust-scorecard wever_payment-authority-inspector wever_x402-payment-gateway wever_ap2-mandate-gateway wever_agent-to-agent-handoff-pack wever_proof-inbox wever_rail-playground wever_agent-escrow-lite wever_agent-invoice-rail wever_agent-permission-ledger wever_agent-work-order-rail wever_agent-decision-packet-rail wever_agent-file-desk-rail wever_mcp-diligence-rail wever_agent-daily-operator-brief wever_proof-relay wever_referral-rail wever_subscription-rail wever_atlas-asset-passport wever_atlas-asset-search wever_treasury-balance wever_treasury-flows wever_workorder-create wever_workorder-fund wever_workorder-accept wever_workorder-deliver wever_workorder-release wever_workorder-dispute wever_payout-create wever_payout-authorize wever_payout-execute wever_payout-status wever_dispute-open wever_dispute-submit-evidence wever_dispute-resolve wever_dispute-status wever_boutique-list-products wever_boutique-product-detail wever_boutique-create-order wever_boutique-record-shipment wever_boutique-confirm-delivery wever_boutique-real-money-acceptance wever_purchase-create-intent wever_purchase-status wever_purchase-execute wever_purchase-dispute
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-codewever-wever-labs-products)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.