verify_payee_binding — SpendPreflight MCP Tool
verify_payee_binding
(verify payee binding) is one of 17 tools on the
SpendPreflight
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call verify_payee_binding from your client
- Claude Code SpendPreflight verify_payee_binding run in your project directory
- Claude Desktop SpendPreflight verify_payee_binding ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SpendPreflight verify_payee_binding ~/.cursor/mcp.json
- VS Code SpendPreflight verify_payee_binding .vscode/mcp.json
- Zed SpendPreflight verify_payee_binding ~/.config/zed/settings.json
- Windsurf SpendPreflight verify_payee_binding ~/.codeium/windsurf/mcp_config.json
- Cline SpendPreflight verify_payee_binding ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SpendPreflight verify_payee_binding ~/.gemini/settings.json
- Grok SpendPreflight verify_payee_binding .mcp.json (in your project root)
- ChatGPT SpendPreflight verify_payee_binding Settings → Connectors → Advanced → Developer mode
- Claude.ai SpendPreflight verify_payee_binding Settings → Connectors → Add custom connector
- LangChain SpendPreflight verify_payee_binding pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http spendpreflight https://api.spendpreflight.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 5 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.