xflux
Related Servers
Alternatives to xflux
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceEnables AI agents to search, read user profiles, timelines, media, follow threads, track trends, and manage accounts on X/Twitter via GraphQL, without browser automation or paid API keys.10011MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read public X (Twitter) data without the paid official API, including tweet and user search, profiles, timelines, media, replies, retweeters, followers, lists, and trends. All tools are read-only and rotate across multiple scraping accounts with proxy and rate-limit support.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to scrape Twitter/X profiles, tweets, and search results without an API key, returning structured JSON with bios, stats, and engagement metrics via x402 micropayments.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to fully automate X/Twitter interactions including searching, posting, engaging, and managing multiple accounts without paid API keys.MIT
- AlicenseAqualityCmaintenanceEnables reading public X (Twitter) content like profiles, tweets, and search results via a stealth browser, without official API costs.11MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to search live public X/Twitter posts and fetch recent posts from user profiles without API keys, using zero-configuration local MCP tools for Claude, Cursor, and Pi.7 npm1MIT
TDQS
Scored across 9 tools
The core X tools (get_user, search_tweets, get_user_tweets, get_tweet) are cleanly separated by resource and input shape, and descriptions reinforce this. The main soft spots are within the smart-money family: smart_money_list vs smart_money_claims both return account/claim feeds, and smart_money_profile overlaps conceptually with get_user plus claims, though the descriptions do enough to steer selection.
All tools share the xflux_ prefix and most follow a verb_noun pattern (get_user, search_tweets, list_monitors, get_monitor_hits). The smart_money_list/profile/claims group deviates into noun_noun naming, which is a minor inconsistency but still predictable within its sub-family.
Nine tools is well-scoped for a read-only X/Twitter research server, split sensibly between general tweet/user lookups, monitor inspection, and smart-money discovery. No tool appears redundant enough to drop.
The surface covers profile lookup, timeline, keyword search, single-tweet fetch, monitor listing/hits, and smart-money discovery, which is solid lifecycle coverage for a read-only research domain. Gaps are minor but real: no thread/reply traversal, no follower/following lists, and monitor creation is explicitly deferred to the Dashboard, leaving write operations out entirely.