# io.github.kaitoInfra/twitterapi-mcp-server (remote · mcp.twitterapi.io)

Twitter/X read-only MCP server — 12 tools: search, users, tweets, followers, timelines, trends.

- Trust score: 88/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.twitterapi.io`: 88/100 (this document), [markdown](https://verifymcp.io/servers/kaitoinfra-twitterapi-mcp-server/mcp.md), [page](https://verifymcp.io/servers/kaitoinfra-twitterapi-mcp-server/mcp)

## Channel facts

- Endpoint: `https://mcp.twitterapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2047 tokens (~170/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the io.github.kaitoInfra/twitterapi-mcp-server server?

io.github.kaitoInfra/twitterapi-mcp-server is a hosted endpoint at https://mcp.twitterapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http kaitoinfra-twitterapi-mcp-server 'https://mcp.twitterapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "kaitoinfra-twitterapi-mcp-server": {
      "url": "https://mcp.twitterapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "kaitoinfra-twitterapi-mcp-server": {
      "type": "http",
      "url": "https://mcp.twitterapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.kaitoinfra-twitterapi-mcp-server]
url = "https://mcp.twitterapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kaitoinfra-twitterapi-mcp-server": {
      "type": "remote",
      "url": "https://mcp.twitterapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add kaitoinfra-twitterapi-mcp-server --url 'https://mcp.twitterapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  kaitoinfra-twitterapi-mcp-server:
    url: "https://mcp.twitterapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "kaitoinfra-twitterapi-mcp-server": {
      "Transport": "http",
      "Url": "https://mcp.twitterapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add kaitoinfra-twitterapi-mcp-server -t streamable-http -u 'https://mcp.twitterapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "kaitoinfra-twitterapi-mcp-server": {
      "type": "http",
      "url": "https://mcp.twitterapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-05 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (12)

### `search_tweets` (~420 tokens)

Search Tweets

🎯 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.

Input parameters:

- `cursor` (string): Pagination cursor from a previous response's next_cursor field. Omit for first page. Each page returns ~20 tweets.
- `query` (string, required): 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 s…
- `queryType` (string, required): 'Latest' returns most recent tweets first; 'Top' returns highest-engagement tweets first. Default to 'Latest' for time-sensitive queries.

### `get_user_info` (~101 tokens)

Get User Profile

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.

Input parameters:

- `userName` (string, required): Twitter/X screen name (handle) WITHOUT the leading @ sign. Example: 'elonmusk', not '@elonmusk'.

### `get_user_about` (~85 tokens)

Get User About Page

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.

Input parameters:

- `userName` (string, required): Twitter/X screen name without @ — fetches the user's profile 'about' / bio page.

### `get_user_followers` (~162 tokens)

Get User Followers

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.

Input parameters:

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

### `get_user_followings` (~109 tokens)

Get 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 (who they follow signals what they care about).

Input parameters:

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

### `get_user_last_tweets` (~296 tokens)

Get User's Recent 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', '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).

Input parameters:

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

### `get_user_mentions` (~160 tokens)

Get Mentions of a User

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.

Input parameters:

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

### `get_tweets_by_ids` (~122 tokens)

Batch Get Tweets by IDs

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.

Input parameters:

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

### `get_tweet_replies` (~121 tokens)

Get 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 tweet objects. Use this for thread analysis, sentiment on a viral post, or building reply trees.

Input parameters:

- `cursor` (string): Pagination cursor; omit for first page (~20 replies per page).
- `queryType` (string): 'Latest' or 'Top' — sort order of replies. Default 'Latest'.
- `tweetId` (string, required): Numeric ID of the tweet to fetch replies for.

### `get_tweet_quotes` (~149 tokens)

Get Tweet Quotes

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).

Input parameters:

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

### `get_tweet_retweeters` (~95 tokens)

Get Tweet Retweeters

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).

Input parameters:

- `cursor` (string): Pagination cursor; omit for first page (~100 per page).
- `tweetId` (string, required): Numeric ID of the tweet to fetch retweeters for.

### `get_trends` (~167 tokens)

Get Trending Topics

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.

Input parameters:

- `count` (integer): Max trends to return (default API behavior; may be silently capped by API).
- `woeid` (integer, required): 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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/kaitoinfra-twitterapi-mcp-server/mcp#diagnostics

## Score history

- 2026-09-20: 88
- 2026-09-19: 87
- 2026-09-18: 87
- 2026-09-17: 86
- 2026-09-16: 86
- 2026-09-15: 85
- 2026-09-14: 85
- 2026-09-13: 84
- 2026-09-12: 84
- 2026-09-11: 83
- 2026-09-10: 83
- 2026-09-09: 82
- 2026-09-08: 82
- 2026-09-07: 82
- 2026-09-06: 81
- 2026-09-05: 81
- 2026-09-04: 80
- 2026-09-03: 80
- 2026-09-02: 79
- 2026-09-01: 79
- 2026-08-31: 78
- 2026-08-30: 78
- 2026-08-29: 77
- 2026-08-28: 77
- 2026-08-27: 76
- 2026-08-26: 76
- 2026-08-25: 73
- 2026-08-24: 73

## Common questions

### What is the io.github.kaitoInfra/twitterapi-mcp-server server?

io.github.kaitoInfra/twitterapi-mcp-server is listed in the public MCP registry as io.github.kaitoInfra/twitterapi-mcp-server. Twitter/X read-only MCP server, 12 tools: search, users, tweets, followers, timelines, trends. This page covers its hosted endpoint (https://mcp.twitterapi.io/mcp).

### Is the io.github.kaitoInfra/twitterapi-mcp-server server safe to use?

io.github.kaitoInfra/twitterapi-mcp-server scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.kaitoInfra/twitterapi-mcp-server server expose?

io.github.kaitoInfra/twitterapi-mcp-server exposes 12 tools: search_tweets, get_user_info, get_user_about, get_user_followers, get_user_followings, and 7 more. Their descriptions and schemas cost roughly 1,987 tokens of context every time the server is loaded.

### Does the io.github.kaitoInfra/twitterapi-mcp-server server require authentication?

Yes. io.github.kaitoInfra/twitterapi-mcp-server asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.github.kaitoInfra/twitterapi-mcp-server server still maintained?

io.github.kaitoInfra/twitterapi-mcp-server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.twitterapi.io/mcp
- Website: https://twitterapi.io/
- Changelog RSS feed: https://verifymcp.io/servers/kaitoinfra-twitterapi-mcp-server/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/kaitoinfra-twitterapi-mcp-server/mcp.json
- HTML version of this page: https://verifymcp.io/servers/kaitoinfra-twitterapi-mcp-server/mcp