# Glide — wallets and US banking (remote · glide.co)

Instant Base + Solana wallets, free and x402-payable. US bank account after a 2-min check.

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `glide.co`: 71/100 (this document), [markdown](https://verifymcp.io/servers/co-glide-banking-connector/api-connector-mcp.md), [page](https://verifymcp.io/servers/co-glide-banking-connector/api-connector-mcp)

## Channel facts

- Endpoint: `https://glide.co/api/connector/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 83/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http co-glide-banking-connector 'https://glide.co/api/connector/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "co-glide-banking-connector": {
      "url": "https://glide.co/api/connector/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-glide-banking-connector": {
      "type": "http",
      "url": "https://glide.co/api/connector/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.co-glide-banking-connector]
url = "https://glide.co/api/connector/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-glide-banking-connector": {
      "type": "remote",
      "url": "https://glide.co/api/connector/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-glide-banking-connector --url 'https://glide.co/api/connector/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-glide-banking-connector:
    url: "https://glide.co/api/connector/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "co-glide-banking-connector": {
      "Transport": "http",
      "Url": "https://glide.co/api/connector/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-glide-banking-connector -t streamable-http -u 'https://glide.co/api/connector/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 71, +17)

- [security improvement] Authorization: unverified → partial
- [security improvement] Transport: fail → pass
- [functional improvement] Stability: unverified → 0.03

### 2026-09-20 (score 54)

First indexed and scored.

## MCP tools (4)

### `create_account` (~162 tokens)

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.

Input parameters:

- `email` (string, required): 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.

### `check_status` (~67 tokens)

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.

Input parameters:

- `onboarding_token` (string, required): The token returned by create_account.

### `get_funding_details` (~86 tokens)

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.

Input parameters:

- `onboarding_token` (string, required): The token returned by create_account.

### `get_wallets` (~92 tokens)

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.

Input parameters:

- `onboarding_token` (string, required): The token returned by create_account.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-glide-banking-connector/api-connector-mcp#diagnostics

## Score history

- 2026-09-21: 71
- 2026-09-20: 54

## Common questions

### 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.

## Links

- Remote endpoint: https://glide.co/api/connector/mcp
- Website: https://glide.co/connector
- Changelog RSS feed: https://verifymcp.io/servers/co-glide-banking-connector/api-connector-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-glide-banking-connector/api-connector-mcp.json
- HTML version of this page: https://verifymcp.io/servers/co-glide-banking-connector/api-connector-mcp