Media · Remote MCP server
X Twitter Profile Tweets
X (Twitter) profiles, tweets and single-tweet lookup by handle or URL. No login. Pay per result.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.mrocker/x-twitter-profile-tweets- Version
- 1.0.0
- Status
- Active
- Category
- media
- Transport
- Streamable HTTP
- Published
- 2026-08-29
- Updated
- 2026-08-29
- Publisher
- mrocker (GitHub) · 4 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/mrocker) · how
- Listed under
- X (Twitter) MCP servers
- Website
- apify.com/nick.cheng/x-twitter-profile-tweets-scraper
- Repository
- github.com/mrocker/social-data-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.apify.com/?tools=nick.cheng/x-twitter-profile-tweets-scraper | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; a Bearer token is asked for
- Checked on
- 2026-10-05
How to connect X Twitter Profile Tweets
X Twitter Profile Tweets is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.apify.com/?tools=nick.cheng/x-twitter-profile-tweets-scraper, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from mrocker (GitHub)
| Server | Runs |
|---|---|
| Social Data MCPX/Twitter, YouTube and TikTok data tools in one stdio MCP server (Apify-hosted). Pay per result. | Local · stdio |
| Tiktok Profile StatsTikTok profiles (followers, bio) and per-video stats by handle or URL. No login. Pay per result. | Remote · HTTPLive check: sign-in required |
| Youtube Video ChannelYouTube video metadata and channel data by URL or @handle. No API key or quota. Pay per result. | Remote · HTTPLive check: sign-in required |
More media servers
| Server | Runs |
|---|---|
| X MCP AiSafety-first X (Twitter) API v2 MCP server: 41 typed tools across 12 packages, policy-gated. | Local · stdio |
| X TwitterX (twitter): x, xapi, Twitter, twitter api, twitters,tweets, tw, twttr, FollowerIds, friendsIds. | Remote · HTTPLive check: ✓ handshake |
| X TwitterX (formerly Twitter) posts, profiles, and search for AI agents. Free key, self-minted, no signup. | Remote · HTTPLive check: sign-in required |
| X Twitter DataX (Twitter) data for AI agents: tweets, profiles, followers, search, trends + social listening. | Remote · HTTPLive check: sign-in required |
| x-useBrowser-native AI agents for X (Twitter): multi-account, MCP-ready, no X API key required. | Local · stdio |
| x402-video MCPPay-per-call AI video generation over x402 (USDC on Base). No accounts, no API keys. | Local · stdio |
| x402imageX402 image tools (USDC/Base): remove_background/upscale $0.02, resize/optimize $0.005; URL in/out. | Remote · HTTPLive check: ✓ handshake |
| XActionsX/Twitter automation MCP: scrape, post, schedule, analyze, engage. No API key required. | Local · stdio |