private_payment_status — SwapEazi MCP Tool
private_payment_status
(private payment status) is one of 72 tools on the
SwapEazi
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call private_payment_status from your client
- Claude Code SwapEazi private_payment_status run in your project directory
- Claude Desktop SwapEazi private_payment_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SwapEazi private_payment_status ~/.cursor/mcp.json
- VS Code SwapEazi private_payment_status .vscode/mcp.json
- Zed SwapEazi private_payment_status ~/.config/zed/settings.json
- Windsurf SwapEazi private_payment_status ~/.codeium/windsurf/mcp_config.json
- Cline SwapEazi private_payment_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SwapEazi private_payment_status ~/.gemini/settings.json
- Grok SwapEazi private_payment_status .mcp.json (in your project root)
- ChatGPT SwapEazi private_payment_status Settings → Connectors → Advanced → Developer mode
- Claude.ai SwapEazi private_payment_status Settings → Connectors → Add custom connector
- LangChain SwapEazi private_payment_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http swapeazi https://swapeazi.io/api/mcpOther tools on this server
- discover_payment
- run_payments
- approve_payment_run
- payment_run_status
- recommend_payment_route
- assess_route
- liquidity_map
- onchain_liquidity
- record_landed
- reconcile_payment
- record_release
- release_status
- check_fx_charges
- books_record
- swapeazi_coverage
- swapeazi_corridor_registry
- swapeazi_guardrail_check
- swapeazi_guardrail_reconcile
- swapeazi_verify_record
- verify_release_record
- swapeazi_beneficiary_check
- payout_preflight
- swapeazi_dex_cost
- swapeazi_forward
- swapeazi_rwa_compare
- compile_intent
- map_options
- check_constraints
- reconcile_outcome
- coverage
- payout_rules
- route_intent
- intent_status
- prepare_payment
- confirm_payment
- payment_controls
- evidence_passport
- approval_status
- request_introduction
- corridor_events
- price_routes
- get_rate_receipt
- get_coverage
- create_mandate
- get_mandate
- check_payment_against_mandate
- payment_intent
- decide_intent
- rail_handoff
- connect_rail_account
- list_rail_accounts
- remove_rail_account
- join_network
- rail_position
- rate_deal_history
- parallel_signal
- get_corridor_rates
- calculate_payment_cost
- compare_payment_providers
- get_corridor_capacity
- get_payment_guide
- check_provider_liquidity
- prepare_payment_instruction
- request_payment_approval
- submit_payment
- track_payment_settlement
- payment_index
- add_payment_outcome
- swapeazi_landed_cost
- swapeazi_route_compare
- analyse_payment_leakage
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.