discover_commerce_index — Wever Pay Open Exchange Public Beta MCP Tool
discover_commerce_index
(discover commerce index) is one of 50 tools on the
Wever Pay Open Exchange Public Beta
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call discover_commerce_index from your client
- Claude Code Wever Pay Open Exchange Public Beta discover_commerce_index run in your project directory
- Claude Desktop Wever Pay Open Exchange Public Beta discover_commerce_index ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Wever Pay Open Exchange Public Beta discover_commerce_index ~/.cursor/mcp.json
- VS Code Wever Pay Open Exchange Public Beta discover_commerce_index .vscode/mcp.json
- Zed Wever Pay Open Exchange Public Beta discover_commerce_index ~/.config/zed/settings.json
- Windsurf Wever Pay Open Exchange Public Beta discover_commerce_index ~/.codeium/windsurf/mcp_config.json
- Cline Wever Pay Open Exchange Public Beta discover_commerce_index ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Wever Pay Open Exchange Public Beta discover_commerce_index ~/.gemini/settings.json
- Grok Wever Pay Open Exchange Public Beta discover_commerce_index .mcp.json (in your project root)
- ChatGPT Wever Pay Open Exchange Public Beta discover_commerce_index Settings → Connectors → Advanced → Developer mode
- Claude.ai Wever Pay Open Exchange Public Beta discover_commerce_index Settings → Connectors → Add custom connector
- LangChain Wever Pay Open Exchange Public Beta discover_commerce_index pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http public-testnet-alpha https://wever-pay-agent-mesh-phase5-staging.quiet-salad-e96e.workers.dev/mcpOther tools on this server
- get_discovery_manifest
- get_network_metrics
- get_connection_bundle
- generate_client_configuration
- get_connection_health
- get_sandbox_access_requirements
- report_compatibility
- 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_testnet_funding
- get_testnet_funding_status
- 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
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.