list_payments — Singularity Layer MCP MCP Tool Read-only
list_payments
(list payments) is one of 78 tools on the
Singularity Layer MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call list_payments from your client
- Claude Code Singularity Layer MCP list_payments run in your project directory
- Claude Desktop Singularity Layer MCP list_payments ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Singularity Layer MCP list_payments ~/.cursor/mcp.json
- VS Code Singularity Layer MCP list_payments .vscode/mcp.json
- Zed Singularity Layer MCP list_payments ~/.config/zed/settings.json
- Windsurf Singularity Layer MCP list_payments ~/.codeium/windsurf/mcp_config.json
- Cline Singularity Layer MCP list_payments ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Singularity Layer MCP list_payments ~/.gemini/settings.json
- Grok Singularity Layer MCP list_payments .mcp.json (in your project root)
- ChatGPT Singularity Layer MCP list_payments Settings → Connectors → Advanced → Developer mode
- Claude.ai Singularity Layer MCP list_payments Settings → Connectors → Add custom connector
- LangChain Singularity Layer MCP list_payments pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http singularity https://mcp.x402layer.cc/mcpOther tools on this server
- vault_usage
- vault_list_agents
- vault_list_snapshots
- vault_delete_snapshot
- vault_subscribe_pro
- vault_how_to_backup
- list_dataset_pricing
- request_dataset_payment
- create_dataset_with_payment
- get_dataset_status
- cloud_list_plans
- cloud_list_instances
- cloud_get_instance
- cloud_credit_balance
- cloud_credit_activity
- cloud_pod_catalog
- cloud_list_pods
- cloud_get_pod
- cloud_pod_usage
- cloud_list_training_runs
- cloud_get_training_run
- cloud_grid_models
- cloud_grid_usage
- cloud_list_processors
- cloud_processor_runs
- cloud_deploy_pod
- cloud_deploy_machine
- cloud_deploy_processor
- cloud_start_training_run
- cloud_pod_chat
- cloud_pod_exec
- cloud_pod_files
- cloud_pod_write_file
- list_payment_links
- get_payment_link
- create_payment_link
- create_invoice
- list_invoices
- get_invoice
- browse_marketplace
- get_listing
- get_featured
- get_top_rated
- get_agent
- list_categories
- list_networks
- list_agents
- list_my_endpoints
- list_my_campaigns
- create_campaign
- update_campaign
- update_endpoint
- list_my_products
- update_product
- get_endpoint_details
- get_endpoint_stats
- set_webhook
- remove_webhook
- delete_endpoint
- request_endpoint_creation_payment
- create_endpoint_with_payment
- request_endpoint_topup_payment
- topup_endpoint_with_payment
- request_product_purchase_payment
- purchase_product_with_payment
- request_endpoint_credit_purchase_payment
- purchase_endpoint_credits_with_payment
- get_agent_registry_info
- request_agent_wallet_challenge
- verify_agent_wallet_challenge
- list_my_agent_bindable_endpoints
- list_my_registered_agents
- prepare_agent_registration
- finalize_agent_registration
- prepare_agent_update
- finalize_agent_update
- submit_agent_feedback
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.