Skip to content
Xdataapi logo

Xdataapi MCP server

Which servers in the official MCP registry are Xdataapi's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-15

← Back to Xdataapi

Whose server it is
  • Registry nameio.xdataapi/xdataapiverified in the MCP registry

The registry name sits under xdataapi.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-15
  • Stateanswerschecked 2026-10-15
  • Tools14
  • Server calls itselfxdataapi
  • Server version0.3.0+d6bdc82
  • Protocol version2025-06-18

On 2026-10-15 the server answered initialize and tools/list without a sign-in. First answer in 531 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: Pull tweet threads and replies for analysis; Search X posts using X search operators.
  • Checked on 4 of the 7 days it takes to judge reliability.

Once connected

  • For "Pull tweet threads and replies for analysis", the likely first call is get_thread.
  • For "Search X posts using X search operators", the likely first call is search_tweets.
  • Parameters are untyped or undescribed in 11 of 14 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 4, the first on 2026-10-19
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
  • What an agent can do with it2 of 2 use cases
  • Use1 GitHub stars
  • Answeredmeasuring4 of the 7 daily checks it takes to print a share
  • Median first answer528 ms
  • Space in an agent's context≈ 1,703 tokensthe definitions of all its tools (14), which an agent carries on every turn
  • Tool definitionsB · 87 of 100
  • Typed results0 of 14 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 11 of 14

What an agent can do with it

  • not sure · Look up public X profiles by handle
  • can do · Pull tweet threads and replies for analysis
  • can do · Search X posts using X search operators

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers14 tools · read 2026-10-15
  • get_user

    Profile of one X user by handle. 1 credit.

  • get_users

    Profiles of up to 100 X users by handle in one call. 1 credit per profile found.

  • get_user_tweets

    Latest tweets of a user, newest first. 1 credit per tweet.

  • get_followers

    Followers of a user. 0.1 credit per profile. Not every account tier can read this; a 403 is free.

  • get_follower_ids

    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.

  • get_following

    Accounts a user follows. 0.1 credit per profile. Not every account tier can read this; a 403 is free.

  • search_tweets

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

  • get_tweet

    One tweet by numeric id, with its author. 1 credit.

  • get_tweets

    Up to 100 tweets by numeric id in one call. 1 credit per tweet found.

  • get_thread

    A tweet with its thread and replies; the focal tweet comes first. 1 credit per tweet returned.

  • get_replies

    Direct replies to a tweet, one page. 1 credit per reply.

  • get_quotes

    Tweets that quote a tweet, newest first. 1 credit per tweet.

  • get_retweeters

    Accounts that retweeted a tweet. 0.5 credit per profile. Not every account tier can read this; a 403 is free.

  • get_balance

    Credits left on this key and its rate limit. Free.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "xdataapi": {
      "type": "http",
      "url": "https://api.xdataapi.io/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http xdataapi https://api.xdataapi.io/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://api.xdataapi.io/mcp as a custom connector in the settings.

OpenAPI spec

16 paths, read 2026-10-15. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.