Quidli Connect MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONNECT_API_KEY | No | Connect API key for higher limits, connect_me, and Smart Send tools. | |
| EVM_PRIVATE_KEY | No | Wallet private key for x402 pay-per-call authentication. Must have USDC on Base. | |
| CONNECT_API_BASE_URL | No | Base URL of the Connect API. | https://api.connect.quid.li |
| CONNECT_X402_EVM_NETWORK | No | EVM network ID for x402 (8453 for Base mainnet, 84532 for Base Sepolia). | 8453 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| connect_get_priceA | Get public x402 list prices for lookup and scores (reference only; live paywall amounts are in 402 responses). |
| connect_get_chainsA | 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_lookupA | 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. |
| connect_lookup_exposedA | 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. |
| connect_scores_batchA | 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). |
| connect_scores_by_accountC | Scores for a linked social account or wallet. |
| connect_scores_by_usernameC | Scores by Connect public username. |
| connect_meA | Get the Connect profile, scores, and all linked accounts for the API key owner. Use to identify which user the key belongs to. |
| connect_dropA | 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. |
| connect_drop_balanceA | 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. |
| connect_trust_createA | 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. |
| connect_trust_revokeA | 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. |
| connect_trust_checkB | Check whether identities sit in a trust graph at depth 1. Omit context to match any context. |
| connect_trust_graphB | List outgoing or incoming trust edges for an identity at depth 1. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Several clusters overlap: connect_scores_batch covers both linked accounts and usernames, making connect_scores_by_username and connect_scores_by_account largely redundant; connect_lookup and connect_lookup_exposed both return wallet/profile data; and connect_trust_graph and connect_trust_check both query depth-1 trust. Descriptions clarify inputs and outputs, but an agent could still misselect within these clusters.
All tools use a consistent connect_ prefix and snake_case, with mostly predictable domain/action names such as connect_trust_create and connect_drop_balance. Minor deviations like connect_me and connect_lookup_exposed are readable but slightly less formulaic than the rest.
14 tools fit the multi-feature scope of identity lookup, scores, trust, and drops without becoming overwhelming. A few score and trust query variants could be consolidated, but the count is reasonable for the surface area.
Core workflows are covered: lookup/profile, scores, trust graph and attestations, chain metadata, balances, and drops. Minor gaps exist around managing linked accounts or checking delayed drop status, but agents can work around them via retries and existing lookups.