Skip to main content
Glama
Quidli Connect MCP

Quidli Connect MCP

Official

Quidli Connect MCP

npm version npm downloads license

Open payments for multiplayer agents, powered by onchain reputation. Resolve a social handle to a wallet, check its onchain reputation, and send tokens — from Cursor, Claude Desktop, Claude Code, or any MCP-compatible client.

Multiplayer means parties who don't already know each other — an agent paying a person, or another agent, with no prior relationship and no account to fall back on. Connect is how it verifies who it's dealing with before sending anything.

Public repository: github.com/Quidli/connect-mcp

Try it in one command

No API key required.

Claude Code:

claude mcp add --transport http quidli https://mcp.connect.quid.li/

Cursor: Add to Cursor (or paste that link into Settings → MCP → Add new MCP server)

Claude Desktop: Settings → Connectors → Add custom connector, URL https://mcp.connect.quid.li

Local (any client) — runs on your machine instead of the hosted endpoint:

npx -y @quidli/connect-mcp

See Choose how to connect below for API keys, x402 wallet pay-per-call, and full config snippets.

Then ask your agent:

Resolve the GitHub handle justinquidli to a wallet.

{
  "status": "completed",
  "results": [
    {
      "type": "github",
      "value": "justinquidli",
      "ethWalletAddress": "0x6a48ADE3bE3F9f0b8B4c9af61Bb654A219311699",
      "solWalletAddress": "8vo1awED98mwqDa4qR9JyMsk7qJYiwnTSG4EnXGyWXRh"
    }
  ]
}

Resolves across GitHub, X, Telegram, Discord, LinkedIn, Farcaster, email and phone — and generates a wallet for people who have never used Quidli.

Then score what you find: connect_scores_batch returns onchain reputation for a batch of identities.

Lookup, scores, and price run without a key under a shared anonymous quota. Add a Connect API key for higher limits, your own profile (connect_me), and Smart Send.


Related MCP server: MCPAGENT

Choose how to connect

Hosted (mcp.connect.quid.li)

Local (npx @quidli/connect-mcp)

Setup

Add a URL in MCP settings

Run a local process via npx

Auth

Optional API key. Without a key: lookup/scores under a shared anonymous quota; price/chains are public

API key, x402 pay-per-call, or none for lookup/scores

Pros

No install; try without a key; always on Quidli infrastructure

Wallet private key never leaves your machine; pay per call with USDC instead of an API key

Cons

Anonymous traffic shares a global rate limit; no pay-per-call billing

Requires Node.js 20+; npx may download the package on first run

Limitations

Cannot use x402 / wallet auth — do not send a private key to the hosted endpoint

x402 mode needs USDC on Base (mainnet 8453); connect_drop requires an API key

Get a Connect API key at connect.quid.li → Enable API access for higher limits, connect_me, and Smart Send.


Zero local setup. Lookup, scores, and price work without an API key (shared anonymous quota). Add a key for higher limits, your profile (connect_me), and Smart Send.

Cursor

If you already have other MCP servers: skip the deeplink and add manually — the one-click install can overwrite your entire mcp.json in some Cursor versions.

Add to Cursor

Or paste into Cursor Settings → MCP → Add new MCP server:

cursor://anysphere.cursor-deeplink/mcp/install?name=quidli-connect&config=eyJ1cmwiOiJodHRwczovL21jcC5jb25uZWN0LnF1aWQubGkifQ==

Add manually {#cursor-manual}

Merge this into ~/.cursor/mcp.json (global) or .cursor/mcp.json (project) under mcpServers — do not replace your existing entries:

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

Optional — higher limits and Smart Send:

"quidli-connect": {
  "url": "https://mcp.connect.quid.li",
  "headers": {
    "x-api-key": "<your-connect-api-key>"
  }
}

Claude Desktop

  1. Open Claude → Settings → Connectors (or Settings → Developer → Edit Config on older versions).

  2. Add a custom MCP connector with URL https://mcp.connect.quid.li. Optionally set header x-api-key: <your-connect-api-key>.

Or merge this into your config file and restart Claude:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

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

If your Claude version does not support remote url connectors, use the local bridge instead (still hosted API, runs a small local helper):

{
  "mcpServers": {
    "quidli-connect": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "--http",
        "https://mcp.connect.quid.li"
      ]
    }
  }
}

Requires Node.js 20+ for the bridge. Restart Claude Desktop after saving. You should see a hammer icon in the chat input when tools are available.

Without a key, initialize / tools/list always succeed. Anonymous tools/call share a global quota (HTTP 429 when exceeded — get a key for higher limits). Placeholder keys still return 401.


Grok

  1. Go to grok.com/connectors and select Custom.

  2. Enter the server URL: https://mcp.connect.quid.li

This gives Grok access to the anonymous-tier tools -- lookup, scores, and price -- under the shared quota.

Current limitation: Grok's custom connector UI does not currently support attaching an API key or custom header. That means connect_me, connect_drop, and connect_drop_balance (all API key only) are not usable through Grok yet -- calls to them will return an unauthorized error. This isn't a connect-mcp limitation; it's Grok's custom-connector setup not exposing an auth field at this time.


Smithery

If you already use Smithery, it will handle auth and sessions for you. Requires a Smithery account.

npx smithery login
npx smithery mcp add quidli/connect

Local (stdio)

Best if you want pay-per-call with a wallet, or prefer credentials in a local env file.

Requires Node.js 20+.

Cursor

Add one of the following to .cursor/mcp.json (project) or your global MCP settings.

Option A — API key

Same billing model as hosted; credentials stay on your machine.

{
  "mcpServers": {
    "quidli-connect": {
      "command": "npx",
      "args": ["-y", "@quidli/connect-mcp"],
      "env": {
        "CONNECT_API_KEY": "<your-connect-api-key>",
        "CONNECT_API_BASE_URL": "https://api.connect.quid.li"
      }
    }
  }
}

Option B — x402 pay-per-call (wallet)

No API key. Authenticated calls pay automatically when the API returns HTTP 402. Your wallet private key is only read by the local process.

{
  "mcpServers": {
    "quidli-connect": {
      "command": "npx",
      "args": ["-y", "@quidli/connect-mcp"],
      "env": {
        "EVM_PRIVATE_KEY": "0x<wallet-with-usdc-on-base>",
        "CONNECT_API_BASE_URL": "https://api.connect.quid.li",
        "CONNECT_X402_EVM_NETWORK": "8453"
      }
    }
  }
}

Use 84532 for Base Sepolia when pointing at a staging API.

Option C — no credentials (lookup / scores)

The MCP process starts without CONNECT_API_KEY or EVM_PRIVATE_KEY. connect_lookup, connect_scores_*, connect_get_price, and connect_get_chains call the API without auth. That succeeds when x402 is disabled (price 0, typical for local). On production with x402 enabled, those tools return HTTP 402 until you set a key or wallet.

connect_me, connect_drop, and connect_drop_balance still require CONNECT_API_KEY.

{
  "mcpServers": {
    "quidli-connect": {
      "command": "npx",
      "args": ["-y", "@quidli/connect-mcp"],
      "env": {
        "CONNECT_API_BASE_URL": "http://127.0.0.1:3011"
      }
    }
  }
}

Claude Desktop

  1. Open Claude → Settings → Developer → Edit Config (enable Developer mode first if you do not see it).

  2. Merge one of the blocks below into mcpServers in:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

  1. Restart Claude Desktop.

Option A — API key

{
  "mcpServers": {
    "quidli-connect": {
      "command": "npx",
      "args": ["-y", "@quidli/connect-mcp"],
      "env": {
        "CONNECT_API_KEY": "<your-connect-api-key>",
        "CONNECT_API_BASE_URL": "https://api.connect.quid.li"
      }
    }
  }
}

Option B — x402 pay-per-call (wallet)

{
  "mcpServers": {
    "quidli-connect": {
      "command": "npx",
      "args": ["-y", "@quidli/connect-mcp"],
      "env": {
        "EVM_PRIVATE_KEY": "0x<wallet-with-usdc-on-base>",
        "CONNECT_API_BASE_URL": "https://api.connect.quid.li",
        "CONNECT_X402_EVM_NETWORK": "8453"
      }
    }
  }
}

If both CONNECT_API_KEY and EVM_PRIVATE_KEY are set, the API key is used.

Credentials are optional in local mode. Without either variable, lookup/scores still work when the API does not charge x402. connect_me and Smart Send tools require CONNECT_API_KEY.


Troubleshooting

npx hangs with no output when run from a background service

If you're launching @quidli/connect-mcp via npx from inside a background process manager -- a macOS launchd agent, a systemd unit, a supervisor, or any client config running without a normal interactive shell -- it can hang indefinitely with zero output and no error. This isn't a crash; npx is stuck resolving PATH in an environment that doesn't provide the same shell initialization an interactive terminal gets.

Workaround: if you have Bun installed, use bunx instead of npx. It performs the same job -- running the package without a local install -- but doesn't hit this hang in restricted-PATH environments.

{
  "mcpServers": {
    "quidli-connect": {
      "command": "bunx",
      "args": ["-y", "@quidli/connect-mcp"],
      "env": {
        "CONNECT_API_KEY": "your-api-key"
      }
    }
  }
}

If you're spawning the process yourself (rather than through a client's MCP config) and want to be resilient to bunx not being on PATH either, resolve it by absolute path first:

import { spawn } from "node:child_process";
import { existsSync } from "node:fs";
import { homedir } from "node:os";
import { join } from "node:path";

const BUNX_PATH = (() => {
  const candidate = join(homedir(), ".bun", "bin", "bunx");
  return existsSync(candidate) ? candidate : "bunx";
})();

const proc = spawn(BUNX_PATH, ["-y", "@quidli/connect-mcp"], {
  stdio: ["pipe", "pipe", "pipe"],
});

This isn't a general claim that Bun is better than npm -- it's a targeted fix for one specific, reproducible failure mode when npx is spawned outside an interactive shell.

Wrong environment variable name for the API key

Double-check you're setting CONNECT_API_KEY, not API_KEY -- the server only reads CONNECT_API_KEY, and a mismatch here fails silently: your calls will run in anonymous/unauthenticated mode instead of erroring, which can look like a working-but-oddly-limited connection rather than a config mistake.

Supported chains

connect_get_chains (REST: GET /chains) is the source of truth and needs no key. As of 2026-11-07 it lists these mainnets, each with lookup and drop enabled:

Chain

Chain ID

Native token

Ethereum

1

ETH

Base

8453

ETH

Polygon

137

POL

OP Mainnet

10

ETH

Arbitrum One

42161

ETH

Avalanche

43114

AVAX

World Chain

480

ETH

Monad

143

MON

Arc

5042

USDC

Robinhood Chain

4663

ETH

Solana

1399811149

SOL

World Chain Sepolia (4801) is also listed, as a testnet.

  • Social handles resolve on every chain: EVM chains pay the recipient's ethWalletAddress, Solana pays their solWalletAddress.

  • connect_drop sends native tokens when tokenContract is omitted. For an ERC-20 or SPL token you pass its contract address or mint.

  • On Arc (5042) the native token is USDC, not ETH. Omitting tokenContract there sends USDC.

  • Balance coverage depends on the chain. connect_drop_balance returns the native balance everywhere. ERC-20 balances come from a per-chain provider: Moralis on Monad and Base, Blockscout on Robinhood Chain, and other chains may return only native plus featured tokens. Zero balances are omitted, spam tokens can appear, and a token the provider doesn't index can be missing. If you know its contract address you can still send it by passing tokenContract.

Tools

Tool

What it does

connect_get_price

List reference prices (no auth)

connect_get_chains

List supported chains and feature compatibility (no auth)

connect_lookup

Resolve social identities to EVM and SOL wallet addresses

connect_lookup_exposed

List platforms a recipient has exposed on Connect

connect_scores_batch

Batch scores for accounts or usernames

connect_scores_by_account

Scores for one linked account

connect_scores_by_username

Scores by Connect username

connect_me

API key owner profile, scores, and linked accounts — API key only

connect_drop

Smart Send (EVM batch, Solana SOL/SPL, or ERC-721/ERC-1155 NFTs); accepts trustFilter to gate recipients by trust graph — API key only

connect_drop_balance

Smart Send wallet balances on a chain — API key only. Token coverage varies by chain, see Supported chains

connect_trust_create

Create one or more on-chain trust attestations in one EAS transaction (Base) — API key only

connect_trust_check

Check whether identities sit in a trust graph at depth 1

connect_trust_graph

List outgoing/incoming trust edges for an identity

connect_trust_revoke

Revoke active trust attestations by target — API key only

Ask your client to use these tools when you need Connect data or actions.

Sending NFTs

connect_drop sends ERC-721 and ERC-1155 tokens on EVM chains, in the same call shape as a token send. Set tokenStandard and put the ids on the recipients.

One NFT per recipient (ERC-721)

Set tokenStandard to erc721, tokenContract to the collection, and tokenId on every recipient. Do not pass an amount. Connect issues one safeTransferFrom per NFT.

{
  "chainId": 8453,
  "tokenStandard": "erc721",
  "tokenContract": "0xYourCollection",
  "recipients": [
    { "type": "farcaster", "username": "alice", "tokenId": "1" },
    { "type": "twitter", "username": "bob", "tokenId": "2" }
  ]
}

Quantities of one id (ERC-1155)

Set tokenStandard to erc1155, and give every recipient both tokenId and tokenAmount (at least 1). The same id can go to several recipients.

{
  "chainId": 8453,
  "tokenStandard": "erc1155",
  "tokenContract": "0xYourContract",
  "recipients": [
    { "type": "farcaster", "username": "alice", "tokenId": "7", "tokenAmount": "3" },
    { "type": "github", "username": "bob", "tokenId": "7", "tokenAmount": "1" }
  ]
}

Notes:

  • tokenId and tokenAmount are decimal integer strings, like the amounts on a token send.

  • Omit tokenStandard entirely for native, ERC-20 and SPL sends. Nothing about those changes.

  • An EIP-7702 delegation signed before the matching standard has to be replaced first, and a Smart Send wallet enrolled under the previous Privy policy has to re-enable Smart Send.

  • NFT sends are API key only, and connect_get_chains remains the source of truth for which chains accept a drop.

Trust graph

Connect writes trust attestations on Base via EAS. An attestation is unidirectional — you vouch for someone — and anyone can verify it without asking Connect, because it lives onchain rather than in a Quidli database.

Vouch for people

connect_trust_create takes up to 50 identities and attests them in a single transaction, so gas is paid once rather than per person. level (1–100), context and expiresIn apply to every entry in the batch.

{
  "to": [
    { "type": "github",    "username": "alice" },
    { "type": "farcaster", "username": "bob"   },
    { "type": "wallet",    "id": "0x1234..."   }
  ],
  "level": 80,
  "context": "team:quidli"
}

Identical active attestations are returned without submitting a new transaction. Recipients still being provisioned come back as processing while the rest are attested.

Requires an API key, the Smart Send attestation signer enrolled, and ETH on Base for gas when a new attestation is submitted.

Pay only people you trust

connect_drop accepts a trustFilter that keeps recipients inside the sender's trust graph:

{ "trustFilter": { "mode": "skip", "context": "team:quidli" } }

require fails the drop if any recipient is outside the graph; skip pays the ones inside it and drops the others. Omit context to match any context.

Read and revoke

connect_trust_check reports whether identities sit in a trust graph at depth 1. connect_trust_graph lists outgoing or incoming edges for an identity. connect_trust_revoke revokes active attestations to a target, optionally scoped by context.

Contributing

This repository is a read-only mirror, regenerated on every release — changes committed here are overwritten. Please open an issue rather than a pull request. See CONTRIBUTING.md.

Available Tools

14 tools
connect_dropSend Tokens (Smart Send)A
DestructiveIdempotent
Inspect

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.

Inputs: chainId (required), recipients (required), idempotencyKey (required), trustFilter, +3 more.

connect_drop_balanceCheck Smart Send BalanceA
Read-onlyIdempotent
Inspect

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.

Inputs: chainId (required).

connect_get_chainsList Supported ChainsA
Read-onlyIdempotent
Inspect

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

Inputs: no named parameters.

connect_get_priceGet x402 PricesA
Read-onlyIdempotent
Inspect

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

Inputs: no named parameters.

connect_lookupResolve Handle to WalletA
Read-onlyIdempotent
Inspect

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.

Inputs: recipients (required).

connect_lookup_exposedList Exposed AccountsA
Read-onlyIdempotent
Inspect

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.

Inputs: recipient (required).

connect_meGet My Connect ProfileA
Read-onlyIdempotent
Inspect

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

Inputs: no named parameters.

connect_scores_batchScore Identities (Batch)A
Read-onlyIdempotent
Inspect

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

Inputs: users (required), filter.

connect_scores_by_accountScore a Linked AccountC
Read-onlyIdempotent
Inspect

Scores for a linked social account or wallet.

Inputs: platform (required), identifier (required).

connect_scores_by_usernameScore a Connect UsernameC
Read-onlyIdempotent
Inspect

Scores by Connect public username.

Inputs: username (required).

connect_trust_checkCheck TrustB
Read-onlyIdempotent
Inspect

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

Inputs: from (required), targets (required), context.

connect_trust_createCreate Trust AttestationA
DestructiveIdempotent
Inspect

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.

Inputs: to (required), level (required), context, expiresIn.

connect_trust_graphList Trust EdgesB
Read-onlyIdempotent
Inspect

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

Inputs: platform (required), identifier (required), context, direction.

connect_trust_revokeRevoke Trust AttestationA
DestructiveIdempotent
Inspect

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.

Inputs: to (required), context.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 14 tools

    Disambiguation3/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI tools to interact with the Lens Protocol decentralized social network ecosystem. Supports fetching profiles, posts, followers, searching content, and accessing social graph data through standardized MCP interfaces.
      4
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to interact with AgentGram, the social network for AI agents, through native MCP tools for posting, commenting, voting, and managing identity.
      22
      22 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides a trust layer for AI agents with identity, reputation, payments, and discovery via 92 API endpoints as MCP tools, leveraging Nostr-native infrastructure.
      MIT