x-search
Related Servers
Alternatives to x-search
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP agents to perform native X (Twitter) searches with original-post citations and transparent usage tracking. Supports existing Grok login sessions or explicit xAI API billing without runtime dependencies.16 npmMIT
- AlicenseAqualityDmaintenanceEnables searching X (Twitter) posts, discussions, trends, and web content via Grok API using natural language.310 npm1MIT
- AlicenseAqualityDmaintenanceEnables real-time search of X.com (Twitter) posts, users, threads, and trends via xAI's Grok API, directly from Claude.549 PyPI4MIT
- AlicenseNot gradedqualityDmaintenanceEnables real-time web and Twitter/X search via Grok, returning structured results with source URLs, confidence scores, and key points. Supports multiple output modes, language options, and time range filtering.538 npm4MIT
- AlicenseNot gradedqualityDmaintenanceSearch X (formerly Twitter) in real-time from your AI assistant using xAI's Grok API, with no X API account required.538 npmMIT
- AlicenseNot gradedqualityCmaintenanceLive X (Twitter) and web search for any coding agent through your existing Grok subscription. Exposes a grok_search MCP tool, so no X API key or X developer account is needed.63 npm29Apache 2.0
TDQS
Scored across 1 tool
The server exposes a single tool, so there is no possibility of misselection or overlapping purpose. Any agent request for X/Twitter profile, post, or thread search maps unambiguously to x_search.
x_search is a clean snake_case verb_noun name and mirrors the server name x-search. With only one tool there is no broader pattern to evaluate, so consistency is trivially satisfied rather than demonstrated.
One tool is at the thin end of the acceptable range; the rubric treats 1-2 tools as borderline. The scope (X/Twitter search) is narrow enough that a single tool is defensible, but it provides no alternative operations.
Search is covered with structured output, URLs, and cache control, but notable gaps exist: no fetch-by-post-ID, no profile lookup, no thread expansion, and no pagination or result-limit controls beyond cache_mode. Agents can work around this only by re-querying search.