TwitterAPI.io MCP server listing — hosted at https://mcp.twitterapi.io/mcp (sour
TwitterAPI.io MCP server listing — hosted at https://mcp.twitterapi.io/mcp (source: kaitoInfra/twitterapi-io-mcp-server)
active Production-safe Score 96/100 http no auth
At a glance
| Endpoint | https://mcp.twitterapi.io/mcp |
|---|---|
| Source | https://github.com/kaitoInfra/twitterapi-mcp-server |
| Transport | http |
| Tools | 12 |
| Auth | none |
| First seen | 2026-10-07 20:17:54 |
| Last checked | 2026-11-17 21:54:28 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 242 / 467 ms |
| Last successful check | 2026-11-17 21:54:28 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (12)
search_tweets— 🎯 PRIMARY CHOICE for date-range / historical / keyword-based tweet queries. Use this (NOT get_user_last_tweets) whenever user asks about aget_user_info— Fetch basic profile info for a Twitter/X user by their screen name (handle). Returns user ID, display name, bio, follower/following counts,get_user_about— Fetch the extended 'about' / profile page data for a Twitter/X user by screen name. Returns extra profile metadata beyond what get_user_infoget_user_followers— Fetch followers of a Twitter/X user in reverse chronological order (newest first), each with full profile metadata (name, bio, follower counget_user_followings— Fetch the accounts a Twitter/X user follows, with full profile metadata. Paginates via cursor. Use this to map a user's interest graph (whoget_user_last_tweets— ⚠️ ONLY for 'latest / recent / what's new' queries about a user. DO NOT use for date-range queries (e.g. 'tweets from January 2026', 'tweetsget_user_mentions— Fetch tweets that mention a specific Twitter/X user (i.e. tweets containing @userName). Useful for brand monitoring, sentiment tracking on aget_tweets_by_ids— Batch-fetch full tweet objects by their numeric tweet IDs. Pass a comma-separated string of up to 50 IDs. Use this when you already have speget_tweet_replies— Fetch replies to a specific tweet. Pass the numeric tweetId of the root tweet; returns top-level replies (about 20 per page) with full tweetget_tweet_quotes— Fetch quote-tweets (tweets that quote the given tweetId). Useful for finding commentary on a tweet, measuring reach beyond direct replies. Sget_tweet_retweeters— Fetch users who retweeted a specific tweet (the simple 'retweet' action, not quote-tweets — for those use get_tweet_quotes). Returns user prget_trends— Fetch current trending topics/hashtags for a location. Pass a Yahoo Where-On-Earth ID (woeid). Common: 1=Worldwide, 23424977=USA, 23424975=U
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:54:28 | ✓ | ✓ | 115 ms | 95 | active |
| 2026-11-17 21:39:17 | ✓ | ✓ | 109 ms | 95 | active |
| 2026-11-17 21:24:03 | ✓ | ✓ | 132 ms | 95 | active |
| 2026-11-17 21:08:55 | ✓ | ✓ | 246 ms | 95 | active |
| 2026-11-17 20:53:46 | ✓ | ✓ | 130 ms | 95 | active |
| 2026-11-17 20:38:44 | ✓ | ✓ | 129 ms | 95 | active |
| 2026-11-17 20:23:40 | ✓ | ✓ | 144 ms | 95 | active |
| 2026-11-17 20:08:31 | ✓ | ✓ | 95 ms | 98 | active |
| 2026-11-17 19:52:40 | ✓ | ✓ | 255 ms | 95 | active |
| 2026-11-17 19:37:33 | ✓ | ✓ | 140 ms | 95 | active |
| 2026-11-17 19:22:18 | ✓ | ✓ | 361 ms | 91 | active |
| 2026-11-17 19:07:07 | ✓ | ✓ | 192 ms | 95 | active |
| 2026-11-17 18:51:52 | ✓ | ✓ | 98 ms | 98 | active |
| 2026-11-17 18:36:46 | ✓ | ✓ | 288 ms | 95 | active |
| 2026-11-17 18:21:42 | ✓ | ✓ | 335 ms | 91 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://mcp.twitterapi.io/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/mcp-twitterapi-io-mcp # JSON