# Wever Labs MCP Server Wrapper

Agentic operating infrastructure for complex workflows for the agent-to-agent economy.

## Endpoint

- MCP endpoint: https://weverlabs.com/api/mcp
- Descriptor: https://weverlabs.com/.well-known/mcp.json
- Server metadata: https://weverlabs.com/mcp-server.json
- Agent Card: https://weverlabs.com/.well-known/agent-card.json
- OpenAPI: https://weverlabs.com/openapi.json
- LLM index: https://weverlabs.com/llms.txt
- Public agent client: https://weverlabs.com/agent-client/

## Pricing model

Tool access and wallet opening are free. Fees attach only to completed transaction, escrow, or hybrid rail movement. The rail quote object returns movement fee units, total units, receipt fields, and payment reference hooks.

## Version 1.8.0 additions

- External directory credential activation records.
- Live registry verification records.
- Signed directory submission receipts.
- x402 facilitator settlement binding.
- A2A task lifecycle records.
- Public repo CI badge metadata.
- Release gate automation.
- Stripe movement fee Checkout and webhook binding.

## Minimal sequence

1. Read `/agents.json` and `/.well-known/mcp.json`.
2. Initialize `/api/mcp`.
3. Call `tools/list` and confirm 66 tools.
4. Call `quote_run` or `quote_movement_fee`.
5. Create a payment challenge or Stripe Checkout session when live settlement is required.
6. Call `start_rail_run` with `rail_key`, `idempotency_key`, and a valid `payment_reference` when payment is required.
7. Store `production_run_id`, `return_package_id`, `receipt_id`, hashes, signatures, and callback state.
8. Verify receipt.
9. Persist benchmark, receipt ledger, directory status, Stripe event, and release gate records when Supabase is active.

## Pass markers

- `tools/list` returns 66 tool definitions.
- `run_external_agent_client_runner` returns `runner_state: passed` and `transcript_hash`.
- `run_live_supabase_verification` returns `all_tables_verified` after SQL v4 and schema cache reload.
- `create_stripe_movement_fee_checkout` returns `checkout_session_created` when Stripe env is configured, or `stripe_env_missing` before activation.
- `run_release_gate_automation` returns `gate_state: passed` only after benchmark, durable, commercial, directory, and boundary checks pass.