xdataapi: X (Twitter) data
REMOTE · API.XDATAAPI.IO · SCANNED SEP 23
Read-only public X (Twitter) data: profiles, tweets, threads, followers, search. Pay per result.
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 Security97
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1115 tokens (~79/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 70% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the xdataapi: X (Twitter) data MCP server?
xdataapi: X (Twitter) data is a hosted endpoint at https://api.xdataapi.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 · api.xdataapi.io
claude mcp add --transport http io-xdataapi-xdataapi 'https://api.xdataapi.io/mcp'
{
"mcpServers": {
"io-xdataapi-xdataapi": {
"url": "https://api.xdataapi.io/mcp"
}
}
} {
"servers": {
"io-xdataapi-xdataapi": {
"type": "http",
"url": "https://api.xdataapi.io/mcp"
}
}
} [mcp_servers.io-xdataapi-xdataapi] url = "https://api.xdataapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-xdataapi-xdataapi": {
"type": "remote",
"url": "https://api.xdataapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-xdataapi-xdataapi --url 'https://api.xdataapi.io/mcp' --transport streamable-http
mcp_servers:
io-xdataapi-xdataapi:
url: "https://api.xdataapi.io/mcp" {
"McpServers": {
"io-xdataapi-xdataapi": {
"Transport": "http",
"Url": "https://api.xdataapi.io/mcp"
}
}
} assistant mcp add io-xdataapi-xdataapi -t streamable-http -u 'https://api.xdataapi.io/mcp'
{
"mcpServers": {
"io-xdataapi-xdataapi": {
"type": "http",
"url": "https://api.xdataapi.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.
- 23 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.3.0+1270fca → 0.3.0+1006e3d functional
- 22 Sept 26 +40
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: 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. security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 70 functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- 20 Sept 26 39
First indexed and scored.
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 23 Sept 2026 · Probed https://api.xdataapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.xdataapi.io | CN=YE2,O=Let's Encrypt,C=US | 20 Sept 2026 | 19 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6ebe1e037f0157023bd7350afaff62ed67f |
| SANs: api.xdataapi.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.xdataapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| xdataapi.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="xdataapi.io", resource_metadata="https://api.xdataapi.io/.well-known/oauth-protected-resource"
Bearer realm="xdataapi.io", resource_metadata="https://api.xdataapi.io/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
Protected resource metadata
| Document | https://api.xdataapi.io/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://api.xdataapi.io/mcp |
| Authorisation server | https://tweetapi.dev |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.xdataapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://api.xdataapi.io/mcp | HTTPS enforced | 308 | https://api.xdataapi.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_balance Balance ~20
Credits left on this key and its rate limit. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_follower_ids Follower ids ~109
Numeric ids of the followers of a user, no profiles. 0.02 credit per id. Same page as get_followers, so a page read there is a cache hit here. A 403 is free.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| cursor | string | – | next_cursor from the previous page |
| fresh | boolean | – | Bypass the cache. Costs 2x credits. |
| user | string | yes | Handle (with or without @) or numeric user id |
No output schema declared.
No examples provided.
get_followers Followers ~91
Followers of a user. 0.1 credit per profile. Not every account tier can read this; a 403 is free.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| cursor | string | – | next_cursor from the previous page |
| fresh | boolean | – | Bypass the cache. Costs 2x credits. |
| user | string | yes | Handle (with or without @) or numeric user id |
No output schema declared.
No examples provided.
get_following Following ~91
Accounts a user follows. 0.1 credit per profile. Not every account tier can read this; a 403 is free.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| cursor | string | – | next_cursor from the previous page |
| fresh | boolean | – | Bypass the cache. Costs 2x credits. |
| user | string | yes | Handle (with or without @) or numeric user id |
No output schema declared.
No examples provided.
get_quotes Quotes ~67
Tweets that quote a tweet, newest first. 1 credit per tweet.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| cursor | string | – | next_cursor from the previous page |
| fresh | boolean | – | Bypass the cache. Costs 2x credits. |
| id | string | yes | – |
No output schema declared.
No examples provided.
get_replies Replies ~61
Direct replies to a tweet, one page. 1 credit per reply.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | next_cursor from the previous page |
| fresh | boolean | – | Bypass the cache. Costs 2x credits. |
| id | string | yes | – |
No output schema declared.
No examples provided.
get_retweeters Retweeters ~83
Accounts that retweeted a tweet. 0.5 credit per profile. Not every account tier can read this; a 403 is free.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| cursor | string | – | next_cursor from the previous page |
| fresh | boolean | – | Bypass the cache. Costs 2x credits. |
| id | string | yes | – |
No output schema declared.
No examples provided.
get_thread Thread ~66
A tweet with its thread and replies; the focal tweet comes first. 1 credit per tweet returned.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | next_cursor from the previous page |
| fresh | boolean | – | Bypass the cache. Costs 2x credits. |
| id | string | yes | – |
No output schema declared.
No examples provided.
get_tweet Tweet ~47
One tweet by numeric id, with its author. 1 credit.
| Name | Type | Req | Description |
|---|---|---|---|
| fresh | boolean | – | Bypass the cache. Costs 2x credits. |
| id | string | yes | – |
No output schema declared.
No examples provided.
get_tweets Tweets, batch ~52
Up to 100 tweets by numeric id in one call. 1 credit per tweet found.
| Name | Type | Req | Description |
|---|---|---|---|
| fresh | boolean | – | Bypass the cache. Costs 2x credits. |
| ids | array | yes | – |
No output schema declared.
No examples provided.
get_user Profile ~50
Profile of one X user by handle. 1 credit.
| Name | Type | Req | Description |
|---|---|---|---|
| fresh | boolean | – | Bypass the cache. Costs 2x credits. |
| handle | string | yes | Handle, with or without @ |
No output schema declared.
No examples provided.
get_user_tweets User tweets ~88
Latest tweets of a user, newest first. 1 credit per tweet.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Page size, 1 to 100 |
| cursor | string | – | next_cursor from the previous page |
| fresh | boolean | – | Bypass the cache. Costs 2x credits. |
| user | string | yes | Handle (with or without @) or numeric user id |
No output schema declared.
No examples provided.
get_users Profiles, batch ~53
Profiles of up to 100 X users by handle in one call. 1 credit per profile found.
| Name | Type | Req | Description |
|---|---|---|---|
| fresh | boolean | – | Bypass the cache. Costs 2x credits. |
| handles | array | yes | – |
No output schema declared.
No examples provided.
search_tweets Search ~124
X advanced search. q takes the x.com operators. 1 credit per tweet or profile. product Latest is always available; Top may answer 403 (free).
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| cursor | string | – | next_cursor from the previous page |
| fresh | boolean | – | Bypass the cache. Costs 2x credits. |
| product | string | – | Default Latest. People returns profiles. |
| q | string | yes | Query with x.com operators, e.g. "from:x since:2026-09-01 -filter:replies" |
No output schema declared.
No examples provided.
What is the xdataapi: X (Twitter) data MCP server?
xdataapi: X (Twitter) data is an MCP server listed in the public MCP registry as io.xdataapi/xdataapi. Read-only public X (Twitter) data: profiles, tweets, threads, followers, search. Pay per result. This page covers its hosted endpoint (https://api.xdataapi.io/mcp).
Is the xdataapi: X (Twitter) data MCP server safe to use?
xdataapi: X (Twitter) data scores 80 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 xdataapi: X (Twitter) data MCP server expose?
xdataapi: X (Twitter) data exposes 14 tools: get_user, get_users, get_user_tweets, get_followers, get_follower_ids, and 9 more. Their descriptions and schemas cost roughly 1,002 tokens of context every time the server is loaded.
Does the xdataapi: X (Twitter) data MCP server require authentication?
Yes. xdataapi: X (Twitter) data 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 xdataapi: X (Twitter) data MCP server still maintained?
xdataapi: X (Twitter) data is still listed as active in the MCP registry. We last reached this channel on 23 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.