Glide — wallets and US banking MCP server
co.glide/banking-connectorglide.costreamable-httpv1.1.0Scanned
Instant Base + Solana wallets, free and x402-payable. US bank account after a 2-min check.
4 tools: 2 change things and 2 only read.
- Reads private data · 1
- Reads text others write · 4
- Can send data out · 1
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Glide — wallets and US banking MCP server can do
The Glide — wallets and US banking MCP server is published by glide.co, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: create_account and get_funding_details), but cannot delete data. 2 tools only read.
1 tool reads private data (check_status); 4 tools bring in text other people can write (create_account, check_status, get_funding_details and 1 more); 1 tool can send data out of your system (create_account). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 12, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 2Claude Code: ask
create_accountSign in to Glide with a verified email and supply the Privy access token in the Authorization: Bearer header to open or reconnect your account.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "create_account" says "create": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.phone): what the tool writes goes there.
Description, as the server wrote it 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.
Annotations the server declares
- title: Open a Glide account
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_funding_detailsThe US bank account — account number and routing number — plus the USDC address on Base.Reads text others write1 finding
Why it is in this group
- The name "get_funding_details" says "get": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "get_funding_details" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "get_funding_details" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get US bank and USDC funding details
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 2Show 2 read-only tools
check_statusWhere the person is in bank verification: awaiting_verification, in_review, approved, declined or unavailable (temporarily unavailable — tell them to contact support, do not specul…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "check_status" says "status": a word for reading.
What it can reach
- private-dataThe description's first sentence says "contact": it reads contacts.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check verification status
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_walletsThe person's Base and Solana wallet addresses, plus the x402 endpoint on each chain that lets any agent pay them in USDC.Reads text others writeNo findings
Why it is in this group
- The name "get_wallets" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get wallet addresses and x402 endpoints
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
4 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__banking-connector__create_account"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:32 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://glide.co/api/connector/mcp: tools/list returned 4 tools to an anonymous client, including create_account (write), get_funding_details (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "get_funding_details" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "get_funding_details" says "get": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http banking-connector https://glide.co/api/connector/mcpclaude mcp add --transport http banking-connector https://glide.co/api/connector/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__banking-connector__check_status",
"mcp__banking-connector__get_wallets"
],
"ask": [
"mcp__banking-connector__create_account",
"mcp__banking-connector__get_funding_details"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as banking-connector. Review it before you use it.
Capability tags behind 4 rules
- mcp__banking-connector__create_account untrusted-input, outbound
- mcp__banking-connector__check_status private-data, untrusted-input
- mcp__banking-connector__get_funding_details untrusted-input
- mcp__banking-connector__get_wallets untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/co.glide/banking-connector/verify?hash=320be9a246837df66be55ccacc58fb59c8d20dffab62bfb9db8c3299e9b01b22" | jq -e '.changed == false'Pinned hash 320be9a24683, from Nov 12, 2026, 10:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/co.glide/banking-connector/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/co.glide/banking-connector)Source: MCP Registry. Synced Oct 21, 2026, 17:46 UTC.
Glide — wallets and US banking MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Glide — wallets and US banking MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Glide — wallets and US banking MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Glide — wallets and US banking MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Glide — wallets and US banking MCP server have?
- 4 tools: 2 write, 2 read. create_account, get_funding_details, check_status and get_wallets.
Does the Glide — wallets and US banking MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Glide — wallets and US banking MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_account.
Has the Glide — wallets and US banking MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.