address_sanctions_screen — Agent Data API MCP Tool
address_sanctions_screen
(address sanctions screen) is one of 65 tools on the
Agent Data API
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call address_sanctions_screen from your client
- Claude Code Agent Data API address_sanctions_screen run in your project directory
- Claude Desktop Agent Data API address_sanctions_screen ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Agent Data API address_sanctions_screen ~/.cursor/mcp.json
- VS Code Agent Data API address_sanctions_screen .vscode/mcp.json
- Zed Agent Data API address_sanctions_screen ~/.config/zed/settings.json
- Windsurf Agent Data API address_sanctions_screen ~/.codeium/windsurf/mcp_config.json
- Cline Agent Data API address_sanctions_screen ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Agent Data API address_sanctions_screen ~/.gemini/settings.json
- Grok Agent Data API address_sanctions_screen .mcp.json (in your project root)
- ChatGPT Agent Data API address_sanctions_screen Settings → Connectors → Advanced → Developer mode
- Claude.ai Agent Data API address_sanctions_screen Settings → Connectors → Add custom connector
- LangChain Agent Data API address_sanctions_screen pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agent-data-api https://ca-tax-api-mainnet.lxtap.workers.dev/mcpOther tools on this server
- canada_sales_tax
- canada_business_days
- canada_statutory_holidays
- fx_ecb_rates
- fx_ecb_convert
- token_risk_check
- solana_token_snapshot
- solana_wallet
- prepayment_safety_check
- prepayment_safety_check_lite
- company_jobs
- x402_ping
- base_token_snapshot
- base_wallet_balances
- base_transaction_summary
- base_gas_prices
- base_contract_info
- base_erc20_allowance
- base_nft_metadata
- base_large_trades
- base_new_pools
- base_wallet_profile
- base_resolve_basename
- eth_token_snapshot
- eth_wallet_balances
- eth_transaction_summary
- eth_gas_prices
- eth_contract_info
- eth_erc20_allowance
- eth_nft_metadata
- eth_large_trades
- eth_new_pools
- eth_wallet_profile
- eth_resolve_ens
- arbitrum_token_snapshot
- arbitrum_wallet_balances
- arbitrum_transaction_summary
- arbitrum_gas_prices
- arbitrum_contract_info
- arbitrum_erc20_allowance
- arbitrum_nft_metadata
- arbitrum_large_trades
- arbitrum_new_pools
- arbitrum_wallet_profile
- optimism_token_snapshot
- optimism_wallet_balances
- optimism_transaction_summary
- optimism_gas_prices
- optimism_contract_info
- optimism_erc20_allowance
- optimism_nft_metadata
- optimism_large_trades
- optimism_new_pools
- optimism_wallet_profile
- polygon_token_snapshot
- polygon_wallet_balances
- polygon_transaction_summary
- polygon_gas_prices
- polygon_contract_info
- polygon_erc20_allowance
- polygon_nft_metadata
- polygon_large_trades
- polygon_new_pools
- polygon_wallet_profile
This list was read from the server itself, by connecting to it and calling tools/list on 24 October 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.