Everything usable runs through Neynar, including the parts that make this more than a feed reader — profile lookup by wallet address, on-chain balances, and a trending feed you can compare across three different ranking providers. The bulk channel search is the piece to remember: several queries in parallel with pagination, instead of one call per channel.
A social-data server with a provider architecture. Farcaster is fully implemented through the Neynar API, including wallet-based profile lookup and balances; a Twitter provider exists as a placeholder.
- `search-content` across a platform, `get-user-content` for one account, `get-thread` for a whole conversation
- Profiles from either direction — `get-user-profile`, `get-user-profile-by-wallet`, `get-wallet-profile`
- `get-user-balance` — a user's wallet balance, taking an FID or a username and resolving the username itself
- Trending — `get-trending-topics`, and `getTrendingFeed` across the neynar, openrank and mbd providers with time windows from 1h to 30d
- Channels — `search-channels`, and `search-bulk-channels` which runs several queries in parallel and returns follower counts and metadata with pagination
- The same data as `social://` resources, plus prompts such as `analyze-thread`, `summarize-user-activity` and `explore-trending-feed`
Node.js 16+ and a Neynar API key in `NEYNAR_API_KEY` — without a valid key the Farcaster tools do not work. `npm install`, `npm run build`, then `npm start` for stdio or `npm run start:http` for HTTP/SSE. `ENABLE_FARCASTER` and `ENABLE_TWITTER` choose which providers load.