# Socialdata MCP server

Source: https://glimind.com/server/mcp-registry%2Ftools.socialdata%2Fsocialdata
Registry id: `mcp-registry/tools.socialdata/socialdata`
Status: live (checked 2026-10-27T04:27:20.547Z)

## Verdict

Socialdata MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 865 ms median handshake and 0 outages in 90 days. Its agent-readiness grade is A (96/100) across 14 tools, costing an agent about 2,356 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 865 ms | 24% of MCP servers |
| p95 handshake latency | 3065 ms | — |
| Checks in 30 days | 4,982 | — |
| Outages, 90 days | 0 | — |
| Median recovery | — | — |
| Agent-readiness score | 96/100 (A) | 82% of MCP servers |
| Tools | 14 | — |
| Tool-list size for an agent | ~2,356 tokens | 50% of MCP servers |
| Days observed | 29 | — |

## Install

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

Claude Code:

```sh
claude mcp add --transport http socialdata-mcp-server https://api.socialdata.tools/mcp
```

## Tools (14)

- `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 account
- `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 co
- `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_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 pa
- `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 c
- `get_user_by_id`: Look up a Twitter/X user profile by numeric user ID. Bills one user request against the caller's balance.
- `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 
- `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 bi
- `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 thro
- `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 t
- `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 prepen
- `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 prepen
- `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 T
- `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 w

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.