get_withdrawal_status — MetaLend MCP Tool Read-only
get_withdrawal_status
(get withdrawal status) is one of 19 tools on the
MetaLend
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_withdrawal_status from your client
- Claude Code MetaLend get_withdrawal_status run in your project directory
- Claude Desktop MetaLend get_withdrawal_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MetaLend get_withdrawal_status ~/.cursor/mcp.json
- VS Code MetaLend get_withdrawal_status .vscode/mcp.json
- Zed MetaLend get_withdrawal_status ~/.config/zed/settings.json
- Windsurf MetaLend get_withdrawal_status ~/.codeium/windsurf/mcp_config.json
- Cline MetaLend get_withdrawal_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MetaLend get_withdrawal_status ~/.gemini/settings.json
- Grok MetaLend get_withdrawal_status .mcp.json (in your project root)
- ChatGPT MetaLend get_withdrawal_status Settings → Connectors → Advanced → Developer mode
- Claude.ai MetaLend get_withdrawal_status Settings → Connectors → Add custom connector
- LangChain MetaLend get_withdrawal_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http metalend https://mcp.metalend.tech/mcpOther 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.