SocialData
by socialdata.tools in News & content
Twitter (X) API alternative for AI agents: tweet search, profiles, followers. $0.0002 per result.
https://api.socialdata.tools/mcp
Last 30 days
Status and outage history · Atom feed
- Uptime
- 100%
- Response time
- 311 ms typical, 338 ms slowest 5%
- Last check
- 6 h ago
- Next check
- any minute now
How to call it
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"socialdata": {
"type": "http",
"url": "https://api.socialdata.tools/mcp"
}
}
}14 tools
- get_user_by_username
Look up a Twitter/X user profile by username (handle). Returns the profile including follower and following counts. Bills one user request against the caller's balance.
- get_user_by_id
Look up a Twitter/X user profile by numeric user ID. Bills one user request against the caller's balance.
- search_users
Search Twitter/X user profiles by name or handle. Returns one page of matching profiles and bills against the caller's balance. Use this when you know roughly who someone is but not their exact handle.
- get_tweet
Fetch a single Twitter/X post by its numeric ID, including engagement counts. Bills one post request against the caller's balance.
- get_tweet_thread
Fetch one page of a Twitter/X thread — the chain of follow-up posts the author wrote under their own post ("1/", "2/", ...). Give it the ID of any post in the chain and it returns that chain in order. It does NOT return what other people replied; use get_tweet_comments for those.
- get_tweet_comments
Fetch one page of replies to a Twitter/X post. Returns about 20 replies plus a next_cursor. The first item of a page can repeat the last item of the previous page, so de-duplicate by post id when paging. Each call bills against the caller's balance — do not page through the whole
- get_user_tweets
Fetch one page of a user's own posts (excluding replies), newest first. Returns about 20 posts plus a next_cursor. If the account has a pinned post it is prepended to every page, so de-duplicate by post id when paging. Each call bills against the caller's balance — do not page th
- get_user_tweets_and_replies
Fetch one page of a user's posts including their replies, newest first. Returns about 20 items plus a next_cursor. If the account has a pinned post it is prepended to every page, so de-duplicate by post id when paging. Each call bills against the caller's balance. Requires a nume
- get_user_mentions
Fetch one page of posts mentioning a given user, newest first. Returns about 20 posts plus a next_cursor. The first item of a page can repeat the last item of the previous page, so de-duplicate by post id when paging. Each call bills against the caller's balance.
- get_user_followers
Fetch one page of a user's followers. This is one of the most expensive tools: a page is set upstream and can run to ~100 user records, every one of which is billed. Never page through a large account's followers without the user explicitly asking. Requires a numeric user ID.
- get_user_following
Fetch one page of the accounts a user follows. Expensive: a page is set upstream and can run to ~100 user records, every one of which is billed. Never page through a large account's following list without the user explicitly asking. Requires a numeric user ID.
- check_is_following
Check whether one Twitter/X user follows another. Far cheaper than fetching a follower list — use this whenever the question is about a specific pair of accounts. Both IDs must be numeric.
- search_tweets
Search Twitter/X posts. Returns one page of about 20 results plus a next_cursor, and bills one search request against the caller's balance. The query supports Twitter's advanced search operators, and using them is almost always better than a bare keyword search: from:handle
- get_list_tweets
Fetch one page of posts from a Twitter/X list, newest first. A page is large — around 100 posts — plus a next_cursor. Billing is per result, so one call here costs several times a single-user timeline call; do not page through a busy list unless the user asked for that.
Security scan
- No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 6 h ago | Passed | 200 | 227 ms |
| 15 h ago | Passed | 200 | 329 ms |
| 25 h ago | Passed | 200 | 317 ms |
| 34 h ago | Passed | 200 | 311 ms |
| 44 h ago | Passed | 200 | 292 ms |
| 2 days ago | Passed | 200 | 295 ms |
| 3 days ago | Passed | 200 | 441 ms |
| 3 days ago | Passed | 200 | 338 ms |