SocialData
REMOTE · API.SOCIALDATA.TOOLS · SCANNED SEP 20
Twitter (X) API alternative for AI agents: tweet search, profiles, followers. $0.0002 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 Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability79
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
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 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.
remote · api.socialdata.tools
claude mcp add --transport http tools-socialdata-socialdata 'https://api.socialdata.tools/mcp'
{
"mcpServers": {
"tools-socialdata-socialdata": {
"url": "https://api.socialdata.tools/mcp"
}
}
} {
"servers": {
"tools-socialdata-socialdata": {
"type": "http",
"url": "https://api.socialdata.tools/mcp"
}
}
} [mcp_servers.tools-socialdata-socialdata] url = "https://api.socialdata.tools/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tools-socialdata-socialdata": {
"type": "remote",
"url": "https://api.socialdata.tools/mcp",
"enabled": true
}
}
} openclaw mcp add tools-socialdata-socialdata --url 'https://api.socialdata.tools/mcp' --transport streamable-http
mcp_servers:
tools-socialdata-socialdata:
url: "https://api.socialdata.tools/mcp" {
"McpServers": {
"tools-socialdata-socialdata": {
"Transport": "http",
"Url": "https://api.socialdata.tools/mcp"
}
}
} assistant mcp add tools-socialdata-socialdata -t streamable-http -u 'https://api.socialdata.tools/mcp'
{
"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.
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.
- 20 Sept 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 19 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 18 Sept 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 17 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 16 Sept 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 15 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 14 Sept 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 13 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
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 20 Sept 2026 · Probed https://api.socialdata.tools/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=socialdata.tools | CN=WE1,O=Google Trust Services,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | be3424a2ae540f2913cc906b6df66662 |
| SANs: socialdata.tools, *.socialdata.tools | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.socialdata.tools. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tools. | present | 13831 | 8 | Verified |
| socialdata.tools. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp", error="invalid_token"
Bearer realm="mcp", error="invalid_token"Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.socialdata.tools/mcp | Verified | 200 | |
| http (plaintext) | http://api.socialdata.tools/mcp | Inconclusive | 405 |
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 →
check_is_following Check Is Following Tool ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| source_user_id | string | yes | The numeric ID of the user who might be following, as a string. |
| target_user_id | string | yes | The numeric ID of the user who might be followed, as a string. |
No output schema declared.
No examples provided.
get_list_tweets Get List Tweets Tool ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor from a previous call's next_cursor. Omit for the first page. |
| list_id | string | yes | The numeric Twitter/X list ID, as a string. |
No output schema declared.
No examples provided.
get_tweet Get Tweet Tool ~50
Fetch a single Twitter/X post by its numeric ID, including engagement counts. Bills one post request against the caller's balance.
| Name | Type | Req | Description |
|---|---|---|---|
| tweet_id | string | yes | The numeric post ID, as a string. |
No output schema declared.
No examples provided.
get_tweet_comments Get Tweet Comments Tool ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor from a previous call's next_cursor. Omit for the first page. |
| tweet_id | string | yes | The numeric ID of the post whose replies you want, as a string. |
No output schema declared.
No examples provided.
get_tweet_thread Get Tweet Thread Tool ~177
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor from a previous call's next_cursor. Omit for the first page. |
| tweet_id | string | yes | The numeric post ID, as a string. |
No output schema declared.
No examples provided.
get_user_by_id Get User By Id Tool ~56
Look up a Twitter/X user profile by numeric user ID. Bills one user request against the caller's balance.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | The numeric Twitter/X user ID, as a string (IDs exceed safe integer precision). |
No output schema declared.
No examples provided.
get_user_by_username Get User By Username Tool ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| username | string | yes | The Twitter/X username (handle), with or without the leading @. |
No output schema declared.
No examples provided.
get_user_followers Get User Followers Tool ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor from a previous call's next_cursor. Omit for the first page. |
| user_id | string | yes | The numeric Twitter/X user ID whose followers you want, as a string. |
No output schema declared.
No examples provided.
get_user_following Get User Following Tool ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor from a previous call's next_cursor. Omit for the first page. |
| user_id | string | yes | The numeric Twitter/X user ID whose following list you want, as a string. |
No output schema declared.
No examples provided.
get_user_mentions Get User Mentions Tool ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor from a previous call's next_cursor. Omit for the first page. |
| username | string | yes | The Twitter/X username (handle) being mentioned, with or without the leading @. |
No output schema declared.
No examples provided.
get_user_tweets Get User Tweets Tool ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor from a previous call's next_cursor. Omit for the first page. |
| user_id | string | yes | The numeric Twitter/X user ID, as a string. |
No output schema declared.
No examples provided.
get_user_tweets_and_replies Get User Tweets And Replies Tool ~131
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor from a previous call's next_cursor. Omit for the first page. |
| user_id | string | yes | The numeric Twitter/X user ID, as a string. |
No output schema declared.
No examples provided.
search_tweets Search Tweets Tool ~283
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
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor from a previous call's next_cursor. Omit for the first page. |
| query | string | yes | 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. |
No output schema declared.
No examples provided.
search_users Search Users Tool ~60
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Name or handle to search for. |
No output schema declared.
No examples provided.
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.