A
licenseNot graded
qualityC
maintenanceEnables reading public X/Twitter posts by URL or numeric ID and returning original structured data, including articles, quoted posts, and media fields, without requiring an X API key.
MIT
x-reader-mcp
Server Details
Read public X posts and full X Articles as clean Markdown. Free, no X API key.
If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- Repository
- danishaali9/x-reader-mcp
- GitHub Stars
- 0
- Server Listing
- X Reader MCP
TDQS
A4.3/5.0
Scored across 1 tool
Disambiguation5/5
There is only one tool, so there is no possibility of misselection between tools. Its purpose—fetching a single X post as Markdown—is stated unambiguously, including explicit exclusions (no replies, no threads).
Naming Consistency4/5
The single name `read_x_post` follows a clear verb_noun convention and is descriptive of the action and resource. With only one tool there is no pattern to compare against, so consistency is trivially satisfied but cannot be demonstrated across a set.
Tool Count3/5
One tool matches the narrow 'read an X post' purpose, but the surface feels thin for a reader-style server—natural siblings like fetching a thread, replies, or a user's timeline are absent. It is borderline rather than clearly well-scoped.
Completeness3/5
The core operation (single post, including long-form Articles, media, polls, quotes) is covered well. However, the description itself flags dead ends—no reply retrieval and no multi-post thread assembly—which are common follow-up needs when a user shares an X link.
Available Tools
1 toolread_x_postRead X post or articleARead-onlyInspect
Reads a public X (Twitter) post and returns it as Markdown: author, date, engagement, text, images, video links, polls, quoted post, and the FULL body of X Articles (long-form posts). Use it whenever the user shares an x.com or twitter.com status link. Does not return replies or full multi-post threads.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Post URL like https://x.com/user/status/123... (twitter.com, fxtwitter.com etc. also work) or a bare numeric post ID. |
TDQS
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered structurally; the description adds real value by disclosing the Markdown return shape and the article-body behavior. It stops short of covering failure modes an agent will hit in practice — deleted posts, protected/private accounts, or age-restricted content.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, all load-bearing: what it returns, when to call it, and what it excludes. The exclusions are placed last so the positive capability is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists, but the description compensates by enumerating the returned fields, which is the main thing an agent needs to know before calling. For a one-parameter read tool with strong annotations, nothing essential is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the single url parameter is already well documented in the schema, including accepted alternate domains and the bare-post-ID form. The description adds nothing about the parameter, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ("Reads a public X (Twitter) post") and then enumerates exactly what is returned: author, date, engagement, text, images, video links, polls, quoted post, and full X Article bodies. That level of specificity makes the tool unmistakable even with no siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives an explicit trigger ("Use it whenever the user shares an x.com or twitter.com status link") and explicit exclusions ("Does not return replies or full multi-post threads"), so an agent knows both when to call it and when this tool is the wrong choice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- First observed
read_x_post
Related MCP Connectors
Read public X (Twitter) posts, threads and X Articles as clean Markdown. Read-only, no auth.
Read public Twitter/X data: tweets, profiles, followers, search. No X developer account.
Read any public web page as clean Markdown for LLMs. Respects robots.txt. Free tier; x402 paid API.
Extract clean article text or Markdown from any public web page; ads and boilerplate stripped.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceConverts X (Twitter) posts into JSON, PDF, PNG, Markdown, or Slack/Discord messages using public endpoints, no API key or login required.MIT
- AlicenseAqualityDmaintenanceEnables saving X (Twitter) Articles as Obsidian-faithful Markdown files with locally downloaded images and videos.18 npmMIT
- AlicenseAqualityCmaintenanceEnables reading public X (Twitter) content like profiles, tweets, and search results via a stealth browser, without official API costs.1117 PyPIMIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.