Skip to content

SocialData MCP server

tools.socialdata/socialdatasocialdata.toolsstreamable-httpv1.0.0Scanned

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

14 tools: 1 change things and 13 only read.

Tools: 0 delete, 0 irreversible, 1 write, 13 read.
  • Reads private data · 1
  • Reads text others write · 8
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the SocialData MCP server can do

The SocialData MCP server is published by socialdata.tools, a domain the MCP Registry verified. It has 14 tools. It can create or change data (1 tool: check_is_following), but cannot delete data. 13 tools only read.

1 tool reads private data (get_tweet_thread); 8 tools bring in text other people can write (get_tweet, get_tweet_thread, get_tweet_comments and 5 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 19, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

14 tools

Changes things 1Claude Code: ask
  • check_is_followingCheck whether one Twitter/X user follows another.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
Only reads 13Show 13 read-only tools
  • get_list_tweetsFetch one page of posts from a Twitter/X list, newest first.Reads text others writeNo findings

    Why it is in this group

    • The name "get_list_tweets" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe name "get_list_tweets" says "get" and "tweet": it reads posts, which other people can write.
    • untrusted-inputThe description's first sentence says "fetch" and "post": it reads posts, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
  • get_tweetFetch a single Twitter/X post by its numeric ID, including engagement counts.Reads text others writeNo findings

    Why it is in this group

    • The name "get_tweet" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe name "get_tweet" says "get" and "tweet": it reads posts, which other people can write.
    • untrusted-inputThe description's first sentence says "fetch" and "post": it reads posts, which other people can write.
    Description, as the server wrote it
    Fetch a single Twitter/X post by its numeric ID, including engagement counts. Bills one post request against the caller's balance.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
  • get_tweet_commentsFetch one page of replies to a Twitter/X post.Reads text others writeNo findings

    Why it is in this group

    • The name "get_tweet_comments" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe name "get_tweet_comments" says "get" and "tweet": it reads posts, which other people can write.
    • untrusted-inputThe description's first sentence says "fetch" and "reply": it reads comments, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
  • get_tweet_threadFetch one page of a Twitter/X thread — the chain of follow-up posts the author wrote under their own post ("1/", "2/", ...).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_tweet_thread" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_tweet_thread" says "get" and "thread": it reads messages.
    • private-dataThe description's first sentence says "fetch" and "thread": it reads messages.
    • untrusted-inputThe name "get_tweet_thread" says "get" and "tweet": it reads posts, which other people can write.
    • untrusted-inputThe description's first sentence says "fetch" and "thread": it reads messages, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
  • get_user_by_idLook up a Twitter/X user profile by numeric user ID.No findings

    Why it is in this group

    • The name "get_user_by_id" says "get": a word for reading.
    Description, as the server wrote it
    Look up a Twitter/X user profile by numeric user ID. Bills one user request against the caller's balance.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
  • get_user_by_usernameLook up a Twitter/X user profile by username (handle).No findings

    Why it is in this group

    • The name "get_user_by_username" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
  • get_user_followersFetch one page of a user's followers.No findings

    Why it is in this group

    • The name "get_user_followers" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
  • get_user_followingFetch one page of the accounts a user follows.No findings

    Why it is in this group

    • The name "get_user_following" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
  • get_user_mentionsFetch one page of posts mentioning a given user, newest first.Reads text others writeNo findings

    Why it is in this group

    • The name "get_user_mentions" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe name "get_user_mentions" says "get" and "mention": it reads comments, which other people can write.
    • untrusted-inputThe description's first sentence says "fetch" and "post": it reads posts, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
  • get_user_tweetsFetch one page of a user's own posts (excluding replies), newest first.Reads text others writeNo findings

    Why it is in this group

    • The name "get_user_tweets" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe name "get_user_tweets" says "get" and "tweet": it reads posts, which other people can write.
    • untrusted-inputThe description's first sentence says "fetch" and "post": it reads posts, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
  • get_user_tweets_and_repliesFetch one page of a user's posts including their replies, newest first.Reads text others writeNo findings

    Why it is in this group

    • The name "get_user_tweets_and_replies" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe name "get_user_tweets_and_replies" says "get" and "tweet": it reads posts, which other people can write.
    • untrusted-inputThe description's first sentence says "fetch" and "post": it reads posts, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
  • search_tweetsSearch Twitter/X posts.Reads text others writeNo findings

    Why it is in this group

    • The name "search_tweets" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe name "search_tweets" says "search" and "tweet": it reads posts, which other people can write.
    • untrusted-inputThe description's first sentence says "search" and "post": it reads posts, which other people can write.
    Description, as the server wrote it
    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

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
  • search_usersSearch Twitter/X user profiles by name or handle.No findings

    Why it is in this group

    • The name "search_users" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write8
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:19 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.socialdata.tools/mcp: tools/list returned 14 tools to an anonymous client, including check_is_following (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http socialdata https://api.socialdata.tools/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http socialdata https://api.socialdata.tools/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__socialdata__get_user_by_username",
      "mcp__socialdata__get_user_by_id",
      "mcp__socialdata__search_users",
      "mcp__socialdata__get_tweet",
      "mcp__socialdata__get_tweet_thread",
      "mcp__socialdata__get_tweet_comments",
      "mcp__socialdata__get_user_tweets",
      "mcp__socialdata__get_user_tweets_and_replies",
      "mcp__socialdata__get_user_mentions",
      "mcp__socialdata__get_user_followers",
      "mcp__socialdata__get_user_following",
      "mcp__socialdata__search_tweets",
      "mcp__socialdata__get_list_tweets"
    ],
    "ask": [
      "mcp__socialdata__check_is_following"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as socialdata. Review it before you use it.

Capability tags behind 8 rules
  • mcp__socialdata__get_tweet untrusted-input
  • mcp__socialdata__get_tweet_thread private-data, untrusted-input
  • mcp__socialdata__get_tweet_comments untrusted-input
  • mcp__socialdata__get_user_tweets untrusted-input
  • mcp__socialdata__get_user_tweets_and_replies untrusted-input
  • mcp__socialdata__get_user_mentions untrusted-input
  • mcp__socialdata__search_tweets untrusted-input
  • mcp__socialdata__get_list_tweets untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/tools.socialdata/socialdata/verify?hash=9e34443dcaf36650617a9db6248aa14d8545673f7224c6d11dd51635371a3c4e" | jq -e '.changed == false'

Pinned hash 9e34443dcaf3, from Nov 19, 2026, 07:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/tools.socialdata/socialdata/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for tools.socialdata/socialdata
[![Anlyon Radar](https://radar.anlyon.com/badge/tools.socialdata/socialdata.svg)](https://radar.anlyon.com/servers/tools.socialdata/socialdata)

Source: MCP Registry. Synced Oct 21, 2026, 18:55 UTC.

SocialData MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the SocialData MCP server safe?

No scan can promise that. What its definitions show: 14 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the SocialData MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the SocialData MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the SocialData MCP server have?

14 tools: 1 write, 13 read. check_is_following, get_user_by_username, get_user_by_id, search_users, get_tweet, get_tweet_thread, get_tweet_comments, get_user_tweets and 6 more.

Does the SocialData MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the SocialData MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the SocialData MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.