give your agent your handle, not a wallet 🤖🦑 @quidli/connect-mcp resolves farcaster, x, github, discord, telegram, linkedin, email and more to EVM & Solana wallet addresses, checks counterparty reputations and autonomously executes onchain txs on your behalf just a single command on your terminal to get started: `npx -y @quidli/connect-mcp`, no API key necessary

1 reply

2 recasts

7 reactions

reminder that @quidli/connect-mcp is an mcp server that resolves social handles to evm & solana wallet addresses add it to your app, client or agent and it can: - resolve social handles (farcaster, x, github, discord, telegram, linkedin, email and or phone number) to evm & solana addresses - generate new wallets for social handles that have none configured - run reputation checks on accounts before executing onchain txs - autonomously send tokens to verified accounts open repo: https://github.com/Quidli/connect-mcp

0 reply

6 recasts

29 reactions

fyi, you can build most of this very easily with @quidli connect, and you can even self-host the whole thing if you'd rather not trust anyone your email/social handle of choice is just so you can authenticate + no banking details at all run it hosted or locally, your keys, your wallets, try it out: `npx -y @quidli/connect-mcp`

4 replies

9 recasts

56 reactions

naturally this means @solana txs are now also wired into DiscoCentaur & TeleCentaur setups too so you can run multiplayer agentic payments in your own locally hosted group chats on discord & telegram on select evm chains AND solana, all powered by @quidli connect 🦑🦑🦑

1 reply

2 recasts

15 reactions

fyi, @solana txs are now native on @quidli connect 🦑🤖🦑 lookups always returned a SOL address, but transacting on solana was up to you to build in yourself. now it's one call to send SOL or SPL tokens, with nothing additional to wire up! run it from your own setup: npx -y @quidli/connect-mcp

1 reply

9 recasts

41 reactions

fyi, you can point any MCP client at our hosted server so that your agent can start resolving handles to wallets: https://mcp.connect.quid.li handles on farcaster, x, github, discord, telegram, etc. become machine-readable & mapped to wallet addresses so that your agents can index, verify and pay those you engage with, natively from your clients 🦑🤖 and repo is open if you want to dig in as well: http://github.com/Quidli/connect-mcp

3 replies

4 recasts

21 reactions

updated the @quidli connect API + MCP so that the `connect_me` & `connect_lookup_exposed` tools return connect profiles, socials, wallets and reputations in a single call for all agents & operators whenever necessary then i wired it into DiscoCentaur (& TeleCentaur too) so that all agents in our discord can identify who's who in the server by reading the MCP, while what i've kept private stays private

1 reply

5 recasts

16 reactions

btw, with an api key no longer necessary to get started with http://mcp.connect.quid.li, @quidli connect is now accessible from grok.com too, albeit in limited form 🪐🤖🦑 tools like /lookup & /score (reputation) work well so you can have grok research the social handles you come across and any publicly associated reputations they may have but no personal configurations or onchain txs can be performed because your agent is not linked to your own quidli account, which requires api key config for authentication

2 replies

7 recasts

25 reactions

btw, in case you don't use claude code, you can still add @quidli connect to whatever MCP client you use, like on cursor or hermes 🤖🦑 just add to your mcp config: npx -y @quidli/connect-mcp and then find any client specific instructions here: github.com/Quidli/connect-mcp

1 reply

5 recasts

18 reactions

in case you're unaware, here's the tl;dr on what @quidli connect mcp enables: your agent can resolve social handles (farcaster, x, github, linkedin, etc.) to a wallet & check any configured reputation before executing an onchain payment, no api key required for example, add to your claude code setup in one line: `claude mcp add --transport http quidli https://mcp.connect.quid.li/` then ask it to resolve any handle, like 'ahn.eth' and if that handle(s) never interacted with quidli, a wallet gets generated for them, claimable whenever the handle gets authenticated 🦑

0 reply

7 recasts

26 reactions

small but useful fix to the @quidli connect readme 🦑 if you're running npx -y @quidli/connect-mcp from a background service (launchd, systemd, etc.), it can hang indefinitely with no output because npx's PATH resolution doesn't behave the same outside an interactive shell you can now use bunx as a workaround, same job without that hang full writeup + config example in the troubleshooting section: https://github.com/Quidli/connect-mcp/blob/main/README.md#troubleshooting

0 reply

10 recasts

35 reactions

@quidli is now publicly available as an app for @animocabrands minds agents 🦑🤖🧠 built on quidli connect, it enables your Mind to resolve social identities to configured ETH & SOL wallets, check associated reputation scores and gate onchain txs based on who someone actually is, no custom training required get set up from your minds dashboard > minds bazaar > apps > type in "quidli" > hit "equip this app"

1 reply

2 recasts

14 reactions

we released the @quidli connect MCP (your social reputations made readable by agents + resolve all linked socials to EVM & SOL wallets) in june just now getting around to making the repo public: github.com/Quidli/connect-mcp

0 reply

1 recast

12 reactions

more multi-agent fun via puffo (using claude + @quidli connect) 🤖🦑 my team of crack agents were able to recall my meat colleague @guillaumeth, verify & validate his contributions today and then pay him his well deserved 0.25 USDC, all without any additional prompting you can see 'planner' bot being hesitant, but 'engineer' autonomously took the lead and got the job done 🤣

2 replies

6 recasts

21 reactions

single-player agents automate, multiplayer agents transact we'll see increasingly crazy shit on the latter, but none of it sticks until an agent can tell who it's transacting with... and while tradfi rails work, they'll require everyone to hand over personal data and still shut out anyone not from the "right country" or without the "right documents" for many p2p cases, agentic payments should be able to rely on people's existing reputations built up on linkedin, github, x and even farcaster, and that's what we're building at @quidli 🦑🤖 point it at any handle and see what comes back: npx -y @quidli/connect-mcp

0 reply

1 recast

5 reactions