Glide opens Base and Solana USDC wallets and, after bank verification, exposes US bank funding details so an assistant can help a person receive and move money.
What you can do
Create or reconnect an account and get Base and Solana wallet addresses, each with an x402 endpoint for agent payments in USDC, available immediately without verification or fee. Check where a person stands in bank verification: awaiting verification, in review, approved, declined or unavailable. Retrieve US bank account number and routing number plus the USDC address on Base once verification is approved. On and off ramps are described as free.
When to use it
Use it when someone wants a USDC wallet on Base or Solana right away, wants an agent to be able to pay them, or needs US bank details to fund or cash out after completing identity and bank verification.
Requirements
Remote streamable HTTP endpoint at glide.co. A verified email and a Privy access token supplied in the Authorization Bearer header. Bank verification must be approved before funding details are returned.
Before you install
The server handles financial account data: bank account and routing numbers and wallet addresses. It requires a Privy access token in the Authorization header, which is a credential to protect. Account creation and verification involve a real person's identity and banking details, and moving balances into a bank account is described as the paid step. Treat verification status and funding details as sensitive.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/co.glide%2Fbanking-connector/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Sign in to Glide with a verified email and supply the Privy access token in the Authorization: Bearer header to open or reconnect your account. Returns your wallets immediately — Base and Solana, both able to receive USDC and both x402-payable — with no additional banking verification and no fee. Also returns a verification link, which is optional and only needed for bank rails (a US account, USD, EUR and other currencies); it is usually approved in about two minutes. Safe to call twice with the same email: it returns the same account rather than making a second one. Returns an onboarding_token — keep it, every later call needs it.
Parametersemailrequiredphone
check_status
Check verification status
Where the person is in bank verification: awaiting_verification, in_review, approved, declined or unavailable (temporarily unavailable — tell them to contact support, do not speculate why). Call this after they open the verification link — approval usually takes about two minutes. Their wallets already work regardless of what this says.
Parametersonboarding_tokenrequired
get_funding_details
Get US bank and USDC funding details
The US bank account — account number and routing number — plus the USDC address on Base. This is the banking half, so it needs verification to be approved; before that it refuses. On and off ramps are free. For a wallet address that works right now, without verification, use get_wallets.
Parametersonboarding_tokenrequired
get_wallets
Get wallet addresses and x402 endpoints
The person's Base and Solana wallet addresses, plus the x402 endpoint on each chain that lets any agent pay them in USDC. Works from the moment the account exists: no verification, no fee, nothing to set up. Receiving is free and unlimited; moving the balance into a US or EUR bank account is the part that needs verification.
Parametersonboarding_tokenrequired
Version history
1
v1.1.0LatestSep 20, 2026
Score
83%
83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.