Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Wever Pay Exchange

REMOTE · EXCHANGE.WEVERPAY.COM

48-tool Base mainnet USDC exchange. Pay the listed price from your own wallet with x402.

+4 this week 63 Trust /100

Last scanned (18 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security49
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 2378 tokens (~49/item across 48 items; 48 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management46
  • Stability check failed: schema churn in the 14 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage68
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 4% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 49 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 42 to 46.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 36 to 39.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 29 to 32.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 22 to 26.

  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 12 to 16.

  • 10 Nov 26 +1
    • Stability: 0.07 → fail ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “execute_authorized_purchase” rewrote its description, which is the text the model reads security
    • Tool “purchase_commerce_service” rewrote its description, which is the text the model reads security
    • “execute_authorized_purchase” added a required parameter “serviceId”, so existing callers break ▼ functional
    • Server version: 2.1.0 → 2.2.0 functional
    • “execute_authorized_purchase” added an optional parameter “input” cosmetic
    • “purchase_commerce_service” added an optional parameter “paymentPayload” cosmetic
    • “execute_authorized_purchase” made “agentRequest” optional cosmetic
    • “execute_authorized_purchase” made “offer” optional cosmetic
    • “purchase_commerce_service” made “buyerWalletId” optional cosmetic
    • “purchase_commerce_service” made “idempotencyKey” optional cosmetic
    • “purchase_commerce_service” made “input” optional cosmetic
  • 8 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “execute_authorized_purchase” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 2.0.0 → 2.1.0 functional
  • 7 Nov 26 56

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://exchange.weverpay.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=weverpay.com CN=WE1,O=Google Trust Services,C=US 7 Nov 2026 5 Feb 2027 ECDSA 256 ECDSA-SHA256 3b55187f7888d92213f107c5b315013b
SANs: weverpay.com, exchange.weverpay.com, *.exchange.weverpay.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of exchange.weverpay.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
weverpay.com. DS published 2371 13 Verified
exchange.weverpay.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
content-security-policy default-src 'none'; frame-ancestors 'none'; base-uri 'none'
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://exchange.weverpay.com/mcp Verified 200
http (plaintext) http://exchange.weverpay.com/mcp Inconclusive 405
MCP tools · 48 exposed · ~2,290 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
claim_external_deposit ~86

Claim a completed external Base mainnet USDC transfer for an owned wallet. The exchange derives and verifies the bound EVM source, exact asset transfer, amount, recipient, and unique transaction before canonical ledger credit.

NameTypeReqDescription
amountMinorintegeryes–
idempotencyKeystringyes–
transactionHashstringyes–
walletIdstringyes–

No output schema declared.

No examples provided.

complete_participant_registration ~40

Prove Ed25519 key control, create or replay the canonical exchange account, and activate one scoped credential generation.

NameTypeReqDescription
completionobjectyes–

No output schema declared.

No examples provided.

create_wallet ~79

Create or bind a permitted BUYER or SELLER wallet for the authenticated agent after EVM ownership proof. Published limits apply per verified identity, never globally.

NameTypeReqDescription
addressstringyes–
displayNamestringyes–
idempotencyKeystringyes–
ownershipProofstringyes–
rolestringyes–

No output schema declared.

No examples provided.

discover_assurance_services ~18

Discover signed-offer commerce assurance services.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

discover_commerce_index ~21

Read the signed receipt-backed Wever Commerce Index manifest.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

execute_authorized_purchase ~84

Pay the listed price from your own wallet with x402; no separate approval. Omit paymentPayload to read payment terms. Provide serviceId, input and paymentPayload to buy.

NameTypeReqDescription
agentRequestobject––
inputobject––
offerobject––
paymentPayloadobject––
serviceIdstringyes–

No output schema declared.

No examples provided.

fulfill_commerce_purchase ~104

Fulfill one paid dynamic purchase exactly once with a seller-signed Ed25519 artifact. The output schema is validated, seller proceeds and the existing fee are settled, and a network-signed economic receipt is issued.

NameTypeReqDescription
fulfillmentobjectyesA JSON object accepted only when its canonical serialized form is at most 50000 characters and its nesting depth is at most 64.
idempotencyKeystringyes–
purchaseIdstringyes–

No output schema declared.

No examples provided.

generate_client_configuration ~33

Generate a credential-free MCP or A2A connection configuration for a supported agent client.

NameTypeReqDescription
clientstringyes–

No output schema declared.

No examples provided.

get_balance ~27

Read available and pending USDC for one owned wallet.

NameTypeReqDescription
walletIdstringyes–

No output schema declared.

No examples provided.

get_commerce_purchase_status ~42

Read an authorized buyer or seller view of one dynamic purchase, fulfillment state, signed receipt, and next recovery action.

NameTypeReqDescription
purchaseIdstringyes–

No output schema declared.

No examples provided.

get_commerce_receipt ~33

Read an existing canonical commerce receipt involving an owned buyer or seller wallet.

NameTypeReqDescription
receiptIdstringyes–

No output schema declared.

No examples provided.

get_connection_bundle ~19

Retrieve the universal signed Wever Pay connection bundle.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_connection_health ~20

Read sanitized distribution, connection, and organic-use status.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_discovery_manifest ~31

Read the signed manifest connecting Wever Pay identities, endpoints, protocols, payment networks, and verification instructions.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_economic_history ~27

Read portable verified economic history for an agent.

NameTypeReqDescription
agentIdstringyes–

No output schema declared.

No examples provided.

get_external_funding_instructions ~45

Read the exact Base mainnet USDC transfer and claim instructions for an owned wallet. This does not move or credit value.

NameTypeReqDescription
walletIdstringyes–

No output schema declared.

No examples provided.

get_network_metrics ~24

Read public-safe discovery, commerce, verification, recovery, and availability metrics.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_participant_account ~19

Inspect the authenticated participant's canonical exchange account.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_participant_registration_requirements ~54

Read the active isolated Base mainnet participant contract, canonical exchange registration authority, lifecycle state, activation prerequisites, policy, credentials, wallets, funding, service admission, commerce, receipts, withdrawal, and recovery rules.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_payment ~30

Read a payment for which the participant owns the buyer or seller wallet.

NameTypeReqDescription
paymentIdstringyes–

No output schema declared.

No examples provided.

get_payment_request ~32

Read a payment request owned by or explicitly addressed to the authenticated participant.

NameTypeReqDescription
paymentRequestIdstringyes–

No output schema declared.

No examples provided.

get_purchase_recovery_status ~29

Inspect durable recovery state for an owned Payment Identifier.

NameTypeReqDescription
paymentIdentifierstringyes–

No output schema declared.

No examples provided.

get_sandbox_access_requirements ~30

Read the mainnet authentication, standing-mandate, and verification requirements without issuing credentials.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_verified_offer ~26

Inspect one indexed service and its verified provenance.

NameTypeReqDescription
serviceIdstring––

No output schema declared.

No examples provided.

get_verified_provider ~27

Inspect one signed provider identity and its verified offers.

NameTypeReqDescription
providerIdstring––

No output schema declared.

No examples provided.

get_wallet ~25

Read one wallet owned by the authenticated participant.

NameTypeReqDescription
walletIdstringyes–

No output schema declared.

No examples provided.

get_withdrawal_status ~61

Read one withdrawal and its canonical provider-transfer, ledger status, and machine-readable WAIT_FOR_RECONCILIATION, RETRY_SAME_REQUEST, or RECOVERY_REQUIRED action after proving ownership of the source wallet.

NameTypeReqDescription
withdrawalIdstringyes–

No output schema declared.

No examples provided.

inspect_commerce_service ~35

Inspect one existing commerce directory service.

NameTypeReqDescription
idempotencyKeystringyes–
serviceIdstringyes–

No output schema declared.

No examples provided.

issue_signed_offer ~29

Issue an official x402 signed offer with Payment Identifier support.

NameTypeReqDescription
serviceIdstringyes–

No output schema declared.

No examples provided.

list_transactions ~40

Read bounded ledger history for one owned wallet.

NameTypeReqDescription
cursorstring|null––
limitinteger––
walletIdstringyes–

No output schema declared.

No examples provided.

purchase_commerce_service ~135

Buy a listed Commerce Assurance service with a buyer-signed x402 payment from your own wallet; no separate approval. Omit paymentPayload for payment terms.

NameTypeReqDescription
buyerWalletIdstring––
idempotencyKeystring––
inputobject–A JSON object accepted only when its canonical serialized form is at most 50000 characters and its nesting depth is at most 64.
paymentPayloadobject–A JSON object accepted only when its canonical serialized form is at most 50000 characters and its nesting depth is at most 64.
serviceIdstringyes–

No output schema declared.

No examples provided.

recover_authorized_purchase ~30

Resume an owned uncertain purchase through the existing durable recovery path.

NameTypeReqDescription
paymentIdentifierstringyes–

No output schema declared.

No examples provided.

recover_commerce_purchase ~60

Resume an uncertain buyer authorization with the same purchase identity and economic idempotency key, without creating a second charge.

NameTypeReqDescription
buyerWalletIdstringyes–
idempotencyKeystringyes–
purchaseIdstringyes–

No output schema declared.

No examples provided.

refund_payment ~51

Refund a sale from the participant's owned seller wallet through existing fee-reversal rules.

NameTypeReqDescription
amountMinorintegeryes–
idempotencyKeystringyes–
paymentIdstringyes–

No output schema declared.

No examples provided.

register_commerce_service ~102

Automatically admit a versioned service into the existing commerce directory and Commerce Index after bounded JSON Schema draft 2020-12, examples, price, endpoint, content hash, seller, payout, and fulfillment-key validation. No seller approval is required.

NameTypeReqDescription
idempotencyKeystringyes–
payoutOwnershipProofstringyesEIP-191 signature by the seller wallet address over the published payout-ownership message.
serviceobjectyes–

No output schema declared.

No examples provided.

register_owner_mandate ~30

Register a reusable owner-signed mandate for autonomous agent execution.

NameTypeReqDescription
mandateobjectyes–

No output schema declared.

No examples provided.

report_compatibility ~61

Record a bounded client compatibility result as external-unclassified unless separately verified as organic.

NameTypeReqDescription
clientstringyes–
notesstring––
reporterstring––
stagestringyes–
successbooleanyes–

No output schema declared.

No examples provided.

request_commerce_refund ~76

Create a durable buyer refund request for a paid dynamic purchase. The seller resolves it through the existing seller-authorized refund_payment tool and fee-reversal ledger rules.

NameTypeReqDescription
amountMinorintegeryes–
idempotencyKeystringyes–
purchaseIdstringyes–
reasonstringyes–

No output schema declared.

No examples provided.

request_participant_challenge ~45

Request a five-minute server-signed Ed25519 challenge for any schema-valid agent.external. registration through automated cryptographic challenge-response.

NameTypeReqDescription
registrationRequestobjectyes–

No output schema declared.

No examples provided.

request_payment ~73

Create a bounded USDC request payable by one named participant agent.

NameTypeReqDescription
amountMinorintegeryes–
buyerAgentIdstringyes–
descriptionstringyes–
expiresAtstring|null––
idempotencyKeystringyes–
sellerWalletIdstringyes–

No output schema declared.

No examples provided.

request_withdrawal ~54

Transfer available USDC out of an owned wallet only to its verified EVM-bound address.

NameTypeReqDescription
amountMinorintegeryes–
idempotencyKeystringyes–
walletIdstringyes–

No output schema declared.

No examples provided.

revoke_owner_mandate ~28

Apply an owner-signed mandate revocation.

NameTypeReqDescription
revocationobjectyes–

No output schema declared.

No examples provided.

revoke_participant_credential ~56

Revoke the authenticated agent's active participant credential without operator intervention. Revocation is idempotent and cannot affect another agent's credential.

NameTypeReqDescription
credentialIdstringyes–
idempotencyKeystringyes–

No output schema declared.

No examples provided.

search_commerce_services ~66

Search the existing commerce directory with bounded filters.

NameTypeReqDescription
assetstring––
idempotencyKeystringyes–
maxPriceAtomicinteger––
networkstring––
querystring––
statusstring––

No output schema declared.

No examples provided.

search_verified_offers ~90

Filter independently verified offers by policy and history.

NameTypeReqDescription
availableboolean––
capabilitystring––
cursorstring––
evidenceRequirementsarray––
limitinteger––
maximumPriceAtomicinteger––
minimumVerifiedCompletionsinteger––
networkstring––
providerIdstring––

No output schema declared.

No examples provided.

send_payment ~84

Transfer bounded available USDC from any participant-owned wallet, including legitimately available seller proceeds, using the existing payment engine.

NameTypeReqDescription
buyerWalletIdstringyes–
descriptionstring––
grossAmountMinorinteger––
idempotencyKeystringyes–
paymentRequestIdstring––
sellerWalletIdstring––

No output schema declared.

No examples provided.

verify_economic_receipt ~49

Verify the network Ed25519 signature and digest of an authorized canonical dynamic-commerce or completed-withdrawal receipt.

NameTypeReqDescription
receiptIdstring––
withdrawalIdstring––

No output schema declared.

No examples provided.

verify_portable_bundle ~30

Independently verify an x402 and Wever assurance artifact bundle.

NameTypeReqDescription
bundleobjectyes–

No output schema declared.

No examples provided.

Install

How do I install the Wever Pay Exchange MCP server?

Wever Pay Exchange is a hosted endpoint at https://exchange.weverpay.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · exchange.weverpay.com

# add to Claude Code
claude mcp add --transport http com-weverpay-exchange 'https://exchange.weverpay.com/mcp'
Common questions

What is the Wever Pay Exchange MCP server?

Wever Pay Exchange is an MCP server listed in the public MCP registry as com.weverpay/exchange. 48-tool Base mainnet USDC exchange. Pay the listed price from your own wallet with x402. This page covers its hosted endpoint (https://exchange.weverpay.com/mcp).

Is the Wever Pay Exchange MCP server safe to use?

Wever Pay Exchange scores 63 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Wever Pay Exchange MCP server expose?

Wever Pay Exchange exposes 48 tools: get_discovery_manifest, get_network_metrics, get_connection_bundle, generate_client_configuration, get_connection_health, and 43 more. Their descriptions and schemas cost roughly 2,290 tokens of context every time the server is loaded.

Does the Wever Pay Exchange MCP server require authentication?

No. We connected to Wever Pay Exchange without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Wever Pay Exchange MCP server still maintained?

Wever Pay Exchange is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Wever Pay Exchange MCP server?

VerifyMCP ran 12 checks on Wever Pay Exchange, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Wever Pay Exchange: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.