Does DriveWealth have an MCP server?

Access is gated to DriveWealth correspondent clients. Production access and timelines go through your DriveWealth relationship manager, and 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, so a connection approved for the API does not automatically cover the MCP endpoint.

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.