# SocialData (remote · api.socialdata.tools)

Twitter (X) API alternative for AI agents: tweet search, profiles, followers. $0.0002 per result.

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

## Components

- remote · `api.socialdata.tools`: 83/100 (this document), [markdown](https://verifymcp.io/servers/tools-socialdata-socialdata/api.md), [page](https://verifymcp.io/servers/tools-socialdata-socialdata/api)

## Channel facts

- Endpoint: `https://api.socialdata.tools/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.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**: 71/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1750 tokens (~125/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the SocialData MCP server?

SocialData is a hosted endpoint at https://api.socialdata.tools/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 tools-socialdata-socialdata 'https://api.socialdata.tools/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "tools-socialdata-socialdata": {
      "url": "https://api.socialdata.tools/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tools-socialdata-socialdata": {
      "type": "http",
      "url": "https://api.socialdata.tools/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tools-socialdata-socialdata]
url = "https://api.socialdata.tools/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tools-socialdata-socialdata": {
      "type": "remote",
      "url": "https://api.socialdata.tools/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tools-socialdata-socialdata --url 'https://api.socialdata.tools/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tools-socialdata-socialdata:
    url: "https://api.socialdata.tools/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tools-socialdata-socialdata": {
      "Transport": "http",
      "Url": "https://api.socialdata.tools/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tools-socialdata-socialdata -t streamable-http -u 'https://api.socialdata.tools/mcp'
```

### Other

```json
{
  "mcpServers": {
    "tools-socialdata-socialdata": {
      "type": "http",
      "url": "https://api.socialdata.tools/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 83, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-19 (score 82, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

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

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-17 (score 81, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

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

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-15 (score 80, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

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

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-13 (score 79, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

## MCP tools (14)

### `get_user_by_username` (~61 tokens)

Get User By Username Tool

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.

Input parameters:

- `username` (string, required): The Twitter/X username (handle), with or without the leading @.

### `get_user_by_id` (~56 tokens)

Get User By Id Tool

Look up a Twitter/X user profile by numeric user ID. Bills one user request against the caller's balance.

Input parameters:

- `user_id` (string, required): The numeric Twitter/X user ID, as a string (IDs exceed safe integer precision).

### `search_users` (~60 tokens)

Search Users Tool

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.

Input parameters:

- `query` (string, required): Name or handle to search for.

### `get_tweet` (~50 tokens)

Get Tweet Tool

Fetch a single Twitter/X post by its numeric ID, including engagement counts. Bills one post request against the caller's balance.

Input parameters:

- `tweet_id` (string, required): The numeric post ID, as a string.

### `get_tweet_thread` (~177 tokens)

Get Tweet Thread Tool

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. A post the author never followed up on is a one-post thread and correctly returns just that post. Roughly 30 posts per page plus a next_cursor, so a long thread takes several calls. Each call bills against the caller's balance — do not page through a long thread unless the user asked for that.

Input parameters:

- `cursor` (string): Pagination cursor from a previous call's next_cursor. Omit for the first page.
- `tweet_id` (string, required): The numeric post ID, as a string.

### `get_tweet_comments` (~125 tokens)

Get Tweet Comments Tool

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 conversation unless the user asked for that.

Input parameters:

- `cursor` (string): Pagination cursor from a previous call's next_cursor. Omit for the first page.
- `tweet_id` (string, required): The numeric ID of the post whose replies you want, as a string.

### `get_user_tweets` (~143 tokens)

Get User Tweets Tool

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 through a whole timeline unless the user asked for that. Requires a numeric user ID: call get_user_by_username first if you only have a handle.

Input parameters:

- `cursor` (string): Pagination cursor from a previous call's next_cursor. Omit for the first page.
- `user_id` (string, required): The numeric Twitter/X user ID, as a string.

### `get_user_tweets_and_replies` (~131 tokens)

Get User Tweets And Replies Tool

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 numeric user ID: call get_user_by_username first if you only have a handle.

Input parameters:

- `cursor` (string): Pagination cursor from a previous call's next_cursor. Omit for the first page.
- `user_id` (string, required): The numeric Twitter/X user ID, as a string.

### `get_user_mentions` (~113 tokens)

Get User Mentions Tool

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.

Input parameters:

- `cursor` (string): Pagination cursor from a previous call's next_cursor. Omit for the first page.
- `username` (string, required): The Twitter/X username (handle) being mentioned, with or without the leading @.

### `get_user_followers` (~113 tokens)

Get User Followers Tool

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.

Input parameters:

- `cursor` (string): Pagination cursor from a previous call's next_cursor. Omit for the first page.
- `user_id` (string, required): The numeric Twitter/X user ID whose followers you want, as a string.

### `get_user_following` (~111 tokens)

Get User Following Tool

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.

Input parameters:

- `cursor` (string): Pagination cursor from a previous call's next_cursor. Omit for the first page.
- `user_id` (string, required): The numeric Twitter/X user ID whose following list you want, as a string.

### `check_is_following` (~92 tokens)

Check Is Following Tool

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.

Input parameters:

- `source_user_id` (string, required): The numeric ID of the user who might be following, as a string.
- `target_user_id` (string, required): The numeric ID of the user who might be followed, as a string.

### `search_tweets` (~283 tokens)

Search Tweets Tool

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          posts by an account
  to:handle            replies to an account
  @handle              posts mentioning an account
  \#tag                 hashtag
  "exact phrase"       phrase match
  since:2026-01-01     posts on or after a date
  until:2026-02-01     posts before a date
  min_faves:100        at least N likes
  min_retweets:10      at least N retweets
  filter:links         posts containing links
  \-filter:replies      exclude replies
Combine them freely: from:jack min_faves:500 since:2026-01-01

Input parameters:

- `cursor` (string): Pagination cursor from a previous call's next_cursor. Omit for the first page.
- `query` (string, required): The search query. Supports Twitter advanced search operators such as from:, to:, since:, until:, min_faves: and filter:.
- `type` (string): Latest returns the newest matching posts; Top returns the most engaged-with. Defaults to Latest.

### `get_list_tweets` (~112 tokens)

Get List Tweets Tool

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.

Input parameters:

- `cursor` (string): Pagination cursor from a previous call's next_cursor. Omit for the first page.
- `list_id` (string, required): The numeric Twitter/X list ID, as a string.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tools-socialdata-socialdata/api#diagnostics

## Score history

- 2026-09-20: 83
- 2026-09-19: 82
- 2026-09-18: 82
- 2026-09-17: 81
- 2026-09-16: 81
- 2026-09-15: 80
- 2026-09-14: 80
- 2026-09-13: 79
- 2026-09-12: 79
- 2026-09-11: 79
- 2026-09-10: 78
- 2026-09-09: 78
- 2026-09-08: 77
- 2026-09-07: 77
- 2026-09-06: 76
- 2026-09-05: 76
- 2026-09-04: 75
- 2026-09-03: 75
- 2026-09-02: 74
- 2026-09-01: 74
- 2026-08-31: 73
- 2026-08-30: 73
- 2026-08-29: 72
- 2026-08-28: 72
- 2026-08-27: 72
- 2026-08-26: 71
- 2026-08-25: 69

## Common questions

### What is the SocialData MCP server?

SocialData is an MCP server listed in the public MCP registry as tools.socialdata/socialdata. Twitter (X) API alternative for AI agents: tweet search, profiles, followers. $0.0002 per result. This page covers its hosted endpoint (https://api.socialdata.tools/mcp).

### Is the SocialData MCP server safe to use?

SocialData scores 83 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 SocialData MCP server expose?

SocialData exposes 14 tools: get_user_by_username, get_user_by_id, search_users, get_tweet, get_tweet_thread, and 9 more. Their descriptions and schemas cost roughly 1,627 tokens of context every time the server is loaded.

### Does the SocialData MCP server require authentication?

Yes. SocialData 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 SocialData MCP server still maintained?

SocialData 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://api.socialdata.tools/mcp
- Authorisation metadata: https://api.socialdata.tools/.well-known/oauth-protected-resource/mcp
- Website: https://socialdata.tools/
- Changelog RSS feed: https://verifymcp.io/servers/tools-socialdata-socialdata/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/tools-socialdata-socialdata/api.json
- HTML version of this page: https://verifymcp.io/servers/tools-socialdata-socialdata/api