xflux
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XFLUX_API_KEY | Yes | API key from https://www.xfluxapi.com/dashboard/api-keys |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| xflux_get_userA | X/Twitter profile lookup via XFlux. Use when the user asks for a public Twitter/X user profile, bio, follower counts, or verified status by @username. Read-only; not for posting. |
| xflux_search_tweetsA | Search recent public tweets/posts on X/Twitter via XFlux (same operators as X search: from:, lang:, quotes). Use when the user wants tweet search, keyword monitoring research, cashtag/hashtag scans, or agent research over live X content. Prefer this over scraping. |
| xflux_get_user_tweetsA | Fetch a public X/Twitter user timeline via XFlux. Use when the user asks what someone posted lately, KOL latest tweets, or to summarize a handle's recent activity. |
| xflux_get_tweetA | Fetch one public tweet/post by numeric status ID via XFlux. Use when the user pastes a tweet ID or needs a single post's text and engagement. |
| xflux_list_monitorsA | List the user's XFlux account monitors (read-only): @targets, keywords, status, webhook flag, optional recent hits. Use when they ask what they are watching on XFlux. Creating monitors requires the Dashboard, not this tool. |
| xflux_get_monitor_hitsA | List recent hits for one XFlux monitor (read-only). Use after xflux_list_monitors when the user wants alert history for a watched @account. Create/edit monitors in the Dashboard. |
| xflux_smart_money_listA | Discover ranked Smart Money X/Twitter accounts (macro, trading, crypto, geopolitics) with recent extractable forward-looking market calls. Use when the user wants new KOL/analyst accounts to follow, alpha sources, or predictor discovery — prefer this over googling long analyst prompts. Pass exclude for handles already tracked. |
| xflux_smart_money_profileA | Get one XFlux Smart Money account profile plus recent extracted prediction calls (default last 14 days). Use when digging into a specific @analyst or KOL already found via xflux_smart_money_list. |
| xflux_smart_money_claimsB | List recent Smart Money prediction/market calls across X accounts via XFlux. Use for a feed of forward-looking claims (macro, trading, crypto, geopolitics). Optional niche and exclude list. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| trading-keywords | Keyword templates for trading/macro XFlux monitors |
| monitors-setup | How to set up XFlux account monitors and webhooks |
| smart-money | Smart Money discovery niches, exclude usage, and monitor CTA |
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.