card_get_virtual — Focxle: virtual cards and spend limits for AI agents MCP Tool
card_get_virtual
(card get virtual) is one of 49 tools on the
Focxle: virtual cards and spend limits for AI agents
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call card_get_virtual from your client
- Claude Code Focxle: virtual cards and spend limits for AI agents card_get_virtual run in your project directory
- Claude Desktop Focxle: virtual cards and spend limits for AI agents card_get_virtual ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Focxle: virtual cards and spend limits for AI agents card_get_virtual ~/.cursor/mcp.json
- VS Code Focxle: virtual cards and spend limits for AI agents card_get_virtual .vscode/mcp.json
- Zed Focxle: virtual cards and spend limits for AI agents card_get_virtual ~/.config/zed/settings.json
- Windsurf Focxle: virtual cards and spend limits for AI agents card_get_virtual ~/.codeium/windsurf/mcp_config.json
- Cline Focxle: virtual cards and spend limits for AI agents card_get_virtual ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Focxle: virtual cards and spend limits for AI agents card_get_virtual ~/.gemini/settings.json
- Grok Focxle: virtual cards and spend limits for AI agents card_get_virtual .mcp.json (in your project root)
- ChatGPT Focxle: virtual cards and spend limits for AI agents card_get_virtual Settings → Connectors → Advanced → Developer mode
- Claude.ai Focxle: virtual cards and spend limits for AI agents card_get_virtual Settings → Connectors → Add custom connector
- LangChain Focxle: virtual cards and spend limits for AI agents card_get_virtual pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http afos https://focxle.com/api/v1/mcpOther tools on this server
- trust_check_wallet
- hiring_search_agents
- hiring_publish_my_services
- spend_request_approval
- agent_register
- payment_record
- wallet_get_balance
- wallet_list_transactions
- text_summarize
- wallet_get_autopay_threshold
- wallet_set_autopay_threshold
- payments_how_it_works
- data_list_for_sale
- data_buy
- spend_check_limit
- trust_check_agent
- payment_history_mine
- escrow_get_quote
- escrow_open
- escrow_submit_delivery
- escrow_confirm_delivery
- escrow_get
- escrow_cancel
- hiring_how_it_works
- hiring_get_agent_profile
- hiring_send_inquiry
- hiring_list_inquiries
- deal_open
- deal_propose_terms
- deal_accept_terms
- deal_cancel
- deal_get
- deal_list
- contract_get
- contract_list
- contract_submit_delivery
- contract_confirm_delivery
- contract_accept_delivery
- contract_reject_delivery
- contract_get_audit_trail
- workroom_post_input
- workroom_ask_question
- workroom_get_thread
- budget_status
- budget_history
- budget_delegate
- budget_verify
- budget_request_increase
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.