Glide — wallets and US banking
REMOTE · GLIDE.CO · SCANNED SEP 21
Instant Base + Solana wallets, free and x402-payable. US bank account after a 2-min check.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 514 tokens (~128/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Glide — wallets and US banking MCP server?
Glide — wallets and US banking is a hosted endpoint at https://glide.co/api/connector/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · glide.co
claude mcp add --transport http co-glide-banking-connector 'https://glide.co/api/connector/mcp'
{
"mcpServers": {
"co-glide-banking-connector": {
"url": "https://glide.co/api/connector/mcp"
}
}
} {
"servers": {
"co-glide-banking-connector": {
"type": "http",
"url": "https://glide.co/api/connector/mcp"
}
}
} [mcp_servers.co-glide-banking-connector] url = "https://glide.co/api/connector/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"co-glide-banking-connector": {
"type": "remote",
"url": "https://glide.co/api/connector/mcp",
"enabled": true
}
}
} openclaw mcp add co-glide-banking-connector --url 'https://glide.co/api/connector/mcp' --transport streamable-http
mcp_servers:
co-glide-banking-connector:
url: "https://glide.co/api/connector/mcp" {
"McpServers": {
"co-glide-banking-connector": {
"Transport": "http",
"Url": "https://glide.co/api/connector/mcp"
}
}
} assistant mcp add co-glide-banking-connector -t streamable-http -u 'https://glide.co/api/connector/mcp'
{
"mcpServers": {
"co-glide-banking-connector": {
"type": "http",
"url": "https://glide.co/api/connector/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 +17
- Authorization: unverified → partial ▲ security
- Transport: fail → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- 20 Sept 26 54
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://glide.co/api/connector/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=glide.co | CN=YE2,O=Let's Encrypt,C=US | 8 Sept 2026 | 7 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5c6d9f090e32aacd8477177247e374fb622 |
| SANs: glide.co | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of glide.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| glide.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://glide.co/api/connector/mcp | Verified | 200 | |
| http (plaintext) | http://glide.co/api/connector/mcp | HTTPS enforced | 308 | https://glide.co/api/connector/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_status ~67
Where the person is in bank verification: awaiting_verification, in_review, approved or declined. Call this after they open the verification link — approval usually takes about two minutes. Their wallets already work regardless of what this says.
| Name | Type | Req | Description |
|---|---|---|---|
| onboarding_token | string | yes | The token returned by create_account. |
No output schema declared.
No examples provided.
create_account ~162
Open a Glide account for a person. Returns their wallets immediately — Base and Solana, both able to receive USDC and both x402-payable — with no 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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The person's email address. Their welcome letter and bank details are sent here. | |
| phone | string | – | Optional phone number in E.164 form, e.g. +14155551234. |
No output schema declared.
No examples provided.
get_funding_details ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| onboarding_token | string | yes | The token returned by create_account. |
No output schema declared.
No examples provided.
get_wallets ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| onboarding_token | string | yes | The token returned by create_account. |
No output schema declared.
No examples provided.
What is the Glide — wallets and US banking MCP server?
Glide — wallets and US banking is an MCP server listed in the public MCP registry as co.glide/banking-connector. Instant Base + Solana wallets, free and x402-payable. US bank account after a 2-min check. This page covers its hosted endpoint (https://glide.co/api/connector/mcp).
Is the Glide — wallets and US banking MCP server safe to use?
Glide — wallets and US banking scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Glide — wallets and US banking MCP server expose?
Glide — wallets and US banking exposes 4 tools: create_account, check_status, get_funding_details, get_wallets. Their descriptions and schemas cost roughly 407 tokens of context every time the server is loaded.
Does the Glide — wallets and US banking MCP server require authentication?
No. We connected to Glide — wallets and US banking without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Glide — wallets and US banking MCP server still maintained?
Glide — wallets and US banking is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.