# Wever Pay Agent Discovery Mesh [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://wever-pay-agent-mesh-phase5-staging.quiet-salad-e96e.workers.dev/.well-known/wever-pay-discovery.json  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/wever-pay-agent-discovery-mesh

## Description
Receipt-backed Base Sepolia commerce with standing mandates and independent outcome verification.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What Wever Pay Agent Discovery Mesh MCP server does

The Wever Pay Agent Discovery Mesh MCP server is described as supporting receipt-backed commerce on Base Sepolia. Its stated scope includes two related mechanisms: standing mandates and independent verification of outcomes. Together, these capabilities indicate a workflow in which commerce activity can be associated with receipts, ongoing authorization can be represented through mandates, and results can be checked separately.

The supplied material does not identify particular payment providers, wallet products, merchant systems, or external APIs. It also does not provide a list of callable MCP tools. Developers should therefore treat the description as a high-level capability statement rather than a complete integration reference.

## How it works

The documented network is Base Sepolia, a test network. Commerce is described as receipt-backed, which establishes receipts as part of the stated transaction model. Standing mandates are also part of the design, but the available material does not explain how mandates are created, stored, approved, revoked, or applied.

Independent outcome verification is another stated component. No verification protocol, verifier identity, response format, or failure behavior is provided. The Wever Pay Agent Discovery Mesh MCP server may therefore be relevant to agent workflows that require evidence of commerce outcomes, but the exact request and response lifecycle must be confirmed from the discovery metadata or implementation.

## Setup and configuration

The only supplied source is the following discovery document:

`https://wever-pay-agent-mesh-phase5-staging.quiet-salad-e96e.workers.dev/.well-known/wever-pay-discovery.json`

Its hostname identifies a staging deployment. The available material does not include installation commands, transport details, package information, configuration keys, authentication steps, or client-specific instructions. No environment variables can be reliably listed from the supplied content.

Before connecting an agent, inspect the discovery document to determine whether it publishes the server’s MCP endpoint, available capabilities, authorization requirements, or other runtime metadata. Do not assume that staging behavior or network availability matches a production deployment.

## Limitations and notes

The Wever Pay Agent Discovery Mesh MCP server cannot be evaluated as a complete tool integration from the provided information alone. Tool names, parameters, return schemas, error handling, payment flows, and mandate semantics are unspecified. Compatibility with individual MCP clients is also not documented.

Base Sepolia indicates a test-network context, so developers should confirm whether assets, receipts, and outcomes are intended for testing rather than production commerce. Independent verification is named as a capability, but its trust model and implementation are not described. The discovery URL should be treated as the authoritative next source for those details.

_Full upstream README: https://allmcps.com/mcp/wever-pay-agent-discovery-mesh/readme_