prepare_paid_handoff — RIVET / AliEV EV Charging Site Intelligence MCP Tool
prepare_paid_handoff
(prepare paid handoff) is one of 6 tools on the
RIVET / AliEV EV Charging Site Intelligence
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call prepare_paid_handoff from your client
- Claude Code RIVET / AliEV EV Charging Site Intelligence prepare_paid_handoff run in your project directory
- Claude Desktop RIVET / AliEV EV Charging Site Intelligence prepare_paid_handoff ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor RIVET / AliEV EV Charging Site Intelligence prepare_paid_handoff ~/.cursor/mcp.json
- VS Code RIVET / AliEV EV Charging Site Intelligence prepare_paid_handoff .vscode/mcp.json
- Zed RIVET / AliEV EV Charging Site Intelligence prepare_paid_handoff ~/.config/zed/settings.json
- Windsurf RIVET / AliEV EV Charging Site Intelligence prepare_paid_handoff ~/.codeium/windsurf/mcp_config.json
- Cline RIVET / AliEV EV Charging Site Intelligence prepare_paid_handoff ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI RIVET / AliEV EV Charging Site Intelligence prepare_paid_handoff ~/.gemini/settings.json
- Grok RIVET / AliEV EV Charging Site Intelligence prepare_paid_handoff .mcp.json (in your project root)
- ChatGPT RIVET / AliEV EV Charging Site Intelligence prepare_paid_handoff Settings → Connectors → Advanced → Developer mode
- Claude.ai RIVET / AliEV EV Charging Site Intelligence prepare_paid_handoff Settings → Connectors → Add custom connector
- LangChain RIVET / AliEV EV Charging Site Intelligence prepare_paid_handoff pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http aliev https://aliev.base44.app/functions/alievMcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.