Home / MCP registry index / com.weverpay/exchange
Wever Pay Exchange
com.weverpay/exchange in the official MCP registry.
Endpoint https://exchange.weverpay.com/mcp.
The registry describes it as: Base mainnet exchange with real USDC, signed discovery, scoped agent accounts and 48 MCP tools.
We read its 48 tools on 2026-11-07. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again about every two weeks.
Connect it
The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:
claude mcp add --transport http exchange https://exchange.weverpay.com/mcp{
"mcpServers": {
"exchange": {
"url": "https://exchange.weverpay.com/mcp"
}
}
}code --add-mcp '{"name":"exchange","type":"http","url":"https://exchange.weverpay.com/mcp"}'Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.
Let Claude Code check servers as it adds them
With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.
claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-pluginsTools it advertises
get_discovery_manifest get_network_metrics get_connection_bundle generate_client_configuration get_connection_health get_sandbox_access_requirements report_compatibility discover_commerce_index search_verified_offers get_verified_offer get_verified_provider discover_assurance_services register_owner_mandate revoke_owner_mandate issue_signed_offer execute_authorized_purchase get_purchase_recovery_status recover_authorized_purchase verify_portable_bundle get_economic_history get_participant_registration_requirements request_participant_challenge complete_participant_registration revoke_participant_credential get_participant_account create_wallet get_wallet get_balance list_transactions get_external_funding_instructions claim_external_deposit request_payment get_payment_request send_payment get_payment refund_payment register_commerce_service search_commerce_services inspect_commerce_service purchase_commerce_service fulfill_commerce_purchase get_commerce_purchase_status recover_commerce_purchase request_commerce_refund get_commerce_receipt verify_economic_receipt request_withdrawal get_withdrawal_status
Tool changes
We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.
Fingerprint of its tools at our last full read (2026-11-07):
4ec39b9537e1c5ea. A client can hash the tools it is served the same way and compare;
the full value and a hash per tool are in this page as JSON.
Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.
Run this server? Show the check in your README
The badge reflects the latest read: 
[](https://lazaretto.dev/mcp-registry/com-weverpay-exchange)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.