Wever Labs Agentic Rails
Rieles MCP para ejecuciones de agentes respaldadas por pruebas, recibos, callbacks y paquetes de transferencia.
Documentación
Wever Labs Agentic Rails
Wever Labs Agentic Rails provides MCP-accessible commercial trust rails for agent work.
Agents and developers can inspect rails, create scoped work orders, execute bounded workflows, verify receipts, and review Trust Ledger / Agent Work History evidence.
Primary endpoints
| Surface | URL |
|---|---|
| MCP endpoint | https://weverlabs.com/api/mcp |
| MCP descriptor | https://weverlabs.com/.well-known/mcp.json |
| Agent descriptor | https://weverlabs.com/.well-known/agent.json |
| Work-order API | https://weverlabs.com/api/work-orders |
| Trust Ledger summary | https://weverlabs.com/api/work-history/summary |
| Agent Work History | https://weverlabs.com/api/agent-work-history?agent_id=weverlabs-first-live-agent-001 |
| Proof pack | https://weverlabs.com/investor-proof-pack/ |
| OpenAPI | https://weverlabs.com/openapi.json |
| Pricing | https://weverlabs.com/pricing/ |
| Smithery listing | https://smithery.ai/server/davidwever/wever-labs-agentic-rails |
| Glama listing | https://glama.ai/mcp/servers/io.github.CodeWever/wever-labs |
What the server exposes
The MCP server exposes tools for scoped work orders, rail discovery, movement-fee quotes, rail execution, receipt verification, callback evidence, and work-history inspection.
The observed proof records show a non-sample requester moving through:
Work order -> Rail run -> Receipt -> Verification -> Trust Ledger -> Agent Work History
The current proof pack defines these records as technical de-risking evidence. They show that the loop executes, verifies, and persists end-to-end. External developer invocation is the next adoption milestone.
Smithery integration
Wever Labs Agentic Rails is available through Smithery for agent builders who want to connect through the Smithery CLI, MCP SDK, or AI SDK.
Smithery listing: https://smithery.ai/server/davidwever/wever-labs-agentic-rails
Install Smithery CLI:
npm install -g smithery
Install Smithery CLI: npm install -g smithery
Add the Wever Labs MCP server: smithery mcp add davidwever/wever-labs-agentic-rails
List available tools: smithery tool list {connection}
Call a tool: smithery tool call {connection} {tool_name} '{"key":"value"}'
## Current capabilities
- List MCP tools
- Quote paid rail movement fees
- Create or reference payment authority
- Complete paid PacketOps rail runs
- Verify receipts
- Return signed proof objects
- Create callback-ready proof
- Demonstrate credential allow/deny boundaries
- Provide receiver-side callback examples
## Registry naming
Default GitHub-auth server name:
`io.github.CodeWever/wever-labs`
If the registry requires lowercase GitHub namespace matching, change it to:
`io.github.codewever/wever-labs`
If DNS authentication is used later, use the example file:
`server.dns-auth.example.json`