io.github.kaitoInfra/twitterapi-mcp-server

Est-ce que io.github.kaitoInfra/twitterapi-mcp-server est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.kaitoInfra/twitterapi-mcp-server » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 12 outils

• get_trends≈ 216 tokens

  Fetch current trending topics/hashtags for a location. Pass a Yahoo Where-On-Earth ID (woeid). Common: 1=Worldwide, 23424977=USA, 23424975=UK, 23424856=Japan, 23424848=India, 23424881=South Korea. Use woeid=1 for global trends if you don't know a specific location.

  Paramètres, retour & exemple (2)

  Paramètres

  • count · integer · optionnel
    Max trends to return (default API behavior; may be silently capped by API).
  • woeid · integer · requis
    Yahoo Where-On-Earth ID for the location. Common values: 1 = Worldwide, 23424977 = USA, 23424975 = UK, 23424856 = Japan. Use 1 for global trends if unsure.

  Exemple d'appel

  {"name": "get_trends", "arguments": {"woeid": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_tweet_quotes≈ 247 tokens

  Fetch quote-tweets (tweets that quote the given tweetId). Useful for finding commentary on a tweet, measuring reach beyond direct replies. Supports time bounds (sinceTime/untilTime, Unix seconds). Paginates via cursor (~20 per page).

  Paramètres, retour & exemple (5)

  Paramètres

  • cursor · string · optionnel
    Pagination cursor; omit for first page (~20 per page).
  • tweetId · string · requis
    Numeric ID of the tweet to fetch quote-tweets for.
  • sinceTime · integer · optionnel
    Unix timestamp (seconds) lower bound.
  • untilTime · integer · optionnel
    Unix timestamp (seconds) upper bound.
  • includeReplies · boolean · optionnel
    Include reply-type quote-tweets in addition to top-level. Default false.

  Exemple d'appel

  {"name": "get_tweet_quotes", "arguments": {"tweetId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_tweet_replies≈ 206 tokens

  Fetch replies to a specific tweet. Pass the numeric tweetId of the root tweet; returns top-level replies (about 20 per page) with full tweet objects. Use this for thread analysis, sentiment on a viral post, or building reply trees.

  Paramètres, retour & exemple (3)

  Paramètres

  • cursor · string · optionnel
    Pagination cursor; omit for first page (~20 replies per page).
  • tweetId · string · requis
    Numeric ID of the tweet to fetch replies for.
  • queryType · string · optionnel · Latest | Top
    'Latest' or 'Top' — sort order of replies. Default 'Latest'.

  Exemple d'appel

  {"name": "get_tweet_replies", "arguments": {"tweetId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_tweet_retweeters≈ 164 tokens

  Fetch users who retweeted a specific tweet (the simple 'retweet' action, not quote-tweets — for those use get_tweet_quotes). Returns user profiles with metadata. Paginates via cursor (~100 per page).

  Paramètres, retour & exemple (2)

  Paramètres

  • cursor · string · optionnel
    Pagination cursor; omit for first page (~100 per page).
  • tweetId · string · requis
    Numeric ID of the tweet to fetch retweeters for.

  Exemple d'appel

  {"name": "get_tweet_retweeters", "arguments": {"tweetId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_tweets_by_ids≈ 182 tokens

  Batch-fetch full tweet objects by their numeric tweet IDs. Pass a comma-separated string of up to 100 IDs. Use this when you already have specific tweet IDs (e.g., from a search result, a URL, or a webhook event) and need the full tweet data — author, text, engagement counts, media, etc.

  Paramètres, retour & exemple (1)

  Paramètres

  • tweet_ids · string · requis
    Comma-separated tweet IDs (e.g. '1234567890,9876543210'). Batch fetch up to 100 tweets in one call. Tweet IDs are numeric strings.

  Exemple d'appel

  {"name": "get_tweets_by_ids", "arguments": {"tweet_ids": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_user_about≈ 156 tokens

  Fetch the extended 'about' / profile page data for a Twitter/X user by screen name. Returns extra profile metadata beyond what get_user_info gives (when available). Use get_user_info first; only call this if you need additional about-page fields.

  Paramètres, retour & exemple (1)

  Paramètres

  • userName · string · requis
    Twitter/X screen name without @ — fetches the user's profile 'about' / bio page.

  Exemple d'appel

  {"name": "get_user_about", "arguments": {"userName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_user_followers≈ 267 tokens

  Fetch followers of a Twitter/X user in reverse chronological order (newest first), each with full profile metadata (name, bio, follower count, verified status, etc.). Paginates via cursor. Use this to analyze who follows an account, build follower audiences, or sample for competitive analysis. For large accounts use pagination; you will not get all followers in one call.

  Paramètres, retour & exemple (3)

  Paramètres

  • cursor · string · optionnel
    Pagination cursor from previous response's next_cursor. Omit for first page.
  • pageSize · integer · optionnel
    Followers per page (default 200, max 200). Each follower includes full profile metadata (name, bio, follower count, etc.).
  • userName · string · requis
    Twitter/X screen name without @ — fetches followers of this user.

  Exemple d'appel

  {"name": "get_user_followers", "arguments": {"userName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_user_followings≈ 201 tokens

  Fetch the accounts a Twitter/X user follows, with full profile metadata. Paginates via cursor. Use this to map a user's interest graph (who they follow signals what they care about).

  Paramètres, retour & exemple (3)

  Paramètres

  • cursor · string · optionnel
    Pagination cursor; omit for first page.
  • pageSize · integer · optionnel
    Followings per page (default 200, max 200). Each includes full profile metadata.
  • userName · string · requis
    Twitter/X screen name without @ — fetches accounts this user follows.

  Exemple d'appel

  {"name": "get_user_followings", "arguments": {"userName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_user_info≈ 167 tokens

  Fetch basic profile info for a Twitter/X user by their screen name (handle). Returns user ID, display name, bio, follower/following counts, verified status, profile picture, banner, location, website, and account creation date. Use this as the starting point for any user analysis.

  Paramètres, retour & exemple (1)

  Paramètres

  • userName · string · requis
    Twitter/X screen name (handle) WITHOUT the leading @ sign. Example: 'elonmusk', not '@elonmusk'.

  Exemple d'appel

  {"name": "get_user_info", "arguments": {"userName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_user_last_tweets≈ 366 tokens

  ⚠️ ONLY for 'latest / recent / what's new' queries about a user. DO NOT use for date-range queries (e.g. 'tweets from January 2026', 'tweets last week', 'tweets between X and Y', 'tweets in 2025'). For specific dates / older tweets, use **search_tweets** with query like 'from:elonmusk since:2026-01-01 until:2026-02-01'. Fetch the MOST RECENT tweets posted by a Twitter/X user, sorted by created_at descending (newest first). Provide EITHER userName (screen name, no @) OR userId (numeric). Use userId when known — handles can change. Set includeReplies=true to include the user's reply tweets in addition to top-level tweets. Paginates via cursor (~20 per page).

  Paramètres, retour & exemple (4)

  Paramètres

  • cursor · string · optionnel
    Pagination cursor; omit for first page.
  • userId · string · optionnel
    Twitter/X numeric user ID (e.g. '44196397'). Provide EITHER userName OR userId. Prefer userId if known — handles can change.
  • userName · string · optionnel
    Twitter/X screen name without @ (e.g. 'elonmusk'). Provide EITHER userName OR userId.
  • includeReplies · boolean · optionnel
    Include the user's reply tweets in addition to top-level tweets. Default false — only top-level tweets.

  Exemple d'appel

  {"name": "get_user_last_tweets", "arguments": {"cursor": "texte", "userId": "texte", "userName": "texte", "includeReplies": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_user_mentions≈ 262 tokens

  Fetch tweets that mention a specific Twitter/X user (i.e. tweets containing @userName). Useful for brand monitoring, sentiment tracking on a public figure, or finding conversations involving an account. Supports time-bound queries via sinceTime/untilTime (Unix seconds). Paginates via cursor.

  Paramètres, retour & exemple (4)

  Paramètres

  • cursor · string · optionnel
    Pagination cursor; omit for first page (~20 per page).
  • userName · string · requis
    Twitter/X screen name without @ — fetches tweets that mention this user (@userName).
  • sinceTime · integer · optionnel
    Unix timestamp (seconds) lower bound — only mentions after this time. Omit for no lower bound.
  • untilTime · integer · optionnel
    Unix timestamp (seconds) upper bound. Omit for no upper bound.

  Exemple d'appel

  {"name": "get_user_mentions", "arguments": {"userName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_tweets≈ 484 tokens

  🎯 PRIMARY CHOICE for date-range / historical / keyword-based tweet queries. Use this (NOT get_user_last_tweets) whenever user asks about a SPECIFIC TIME RANGE or historical tweets: • 'tweets from January 2026' → query='from:elonmusk since:2026-01-01 until:2026-02-01' • 'tweets between X and Y' → 'from:USER since:X until:Y' • 'tweets last week / last month' → translate to since:/until: dates • 'tweets containing keyword X by user Y' → 'from:Y X' • 'older tweets' / 'archive' / 'in 2025' → use date range, not pagination Date format: YYYY-MM-DD (UTC midnight). 'until:' is exclusive (until:2026-02-01 = up to Jan 31). General: Search Twitter/X for tweets matching a query. Supports the full Twitter advanced search syntax (from:, to:, since:, until:, lang:, filter:, has:, -, OR, etc). Returns ~20 tweets per page in reverse chronological order ('Latest') or by engagement ('Top'). Use this for keyword research, monitoring mentions of a brand/topic, finding tweets in a date range, or any open-ended tweet discovery.

  Paramètres, retour & exemple (3)

  Paramètres

  • query · string · requis
    Twitter advanced search query string. Supports operators: from:USER, to:USER, since:YYYY-MM-DD, until:YYYY-MM-DD, lang:en, filter:replies, -filter:retweets, has:images, etc. Example: 'from:elonmusk since:2026-01-01 has:images'
  • cursor · string · optionnel
    Pagination cursor from a previous response's next_cursor field. Omit for first page. Each page returns ~20 tweets.
  • queryType · string · requis · Latest | Top
    'Latest' returns most recent tweets first; 'Top' returns highest-engagement tweets first. Default to 'Latest' for time-sensitive queries.

  Exemple d'appel

  {"name": "search_tweets", "arguments": {"query": "texte", "queryType": "Latest"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.twitterapi.io/mcp