io.github.kaitoInfra/twitterapi-mcp-server
REMOTE · MCP.TWITTERAPI.IO · SCANNED SEP 20
Twitter/X read-only MCP server — 12 tools: search, users, tweets, followers, timelines, trends.
Available components
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. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · mcp.twitterapi.io
claude mcp add --transport http kaitoinfra-twitterapi-mcp-server 'https://mcp.twitterapi.io/mcp'
{
"mcpServers": {
"kaitoinfra-twitterapi-mcp-server": {
"url": "https://mcp.twitterapi.io/mcp"
}
}
} {
"servers": {
"kaitoinfra-twitterapi-mcp-server": {
"type": "http",
"url": "https://mcp.twitterapi.io/mcp"
}
}
} [mcp_servers.kaitoinfra-twitterapi-mcp-server] url = "https://mcp.twitterapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kaitoinfra-twitterapi-mcp-server": {
"type": "remote",
"url": "https://mcp.twitterapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add kaitoinfra-twitterapi-mcp-server --url 'https://mcp.twitterapi.io/mcp' --transport streamable-http
mcp_servers:
kaitoinfra-twitterapi-mcp-server:
url: "https://mcp.twitterapi.io/mcp" {
"McpServers": {
"kaitoinfra-twitterapi-mcp-server": {
"Transport": "http",
"Url": "https://mcp.twitterapi.io/mcp"
}
}
} assistant mcp add kaitoinfra-twitterapi-mcp-server -t streamable-http -u 'https://mcp.twitterapi.io/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
- 10 Sept 26 +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.
- 7 Sept 26 +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.
- 5 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.twitterapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=twitterapi.io | CN=WE1,O=Google Trust Services,C=US | 26 Jul 2026 | 24 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 2bbe335cb9c978230ee1f6e10744c281 |
| SANs: twitterapi.io, mcp.twitterapi.io, *.mcp.twitterapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.twitterapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| twitterapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="twitterapi.io", resource_metadata="https://mcp.twitterapi.io/.well-known/oauth-protected-resource"
Bearer realm="twitterapi.io", resource_metadata="https://mcp.twitterapi.io/.well-known/oauth-protected-resource"Protected resource metadata
| Document | https://mcp.twitterapi.io/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.twitterapi.io/mcp |
| Authorisation server | https://mcp.twitterapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.twitterapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.twitterapi.io/mcp | HTTPS enforced | 301 | https://mcp.twitterapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_trends Get Trending Topics ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Max trends to return (default API behavior; may be silently capped by API). |
| woeid | integer | yes | 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. |
No output schema declared.
No examples provided.
get_tweet_quotes Get Tweet Quotes ~149
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Numeric ID of the tweet to fetch quote-tweets for. |
| untilTime | integer | – | Unix timestamp (seconds) upper bound. |
No output schema declared.
No examples provided.
get_tweet_replies Get Tweet Replies ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Numeric ID of the tweet to fetch replies for. |
No output schema declared.
No examples provided.
get_tweet_retweeters Get Tweet Retweeters ~95
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).
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor; omit for first page (~100 per page). |
| tweetId | string | yes | Numeric ID of the tweet to fetch retweeters for. |
No output schema declared.
No examples provided.
get_tweets_by_ids Batch Get Tweets by IDs ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| tweet_ids | string | yes | Comma-separated tweet IDs (e.g. '1234567890,9876543210'). Batch fetch up to 100 tweets in one call. Tweet IDs are numeric strings. |
No output schema declared.
No examples provided.
get_user_about Get User About Page ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| userName | string | yes | Twitter/X screen name without @ — fetches the user's profile 'about' / bio page. |
No output schema declared.
No examples provided.
get_user_followers Get User Followers ~162
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Twitter/X screen name without @ — fetches followers of this user. |
No output schema declared.
No examples provided.
get_user_followings Get User Followings ~109
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).
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor; omit for first page. |
| pageSize | integer | – | Followings per page (default 200, max 200). Each includes full profile metadata. |
| userName | string | yes | Twitter/X screen name without @ — fetches accounts this user follows. |
No output schema declared.
No examples provided.
get_user_info Get User Profile ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| userName | string | yes | Twitter/X screen name (handle) WITHOUT the leading @ sign. Example: 'elonmusk', not '@elonmusk'. |
No output schema declared.
No examples provided.
get_user_last_tweets Get User's Recent Tweets ~296
⚠️ 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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_user_mentions Get Mentions of a User ~160
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Twitter/X screen name without @ — fetches tweets that mention this user (@userName). |
No output schema declared.
No examples provided.
search_tweets Search Tweets ~420
🎯 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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor from a previous response's next_cursor field. Omit for first page. Each page returns ~20 tweets. |
| query | string | yes | 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 | yes | 'Latest' returns most recent tweets first; 'Top' returns highest-engagement tweets first. Default to 'Latest' for time-sensitive queries. |
No output schema declared.
No examples provided.
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.