check_payment_data — toolforte MCP Prompt

check_payment_data is one of 4 prompts on the toolforte MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke check_payment_data from your client

• Claude Code toolforte Prompt/check_payment_data run in your project directory
• Claude Desktop toolforte Prompt/check_payment_data ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor toolforte Prompt/check_payment_data ~/.cursor/mcp.json
• VS Code toolforte Prompt/check_payment_data .vscode/mcp.json
• Zed toolforte Prompt/check_payment_data ~/.config/zed/settings.json
• Windsurf toolforte Prompt/check_payment_data ~/.codeium/windsurf/mcp_config.json
• Cline toolforte Prompt/check_payment_data ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI toolforte Prompt/check_payment_data ~/.gemini/settings.json
• Grok toolforte Prompt/check_payment_data .mcp.json (in your project root)
• ChatGPT toolforte Prompt/check_payment_data Settings → Connectors → Advanced → Developer mode
• Claude.ai toolforte Prompt/check_payment_data Settings → Connectors → Add custom connector
• LangChain toolforte Prompt/check_payment_data pip install langchain-mcp-adapters

Other prompts on this server

• when_to_use_toolforte
• dutch_test_dataset
• page_to_pdf

toolforte also offers 1 resource — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.