ADDX MCP server
No ADDX Model Context Protocol server exists. ADDX publishes no MCP endpoint, no stdio package and no mention of MCP anywhere on its developer or marketing surface, and no npm/PyPI package is published under its name. The tool list below is a CANDIDATE derived from the 68 operations documented in the ADDX Open API reference, so that the shape of a future server is recorded; it is not an agent surface and nothing here can be called today. Input schemas are left null deliberately: the reference documents request bodies as prose and JSON examples rather than as a schema, and ADDX does not publish an OpenAPI document to derive parameters from, so inventing them would be fabrication.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Documentation
Documentation link · transport
Tools
addx_account_info—addx_balance_info—addx_investor_details—addx_portfolio_details—addx_transaction_details—addx_wallet_details—addx_investment_info—addx_investment_fee—addx_confirm_investment—addx_subsequent_investment_info—addx_subsequent_subscription_investment_fee—addx_confirm_subsequent_investment—addx_subsequent_token_info_for_redemption—addx_subsequent_redemption_info—addx_get_subsequent_redemption_fee—addx_confirm_subsequent_redemption_request—addx_investment_info_eam—addx_get_investment_fee_eam—addx_confirm_investment_eam—addx_subsequent_subscription_sto_info_eam—addx_subsequent_subscription_sto_fee_eam—addx_confirm_subsequent_subscription_eam—addx_subsequent_redemption_token_info_eam—addx_subsequent_redemption_info_eam—addx_subsequent_redemption_fee_eam—addx_confirm_subsequent_redemption_eam—addx_sto_list—addx_basic_sto_details—addx_product_details—addx_wallet_filter_details—addx_pending_transactions—addx_historical_transactions—addx_fiat_balances—addx_digital_asset_balances—addx_rewards_balances—addx_portfolio_filters—addx_portfolio_token_holding—addx_portfolio_total_holding—addx_portfolio_percentage_holding—addx_portfolio_tokens—addx_aggregated_order_book—addx_market_depth—addx_market_state—addx_token_list—addx_token_feed—addx_trade_feed—addx_user_balance—addx_available_report_types—addx_get_reports—addx_download_reports—addx_get_bank_accounts—addx_delete_bank_accounts—addx_add_bank_account—addx_edit_bank_account—addx_upload_document—addx_deposit_fiat—addx_withdraw_info—addx_withdraw_otp_request—addx_confirm_withdraw_request—addx_wm_distribute_fiat—addx_wm_collect_fiat—addx_get_digital_balance—addx_get_deposit_address_details—addx_get_applicable_withdrawal_fee—addx_generate_email_otp—addx_generate_mobile_otp—addx_request_identity_verification—addx_confirm_withdraw_request—
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.
Work with this as data
Every MCP server here is available over the APIs.io API and to AI agents over MCP.