Skip to main content
Glama

Related Servers

Alternatives to Xearch MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • A
      license
      C
      quality
      B
      maintenance
      Enables 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.
      100
      11
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to read, post, search, and engage with Twitter/X content, including AI-powered reply drafting and analytics.
      17
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables reading public X/Twitter posts by URL or numeric ID and returning original structured data, including articles, quoted posts, and media fields, without requiring an X API key.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables LLM agents to interact with Twitter (X) for searching tweets, posting content with images, analyzing engagement, and extracting topics using the Twitter API.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to read any X (Twitter) link without login, search X by meaning with every hit re-checked against X, and audit posts and accounts by value rather than reach.
      MIT

    TDQS

    A3.9/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool maps to a distinct retrieval target: single post, batch posts, search, user timeline, user profile, and server status. The only mild overlap is get_user_tweets being a thin wrapper over search_tweets, but the description makes the relationship explicit and recommends when to use it.

    Naming Consistency4/5

    Five of six tools follow a clear verb_noun pattern (get_tweet, get_tweets, get_user, get_user_tweets, search_tweets). The lone 'status' deviates from the convention but is unambiguous in context.

    Tool Count5/5

    Six tools is well-scoped for a read-only X/Twitter reading server, with no redundant variants or filler. Batch, single, and search variants each earn their place.

    Completeness3/5

    The surface covers read workflows (post by ID, batch, search, user timeline, profile, diagnostics) but has no thread/reply retrieval and no write operations, both of which the descriptions acknowledge as unavailable. The missing conversation context is a notable dead end for a common use case.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues