daski_get_payment_challenge — Daski MCP Tool
daski_get_payment_challenge
(daski get payment challenge) is one of 22 tools on the
Daski
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call daski_get_payment_challenge from your client
- Claude Code Daski daski_get_payment_challenge run in your project directory
- Claude Desktop Daski daski_get_payment_challenge ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Daski daski_get_payment_challenge ~/.cursor/mcp.json
- VS Code Daski daski_get_payment_challenge .vscode/mcp.json
- Zed Daski daski_get_payment_challenge ~/.config/zed/settings.json
- Windsurf Daski daski_get_payment_challenge ~/.codeium/windsurf/mcp_config.json
- Cline Daski daski_get_payment_challenge ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Daski daski_get_payment_challenge ~/.gemini/settings.json
- Grok Daski daski_get_payment_challenge .mcp.json (in your project root)
- ChatGPT Daski daski_get_payment_challenge Settings → Connectors → Advanced → Developer mode
- Claude.ai Daski daski_get_payment_challenge Settings → Connectors → Add custom connector
- LangChain Daski daski_get_payment_challenge pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http daski https://daski.io/mcpOther tools on this server
- daski_buy_outcome
- daski_get_setup_guide
- daski_get_outcome_requirements
- daski_list_outcomes
- daski_get_outcome
- daski_get_order_status
- daski_submit_order_input
- daski_cancel_order
- daski_get_order_artifact
- daski_contact_order_support
- daski_get_order_access
- daski_confirm_delivery
- daski_revoke_delivery_confirmation
- daski_list_my_orders
- daski_get_my_reputation
- daski_list_assets
- daski_use_asset
- daski_list_providers
- daski_get_provider
- daski_get_service
- daski_resolve_agent
This list was read from the server itself, by connecting to it and calling tools/list on 1 October 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.