Wever Labs MCP Registry Publishing Pack

Wever Labs provides MCP-callable workflow rails for agents that need bounded work execution, movement-fee quotes, payment authority references, paid rail runs, structured return packages, signed receipts, callback evidence, ledger entries, and verification proof.

Wever Labs agent discovery links

Wever Labs exposes MCP-accessible workflow rails for proof-backed agent runs, receipts, callbacks, and handoff packages.

Surface	URL
Website	https://weverlabs.com
MCP endpoint	https://weverlabs.com/api/mcp
MCP descriptor	https://weverlabs.com/.well-known/mcp.json
Free proof run	https://weverlabs.com/free-proof-run/
Agent tools manifest	https://weverlabs.com/agent-tools.json
All agent tools	https://weverlabs.com/all-agent-tools/
OpenAPI	https://weverlabs.com/openapi.json
LLM instructions	https://weverlabs.com/llms.txt
Smithery listing	https://smithery.ai/servers/davidwever/wever-labs-agentic-rails

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/servers/davidwever/wever-labs-agentic-rails

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

Configuration

This server is a hosted remote MCP server. Users do not install or run a local package target. Configure an MCP client that supports hosted Streamable HTTP remotes with:

{
  "mcpServers": {
    "wever-labs": {
      "url": "https://weverlabs.com/api/mcp"
    }
  }
}

Smithery users can connect with smithery mcp add davidwever/wever-labs-agentic-rails.

The endpoint accepts public discovery, tool listing, quote, sandbox proof, callback acknowledgement, and verification-read calls without publishing secrets. Production or persistent-write workflows can require scoped agent credentials, payment references, idempotency keys, or Wever Labs server-side provider credentials. Optional HTTP headers accepted by the endpoint include X-Wever-Agent-Key, Idempotency-Key, X-Idempotency-Key, X-Wever-Tool-Scope, X-Wever-Movement-Type, and X-Wever-Movement-Amount; they are not required for the public remote target and are not included in the Wardn remote configuration.

Documented sample-client environment variables such as WEVER_MCP_URL, WEVER_BASE_URL, WEVER_RAIL_KEY, WEVER_MOVEMENT_TYPE, WEVER_MOVEMENT_AMOUNT_UNITS, WEVER_IDEMPOTENCY_KEY, WEVER_BASE, BASE, and RAIL_KEY are only for external client examples and are not needed in Wardn runtime launch configuration. Server-side secrets such as ANTHROPIC_API_KEY, STRIPE_SECRET_KEY, and STRIPE_WEBHOOK_SECRET remain on Wever Labs infrastructure and must not be supplied to the public remote client.

Limitations and Operational Notes

The server is remote-only in the inspected docs; no local MCP server package is documented. Tool access and wallet opening are free, but completed transaction, escrow, or hybrid rail movement can carry movement fees. Agents should quote with quote_run or quote_movement_fee before paid execution and supply accepted payment authority, payment reference, or checkout state for billable production completion.

Registry Metadata Note

The live MCP descriptor currently reports version 1.8.4, while the registry source server.json and official_registry_version report 1.8.0. This draft uses 1.8.4 and records the 1.8.0 registry-source value in sourceReview.versionRationale; the prior 1.0.0 value was stale. Website is set to https://weverlabs.com. STRIPE_PAYMENT_LINK_* and CLAUDE_ANALYSIS_* variables are documented in the live OpenAPI manifest as hosted server-side configuration, not MCP client remote settings, so they are recorded in sourceReview.environmentVariables with empty defaults.

Repository metadata is set to https://github.com/CodeWever/wever-labs-agent-client because the pinned upstream registry server.json declares that repository; https://github.com/CodeWever/wever-labs-mcp-registry remains source-review evidence for the publishing pack and pinned server.json.