Veezee
Related Servers
Alternatives to Veezee
AlicenseNot gradedqualityBmaintenanceEnables AI agents to enrich LinkedIn prospect data with current role, company, and experience through MCP or REST, with credit-metered access and free credits.MIT
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to retrieve X/Twitter profiles and tweets, YouTube video and channel data, and TikTok profile and video stats on a pay-per-result basis without requiring login or platform API keys.34 npmMIT
- AlicenseAqualityDmaintenanceProvides AI agents with unified access to 21 social media platforms and 105 endpoints for retrieving profiles, posts, comments, search results, trending content, and analytics without per-platform authentication.4184 npmMIT
- AlicenseNot gradedqualityBmaintenanceLive LinkedIn data for AI agents: 44 tools for profiles, companies, jobs, posts, people search, job-change signals and email finding. Hosted remote server (streamable HTTP) - your agent never touches your own LinkedIn account. 300 free credits on signup, no card. Dockerfile in repo bridges stdio clients to the hosted endpoint via mcp-remote.MIT
- -licenseNot gradedqualityCmaintenanceTwitter/X, YouTube, Reddit, Google and more - 100+ endpoints in total. No account, no OAuth, no subscription. Pay per call in USDC, or top up once and spend one balance across all of them.1-

fetcher.sh MCP Serverofficial
AlicenseAqualityAmaintenanceEnables AI assistants to search Twitter/X, YouTube, Reddit, Google, app-store listings, and 100+ other public web data endpoints via natural language, with prepaid credit or per-call USDC payment and no account or OAuth required.512 npmMIT
Xpoz MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceSearch Twitter/X, Instagram, Reddit, and TikTok from AI agents. 52 tools for keyword and hashtag search, user profiles, posts, comments, follower connections, and tracking. Billions of posts indexed, natural-language queries, CSV export up to 500K rows. Remote server (Streamable HTTP) with OAuth sign-in, no API keys needed.12MIT
TDQS
Scored across 10 tools
Each tool maps to a distinct platform, entity, and action. The search-vs-fetch boundaries are explicit, and the singular/plural x_get_tweet vs x_get_tweets pair is clearly differentiated by description.
Names broadly follow a snake_case platform_verb_object pattern, and parallel resolvers are consistently named. Minor inconsistencies exist in pluralization (x_get_tweet vs x_get_tweets vs linkedin_get_posts) and get_usage lacks a platform prefix.
Ten tools is within the ideal range, and each tool has a clear purpose. The count fits a multi-platform social data API without feeling bloated or thin.
The Reddit and X surfaces are notably incomplete: reddit_resolve_url returns post/comment/user IDs but the corresponding reddit_get_post and reddit_get_user tools are absent, and x_resolve_url references x_get_profile and x_search which are also missing. LinkedIn is better covered, but the multi-platform promise is undermined by these dead ends.