# Quidli Connect (remote · mcp.connect.quid.li)

Resolve social handles to wallets, score onchain reputation, and make agent payments in USDC.

- Trust score: 61/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `mcp.connect.quid.li`: 61/100 (this document), [markdown](https://verifymcp.io/servers/quidli-connect-mcp/mcp.md), [page](https://verifymcp.io/servers/quidli-connect-mcp/mcp)
- npm · `@quidli/connect-mcp`: 67/100, [markdown](https://verifymcp.io/servers/quidli-connect-mcp/quidli-connect-mcp.md), [page](https://verifymcp.io/servers/quidli-connect-mcp/quidli-connect-mcp)

## Channel facts

- Endpoint: `https://mcp.connect.quid.li`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.6.12`

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

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (connect_drop).
  - 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**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1804 tokens (~128/item across 14 items; 14 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**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 75% of tool parameters carry a description.
- **Tool Safety**: 92/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 2 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "connect_drop_balance" implies "drop" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Quidli Connect MCP server?

Quidli Connect is a hosted endpoint at https://mcp.connect.quid.li/, 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 quidli-connect-mcp 'https://mcp.connect.quid.li/'
```

### Cursor

```json
{
  "mcpServers": {
    "quidli-connect-mcp": {
      "url": "https://mcp.connect.quid.li/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "quidli-connect-mcp": {
      "type": "http",
      "url": "https://mcp.connect.quid.li/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.quidli-connect-mcp]
url = "https://mcp.connect.quid.li/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "quidli-connect-mcp": {
      "type": "remote",
      "url": "https://mcp.connect.quid.li/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add quidli-connect-mcp --url 'https://mcp.connect.quid.li/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  quidli-connect-mcp:
    url: "https://mcp.connect.quid.li/"
```

### Netclaw

```json
{
  "McpServers": {
    "quidli-connect-mcp": {
      "Transport": "http",
      "Url": "https://mcp.connect.quid.li/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add quidli-connect-mcp -t streamable-http -u 'https://mcp.connect.quid.li/'
```

### Other

```json
{
  "mcpServers": {
    "quidli-connect-mcp": {
      "type": "http",
      "url": "https://mcp.connect.quid.li/"
    }
  }
}
```

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-10-18 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-17 (score 61)

First indexed and scored.

## MCP tools (14)

### `connect_get_price` (~33 tokens)

Get x402 Prices

Get public x402 list prices for lookup and scores (reference only; live paywall amounts are in 402 responses).

### `connect_get_chains` (~61 tokens)

List Supported Chains

List product chains with per-feature compatibility. lookup is true for EVM catalog chains and Solana; drop is true for Smart Send chains, enabled delegation chains, and Solana (chainId 1399811149 for connect_drop / connect_drop_balance).

### `connect_lookup` (~74 tokens)

Resolve Handle to Wallet

Resolve social identities to EVM and Solana wallet addresses. Resolving a recipient who has no wallet provisions one for them, so this is read-only for the caller but not for the recipient. If status is processing, retry the same payload.

Input parameters:

- `recipients` (array, required): Recipients to resolve to EVM/Solana wallets

### `connect_lookup_exposed` (~101 tokens)

List Exposed Accounts

List platforms a recipient has exposed on Connect, with enriched profile, scores, and wallet addresses. Recipient may be a social account, an exposed wallet (EVM/Solana/smart wallet), or a Connect username. May require x402 payment when the profile owner charges for lookups.

Input parameters:

- `recipient` (object, required): Social identity, exposed wallet (EVM/Solana/smart wallet), or Connect username whose exposed linked accounts and Connect profile should be listed

### `connect_scores_batch` (~73 tokens)

Score Identities (Batch)

Batch scores for linked accounts or Connect usernames. One result per request user. Optional filter sets passedFilter (quidli 0–100, neynar/lens 0–1, ethos 0–2800).

Input parameters:

- `filter` (object)
- `users` (array, required): Users to fetch scores for

### `connect_scores_by_account` (~33 tokens)

Score a Linked Account

Scores for a linked social account or wallet.

Input parameters:

- `identifier` (string, required)
- `platform` (string, required)

### `connect_scores_by_username` (~23 tokens)

Score a Connect Username

Scores by Connect public username.

Input parameters:

- `username` (string, required)

### `connect_me` (~35 tokens)

Get My Connect Profile

Get the Connect profile, scores, and all linked accounts for the API key owner. Use to identify which user the key belongs to.

### `connect_drop` (~768 tokens)

Send Tokens (Smart Send)

Execute a Smart Send from the API key owner Connect embedded wallet. EVM: batch native or ERC-20 (need native gas plus the token). Solana (chainId 1399811149): SOL or SPL from the Solana embedded wallet; packs up to 20 native or 10 SPL recipients per transaction. Social recipient types: email, phone, telegram, discord, farcaster, twitter, github (id or username). linkedin and slack are not on /drop — use connect_lookup first, then type wallet. After connect_lookup, EVM payouts use ethWalletAddress (never solWalletAddress); Solana payouts use solWalletAddress (never ethWalletAddress). Social types on /drop resolve server-side; for type wallet, pass the resolved payout address for the target chain. Omit tokenContract or set it to null for the native token; pass an ERC-20 contract or SPL mint otherwise — do not use the zero address. Amounts are smallest-unit integer strings (ETH 18 decimals, SOL 9, USDC usually 6). Solana native (tokenContract null): no ATA. Sending to a recipient without an existing funded account requires amount ≥ 890880 lamports (rent-exempt minimum for a system account); that SOL stays with the recipient. Below that the tx fails. Sender also pays a ~5000-lamport fee. Solana SPL: tokens sit in Associated Token Accounts (ATA), not on the wallet pubkey. Recipients need not already hold the token — the API prepends CreateIdempotent. The sender (not the recipient) pays ~2039280 lamports (~0.002039 SOL) rent per newly created dest ATA, plus tx fees, on top of the token amount (which can be as small as 1 unit). A 400 "Insufficient funds" on SPL is often missing SOL for ATA rent, not missing USDC. Token-2022 is not supported; USDC mint is EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v. Always call connect_drop_balance first. Returns 201 when submitted or 202 when recipients still processing — retry with the same idempotencyKey.

Input parameters:

- `amountInWeiPerRecipient`: Uniform amount in smallest units. Native ETH uses 18 decimals; SOL uses 9; ERC-20/SPL uses token decimals from connect_drop_balance (USDC usually 6). Omit when setting amountInWei on each recipient.
- `chainId` (integer, required): EVM chain ID or 1399811149 for Solana mainnet
- `idempotencyKey` (string, required)
- `ignoreFailedRecipients` (boolean): When true, send to recipients that resolved successfully and skip failed lookups.
- `recipients` (array, required): Wallet or social recipients (all wallet or all social, no mix). Social types: email, phone, telegram, discord, farcaster, twitter, github (numeric id or username). linkedin and slack are not supporte…
- `tokenContract` (string|null): EVM ERC-20 contract or Solana SPL mint. Omit or null for the native token (ETH/POL/AVAX, or SOL on 1399811149). Do not use the zero address.
- `trustFilter` (object): Keep only recipients in the sender EAS trust graph.

### `connect_drop_balance` (~260 tokens)

Check Smart Send Balance

Get native and token balances for the API key owner embedded wallet. Accepts Smart Send chains and enabled delegation chains. Robinhood Chain (4663) returns ERC-20 balances from Blockscout. Monad (143) returns ERC-20 balances from Moralis; other delegation chains return native plus featured tokens. Always call before connect_drop. Zero balances are omitted, so a missing token means balance 0. EVM: confirm native gas plus the ERC-20 being sent. Solana (chainId 1399811149): SOL in this response is spendable lamports on the wallet pubkey (rent locked in existing token accounts is not included). Native SOL drop to a recipient without an existing funded account: amount itself must be ≥ 890880 lamports and sender SOL must cover amount + ~5000 lamports fee. SPL drop: token balance ≥ total amount, and SOL ≥ tx fee + ~2039280 lamports (~0.002039 SOL) per recipient that may need a new Associated Token Account — even when sending USDC. Insufficient SOL for ATA rent fails before the token transfer.

Input parameters:

- `chainId` (integer, required): EVM chain ID or 1399811149 for Solana mainnet (Smart Send)

### `connect_trust_create` (~127 tokens)

Create Trust Attestation

Create a unidirectional trust attestation on Base (EAS) from the API key owner embedded wallet to a wallet or social identity. Identical active attestations are returned without a new transaction. Requires CONNECT_API_KEY, Smart Send attestation signer enrolled, and ETH on Base for gas.

Input parameters:

- `context` (string): Optional context such as team:quidli
- `expiresIn` (integer): Optional lifetime in seconds
- `level` (integer, required): Trust level 1–100
- `to` (object, required): Identity to trust (wallet, social, or Connect username)

### `connect_trust_revoke` (~77 tokens)

Revoke Trust Attestation

Revoke active trust attestations from the API key owner to a target. Optional context limits which attestations are revoked. Requires CONNECT_API_KEY and ETH on Base.

Input parameters:

- `context` (string): Revoke only this context. Omit to revoke all contexts for the pair.
- `to` (object, required): Identity to untrust

### `connect_trust_check` (~65 tokens)

Check Trust

Check whether identities sit in a trust graph at depth 1. Omit context to match any context.

Input parameters:

- `context` (string): If set, only this context matches
- `from` (object, required): Graph owner
- `targets` (array, required): Identities to test

### `connect_trust_graph` (~74 tokens)

List Trust Edges

List outgoing or incoming trust edges for an identity at depth 1.

Input parameters:

- `context` (string)
- `direction` (string): out = who they trust (default); in = who trusts them
- `identifier` (string, required)
- `platform` (string, required): Identity platform, or username for a Connect username

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/quidli-connect-mcp/mcp#diagnostics

## Score history

- 2026-10-18: 61
- 2026-10-17: 61

## Common questions

### What is the Quidli Connect MCP server?

Quidli Connect is an MCP server listed in the public MCP registry as io.github.Quidli/connect-mcp. Resolve social handles to wallets, score onchain reputation, and make agent payments in USDC. This page covers its hosted endpoint (https://mcp.connect.quid.li).

### Is the Quidli Connect MCP server safe to use?

Quidli Connect scores 61 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 Quidli Connect MCP server expose?

Quidli Connect exposes 14 tools: connect_get_price, connect_get_chains, connect_lookup, connect_lookup_exposed, connect_scores_batch, and 9 more. Their descriptions and schemas cost roughly 1,804 tokens of context every time the server is loaded.

### Does the Quidli Connect MCP server require authentication?

No. We connected to Quidli Connect without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Quidli Connect MCP server still maintained?

Quidli Connect is still listed as active in the MCP registry. We last reached this channel on 18 October 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://mcp.connect.quid.li/
- Repository: https://github.com/Quidli/connect-mcp
- Website: https://connect.quid.li/
- Changelog RSS feed: https://verifymcp.io/servers/quidli-connect-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/quidli-connect-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/quidli-connect-mcp/mcp