Official MCP gateway to DriveWealth's embedded-investing APIs and API documentation: instruments, accounts, positions and order execution for brokerage correspondent clients. Connect once to the MCP endpoint instead of building a REST wrapper for each AI client. The infrastructure layer underneath many fintech and digital-wealth investing apps.
Provides one system's data and actions. Reads and writes inside a single product of record; it can act, but only within its own walls. More on System servers →All seven roles →
Access is gated to DriveWealth correspondent clients. Production access and timelines go through your DriveWealth relationship manager; the sandbox (UAT) is the place to watch an agent behave first.
Auth uses a bearer token from DriveWealth's existing back-office auth flow, and permissions are enforced per tool. MCP IP allowlisting is separate from API IP allowlisting.
The server exposes execution endpoints but performs no suitability, KYC or AML checks at the point of order. Your firm owns the written supervisory procedures governing AI agents that use it.
Start with read-only scopes and keep client-side approval prompts on for any order-placing tool until the connection is proven.
Rate this server
How to connect DriveWealth
Step 1
Remote server: paste a URL
DriveWealth publishes a remote (Streamable HTTP) endpoint, so nothing is installed locally. Add it as a custom connector in Claude, ChatGPT or your IDE and paste the endpoint below.
Pass a bearer token issued by the vendor's existing API in your client's Authorization header. Check how long the token lives and how it renews, and start with the narrowest scopes available.
Step 3
Verify, then widen access
Restart your client, confirm the server's tools appear, and run one read-only question first. Keep client-side approval prompts on for any tool that can write, trade or send. Confirm with your firm's compliance policy before connecting systems holding client data.
Prepare, do not stage or submit, a proposed rebalance for <account>. Take targets and current positions from the wealth platform, then use the brokerage or execution tools read-only to check tradability for each name: current quote, lot sizes, restrictions and anything that cannot be traded as intended. Show symbol, side, quantity, estimated value, rationale tied to the target model, and a tradability note with its source. Note cash impact and any position that would breach a restriction. Stop and show me the blotter for explicit approval before any order is created anywhere.
Guardrail · Proposal only. Keep trade approvals on; no order should exist without your say-so.
Post-trade reconciliation
Confirm fills matched intent, with breaks flagged.
Read-only: reconcile yesterday's executed trades against the intended blotter for <account or household>. Show intended vs. filled quantity and price, unfilled or partially filled orders, and any unexpected trade. Mask account numbers to the last four digits. Do not cancel, resubmit or correct anything, list the breaks for me to handle.
Guardrail · Read-only. Breaks get resolved by a human through the system of record.
Digital asset holdings snapshot
One consolidated view across exchanges and wallets.
Crypto & Digital AssetsCrypto & Digital AssetsBrokerage & Trade Execution
Read-only: consolidate my digital asset holdings across every connected source, exchange accounts, on-chain wallet or explorer tools, and any brokerage account holding crypto or crypto ETPs, into one table: asset, quantity, venue, source tool, USD value and share of total. Show a per-source subtotal so I can see which tool reported what, and flag any asset that appears in more than one source so it is not double-counted. Mask wallet addresses beyond the first and last four characters. Do not trade, transfer, approve or sign anything.
Guardrail · Read-only keys only. Never give a chat tool withdrawal or signing permissions.
