io.github.CodeWever/wever-labs
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@io.github.CodeWever/wever-labsquote movement fee for 5MB transfer"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Wever Labs Agent Products
Public publication metadata for the hosted Wever Labs MCP server.
Agent commerce rails on weverlabs.com: 27 MCP tools, 10 production services including delegated authority with signed mandates, five planning and settlement tools, and four x402 USDC-paid endpoints on Base mainnet. Four Labs API computations free; MCP tools include 10 free calls per wallet per 30 days.
The catalog lists 10 production services and 17 explicitly disclosed unavailable historical demo backends. The five planning tools prepare or suggest results; they do not execute payments or delivery. Delegated authority creates durable work-order records under signed mandates and credential-bound grants; it does not execute the requested work or authorize payment. The four paid endpoints use x402 with USDC on Base mainnet. Their wallet free tier is shared across those four endpoints, not ten calls for every tool.
Publication field | Value |
Registry name |
|
Title | Wever Labs Agent Products |
Version |
|
Transport | Streamable HTTP |
Remote endpoint | |
Website | |
Repository |
The version was read from the live endpoint's MCP initialize response. Recheck it before a later publication.
The official 2025-12-11 schema limits description to 100 characters. server.json therefore uses a short summary; the longer public description is retained above.
This server is remote-only. server.json has no packages array. package.json is minimal fallback metadata, not an installed MCP server or a published npm artifact. No package publication is needed for the current remote descriptor.
David performs publisher login and publication using PUBLISHING_RUNBOOK.md. After publication, follow VERIFY_CHECKLIST.md. Committing this repository does not publish an Official MCP Registry listing.
No secrets, keys, credentials or private implementation code belong in this repository.
This server cannot be deployed
Maintenance
Related MCP Connectors
Agentic rails for complex workflows with receipts, fees, and MCP tool access.
Workflow diagnostics, capability routing, and x402 settlement for MCP-compatible agents.
Self-facilitated x402/MCP payments for hosted endpoints, rail proofs, receipts, and agents.
Public MCP for agent verification, work discovery and governed interoperability.
Related MCP Servers
- AlicenseNot gradedqualityFmaintenanceOrchestrates persistent task graphs and enforces approval policies for MCP-driven agent workflows, coordinating with Agents Gateway for execution.MIT
- FlicenseNot gradedqualityDmaintenanceProvides MCP tools to enforce spend policies (allow, deny, step-up, allowlist) on agent wallets with an immutable audit trail.-
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible LLM clients to execute server-verified agent workflows, with enforced transitions, invocation caps, and signed audit trails.MIT
- FlicenseNot gradedqualityBmaintenanceEnables authenticated MCP tools for planning commercial routes with fail-closed economic boundaries, plus marketplace discovery, matching, and agent interaction capabilities.-