Quidli Connect

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

¿Debería usar esto?

Calidad de la descripción

98%

Integridad del esquema

80%

Calidad de los nombres

80%

Riesgo de envenenamiento

80%

Coincidencia de permisos

100%

Cumplimiento del protocolo

100%

Hallazgos (3)

HIGHTool poisoning patterns detected
MEDIUMTool description contains suspicious base64-like encoded stringen connect_drop
LOWTool 'connect_scores_by_username' description lacks action verben connect_scores_by_username

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~3,628Tokens (definiciones de herramientas)

~1.6 KBTamaño de respuesta típico

Impacto significativo en la atención (2.83% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

{
  "mcpServers": {
    "connect-mcp": {
      "command": "npx",
      "args": [
        "@quidli/connect-mcp"
      ]
    }
  }
}

Paquetes ejecutables

npm@quidli/connect-mcp0.6.12stdio

Puntos de conexión remotos

https://mcp.connect.quid.listreamable-http

Qué puede hacer

Inventario de herramientas

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

Esquema de entrada

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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

Esquema de entrada

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "recipients": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "type": {
            "type": "string",
            "enum": [
              "email",
              "phone",
              "telegram",
              "discord",
              "farcaster",
              "twitter",
              "github",
              "linkedin",
              "slack"
            ]
          },
          "id": {
            "type": "string"
          },
          "username": {
            "type": "string"
          }
        },
        "required": [
          "type"
        ],
        "additionalProperties": true
      },
      "minItems": 1,
      "description": "Recipients to resolve to EVM/Solana wallets"
    }
  },
  "required": [
    "recipients"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "recipient": {
      "type": "object",
      "properties": {
        "type": {
          "type": "string",
          "enum": [
            "email",
            "phone",
            "telegram",
            "discord",
            "farcaster",
            "twitter",
            "github",
            "linkedin",
            "slack",
            "wallet",
            "username"
          ]
        },
        "id": {
          "type": "string"
        },
        "username": {
          "type": "string"
        }
      },
      "required": [
        "type"
      ],
      "additionalProperties": true,
      "description": "Social identity, exposed wallet (EVM/Solana/smart wallet), or Connect username whose exposed linked accounts and Connect profile should be listed"
    }
  },
  "required": [
    "recipient"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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

Esquema de entrada

{
  "type": "object",
  "properties": {
    "users": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "type": {
            "type": "string",
            "enum": [
              "email",
              "phone",
              "telegram",
              "discord",
              "farcaster",
              "twitter",
              "github",
              "linkedin",
              "slack",
              "wallet",
              "username"
            ]
          },
          "id": {
            "type": "string"
          },
          "username": {
            "type": "string"
          }
        },
        "required": [
          "type"
        ],
        "additionalProperties": true
      },
      "minItems": 1,
      "description": "Users to fetch scores for"
    },
    "filter": {
      "type": "object",
      "properties": {
        "type": {
          "type": "string",
          "enum": [
            "quidli_score",
            "lens_score",
            "neynar_score",
            "ethos_twitter_reputation",
            "ethos_wallet_reputation"
          ]
        },
        "minScore": {
          "type": "number",
          "description": "quidli_score: 0–100; neynar/lens: 0–1; ethos_twitter/wallet: 0–2800"
        }
      },
      "required": [
        "type",
        "minScore"
      ],
      "additionalProperties": false
    }
  },
  "required": [
    "users"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Scores for a linked social account or wallet.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "platform": {
      "type": "string",
      "enum": [
        "wallet",
        "email",
        "phone",
        "telegram",
        "discord",
        "farcaster",
        "twitter",
        "github",
        "linkedin",
        "slack"
      ]
    },
    "identifier": {
      "type": "string",
      "minLength": 1
    }
  },
  "required": [
    "platform",
    "identifier"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Scores by Connect public username.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "username": {
      "type": "string",
      "minLength": 1
    }
  },
  "required": [
    "username"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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

Esquema de entrada

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "idempotencyKey": {
      "type": "string",
      "format": "uuid"
    },
    "chainId": {
      "type": "integer",
      "description": "EVM chain ID or 1399811149 for Solana mainnet"
    },
    "tokenContract": {
      "type": [
        "string",
        "null"
      ],
      "description": "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."
    },
    "recipients": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "type": {
            "type": "string",
            "enum": [
              "email",
              "phone",
              "telegram",
              "discord",
              "farcaster",
              "twitter",
              "github",
              "wallet"
            ]
          },
          "id": {
            "type": "string"
          },
          "username": {
            "type": "string"
          }
        },
        "required": [
          "type"
        ],
        "additionalProperties": true
      },
      "minItems": 1,
      "description": "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 supported — use connect_lookup first, then type wallet. Optional amountInWei per recipient uses the same smallest-unit rules as amountInWeiPerRecipient. On EVM, wallet ids are 0x addresses; on Solana, base58 pubkeys. Social lookup payouts use ethWalletAddress on EVM and solWalletAddress on Solana."
    },
    "amountInWeiPerRecipient": {
      "anyOf": [
        {
          "anyOf": [
            {
              "not": {}
            },
            {
              "type": "string"
            }
          ]
        },
        {
          "type": "null"
        }
      ],
      "description": "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."
    },
    "ignoreFailedRecipients": {
      "type": "boolean",
      "description": "When true, send to recipients that resolved successfully and skip failed lookups."
    },
    "trustFilter": {
      "type": "object",
      "properties": {
        "context": {
          "type": "string",
          "description": "Restrict to this trust context. Omit to match any."
        },
        "mode": {
          "type": "string",
          "enum": [
            "require",
            "skip"
          ],
          "description": "require = fail if anyone is outside the graph; skip = drop them"
        }
      },
      "required": [
        "mode"
      ],
      "additionalProperties": false,
      "description": "Keep only recipients in the sender EAS trust graph."
    }
  },
  "required": [
    "idempotencyKey",
    "chainId",
    "recipients"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "chainId": {
      "type": "integer",
      "description": "EVM chain ID or 1399811149 for Solana mainnet (Smart Send)"
    }
  },
  "required": [
    "chainId"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "to": {
      "type": "object",
      "properties": {
        "type": {
          "type": "string",
          "enum": [
            "email",
            "phone",
            "telegram",
            "discord",
            "farcaster",
            "twitter",
            "github",
            "linkedin",
            "slack",
            "wallet",
            "username"
          ]
        },
        "id": {
          "type": "string"
        },
        "username": {
          "type": "string"
        }
      },
      "required": [
        "type"
      ],
      "additionalProperties": true,
      "description": "Identity to trust (wallet, social, or Connect username)"
    },
    "level": {
      "type": "integer",
      "minimum": 1,
      "maximum": 100,
      "description": "Trust level 1–100"
    },
    "context": {
      "type": "string",
      "maxLength": 64,
      "description": "Optional context such as team:quidli"
    },
    "expiresIn": {
      "type": "integer",
      "exclusiveMinimum": 0,
      "description": "Optional lifetime in seconds"
    }
  },
  "required": [
    "to",
    "level"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "to": {
      "type": "object",
      "properties": {
        "type": {
          "type": "string",
          "enum": [
            "email",
            "phone",
            "telegram",
            "discord",
            "farcaster",
            "twitter",
            "github",
            "linkedin",
            "slack",
            "wallet",
            "username"
          ]
        },
        "id": {
          "type": "string"
        },
        "username": {
          "type": "string"
        }
      },
      "required": [
        "type"
      ],
      "additionalProperties": true,
      "description": "Identity to untrust"
    },
    "context": {
      "type": "string",
      "maxLength": 64,
      "description": "Revoke only this context. Omit to revoke all contexts for the pair."
    }
  },
  "required": [
    "to"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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

Esquema de entrada

{
  "type": "object",
  "properties": {
    "from": {
      "type": "object",
      "properties": {
        "type": {
          "type": "string",
          "enum": [
            "email",
            "phone",
            "telegram",
            "discord",
            "farcaster",
            "twitter",
            "github",
            "linkedin",
            "slack",
            "wallet",
            "username"
          ]
        },
        "id": {
          "type": "string"
        },
        "username": {
          "type": "string"
        }
      },
      "required": [
        "type"
      ],
      "additionalProperties": true,
      "description": "Graph owner"
    },
    "targets": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "type": {
            "$ref": "#/properties/from/properties/type"
          },
          "id": {
            "$ref": "#/properties/from/properties/id"
          },
          "username": {
            "$ref": "#/properties/from/properties/username"
          }
        },
        "required": [
          "type"
        ],
        "additionalProperties": true
      },
      "minItems": 1,
      "description": "Identities to test"
    },
    "context": {
      "type": "string",
      "maxLength": 64,
      "description": "If set, only this context matches"
    }
  },
  "required": [
    "from",
    "targets"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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

Esquema de entrada

{
  "type": "object",
  "properties": {
    "platform": {
      "type": "string",
      "enum": [
        "wallet",
        "email",
        "phone",
        "telegram",
        "discord",
        "farcaster",
        "twitter",
        "github",
        "linkedin",
        "slack",
        "username"
      ],
      "description": "Identity platform, or username for a Connect username"
    },
    "identifier": {
      "type": "string",
      "minLength": 1
    },
    "context": {
      "type": "string",
      "maxLength": 64
    },
    "direction": {
      "type": "string",
      "enum": [
        "out",
        "in"
      ],
      "description": "out = who they trust (default); in = who trusts them"
    }
  },
  "required": [
    "platform",
    "identifier"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

18 oct 2026, 7:33 UTCverificadoversión no registrada14 herramientas

Quidli Connect

Calidad y seguridad

Hallazgos (3)

Costo de contexto

Instalación con un clic

Paquetes ejecutables

Puntos de conexión remotos

Inventario de herramientas

Herramientas (14)

Esquema de entrada

Esquema de entrada

Esquema de entrada

Esquema de entrada

Esquema de entrada

Esquema de entrada

Esquema de entrada

Esquema de entrada

Esquema de entrada

Esquema de entrada

Esquema de entrada

Esquema de entrada

Esquema de entrada

Esquema de entrada

Califica este servidor

Observaciones recientes