MCP server for agent identity and reputation: resolve social handles to wallet addresses, score onchain reputation and send USDC from any MCP client.
Scored across 14 tools
Most tools have clearly distinct purposes segmented by domain: drop/payments, lookup/profile, scores, and trust. The main possible confusion is between connect_lookup and connect_lookup_exposed, since both deal with resolving recipients, though one returns wallet addresses while the other lists exposed platforms and profiles. The scores trio is cleanly distinguished by input type.
All tools use a consistent connect_ prefix and snake_case naming, generally following a domain_action pattern such as connect_drop_balance, connect_trust_create, and connect_scores_batch. A few names like connect_me and connect_lookup_exposed deviate slightly from strict verb_noun form but remain predictable and readable.
With 14 tools, the set is well-scoped for a server covering payments, identity lookup, scoring, and trust attestations. Each tool maps to a meaningful operation, and the count stays within a reasonable range without obvious filler.
The surface covers core workflows well: balances, chain compatibility, drops, lookups, profile, scores, and trust create/revoke/check/graph. The main gap is a dedicated drop transaction status or history tool, which would help after connect_drop returns 202 processing or when recipients need follow-up.
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. ERC-721: set tokenStandard to erc721, tokenContract to the collection, and tokenId on each recipient. Do not send an amount. One safeTransferFrom per NFT. ERC-1155: set tokenStandard to erc1155, tokenContract to the contract, and tokenId plus tokenAmount (quantity, at least 1) on each recipient. The same id can go to several recipients. One safeTransferFrom per recipient. An EIP-7702 delegation signed before the matching standard must be replaced. Smart Send wallets enrolled on the previous Privy policy must re-enable Smart Send. 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, +4 more.
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).
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.
Get public x402 list prices for lookup and scores (reference only; live paywall amounts are in 402 responses).
Inputs: no named parameters.
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).
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).
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.
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.
Scores for a linked social account or wallet.
Inputs: platform (required), identifier (required).
Scores by Connect public username.
Inputs: username (required).
Check whether identities sit in a trust graph at depth 1. Omit context to match any context.
Inputs: from (required), targets (required), context.
Create unidirectional trust attestations on Base (EAS) from the API key owner embedded wallet to one or more wallets or social identities, in a single transaction. Identical active attestations are returned without a new transaction. Recipients still provisioning are reported as processing while the others are attested. Requires CONNECT_API_KEY, Smart Send attestation signer enrolled, and ETH on Base for gas when a new attestation is submitted.
Inputs: to (required), level (required), context, expiresIn.
List outgoing or incoming trust edges for an identity at depth 1.
Inputs: platform (required), identifier (required), context, direction.
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.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.