io.github.zezeron/tweetsave-mcp
NPM · TWEETSAVE-MCP · 2 COMPONENTS · SCANNED SEP 20
Twitter/X analysis without token waste. Fetch tweets, download media. No API key.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 34 of 109 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency44
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 241 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1023 tokens (~204/item across 5 items; 5 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 Management90
- Stability observed for 27 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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 io.github.zezeron/tweetsave-mcp server?
io.github.zezeron/tweetsave-mcp runs locally as an npm package, launched with npx -y tweetsave-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · tweetsave-mcp
claude mcp add zezeron-tweetsave-mcp -- npx -y tweetsave-mcp
{
"mcpServers": {
"zezeron-tweetsave-mcp": {
"command": "npx",
"args": [
"-y",
"tweetsave-mcp"
]
}
}
} {
"servers": {
"zezeron-tweetsave-mcp": {
"command": "npx",
"args": [
"-y",
"tweetsave-mcp"
]
}
}
} codex mcp add zezeron-tweetsave-mcp -- npx -y tweetsave-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"zezeron-tweetsave-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"tweetsave-mcp"
],
"enabled": true
}
}
} openclaw mcp add zezeron-tweetsave-mcp --command npx --arg -y --arg tweetsave-mcp
mcp_servers:
zezeron-tweetsave-mcp:
command: "npx"
args: ["-y", "tweetsave-mcp"] {
"McpServers": {
"zezeron-tweetsave-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"tweetsave-mcp"
]
}
}
} assistant mcp add zezeron-tweetsave-mcp -t stdio -c npx -a -y tweetsave-mcp
{
"mcpServers": {
"zezeron-tweetsave-mcp": {
"command": "npx",
"args": [
"-y",
"tweetsave-mcp"
]
}
}
} 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 0
- Security disclosure: unverified → fail ▼ functional
- 19 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 10 Sept 26 −3
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.80 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 · Analysed npm/tweetsave-mcp@1.0.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 109 packages
| Packages resolved | 109 |
|---|---|
| Stale | 34 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
tweetsave_batch Batch Fetch Tweets ~148
Fetch multiple tweets at once (max 10). Useful for: - Collecting tweets from a list - Building a feed from multiple sources - Comparing multiple tweets Args: - urls (string[]): Array of tweet URLs or IDs (max 10) - response_format ('markdown' | 'json'): Output format (default: 'markdown') Returns: Array of tweets or a combined feed in markdown format. Examples: - "Fetch these tweets: [url1, url2, url3]"
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | Output format: 'markdown' or 'json' |
| urls | array | yes | Array of tweet URLs or IDs (max 10) |
No output schema declared.
No examples provided.
tweetsave_extract_media Extract Media URLs ~192
Extract direct media URLs (photos, videos, GIFs) from a tweet. Returns direct URLs that can be downloaded or embedded. Video URLs are the highest quality available. Args: - url (string): Tweet URL or tweet ID - media_type ('all' | 'photos' | 'videos'): Filter by media type (default: 'all') Returns: List of media items with: - type (photo/video/gif) - url (direct download URL) - dimensions (width/height) - duration (for videos) Examples: - "Get all media from this tweet: https://x.com/user/status/123" - "Extract video URLs from tweet 123456"
| Name | Type | Req | Description |
|---|---|---|---|
| media_type | string | – | Type of media to extract: 'all', 'photos', or 'videos' |
| url | string | yes | Tweet URL or tweet ID |
No output schema declared.
No examples provided.
tweetsave_get_thread Get Tweet Thread ~155
Fetch a tweet thread (multiple connected tweets by the same author). Note: Current implementation fetches the main tweet. Full thread crawling requires additional API access. Args: - url (string): URL or ID of any tweet in the thread - response_format ('markdown' | 'json'): Output format (default: 'markdown') Returns: Array of tweets in the thread with all content and media. Examples: - "Get the full thread from this tweet: https://x.com/user/status/123"
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | Output format: 'markdown' for human-readable or 'json' for structured data |
| url | string | yes | URL or ID of any tweet in the thread |
No output schema declared.
No examples provided.
tweetsave_get_tweet Get Tweet ~268
Fetch a single tweet with all its content including text, media (photos, videos, GIFs), polls, and engagement metrics. This tool retrieves tweet data from Twitter/X using the FxTwitter API. It returns the tweet content, author info, media URLs, and engagement stats. Args: - url (string): Tweet URL or tweet ID - response_format ('markdown' | 'json'): Output format (default: 'markdown') Returns: Tweet data including: - Author info (name, username, avatar) - Tweet text - Media URLs (photos, videos) - Engagement (likes, retweets, replies, views) - Poll data (if applicable) - Quote tweet (if applicable) Examples: - "Get tweet from https://x.com/elonmusk/status/123456" - "Fetch this tweet: 123456789" Note: Does not fetch replies. Use tweetsave_to_blog for a complete blog post with formatting.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | Output format: 'markdown' for human-readable or 'json' for structured data |
| url | string | yes | Tweet URL or tweet ID. Examples: 'https://x.com/user/status/123456' or '123456' |
No output schema declared.
No examples provided.
tweetsave_to_blog Convert Tweet to Blog Post ~260
Convert a tweet into a formatted blog post with title, content, media, and metadata. This tool transforms a tweet into a readable blog post format, perfect for: - Archiving tweets - Creating content from threads - Generating blog posts from viral tweets Args: - url (string): Tweet URL or tweet ID - include_engagement (boolean): Include likes/retweets/etc. (default: true) - response_format ('markdown' | 'json'): Output format (default: 'markdown') Returns: BlogPost with: - Generated title from tweet content - Author info with avatar - Formatted content with media - Tags from hashtags - Read time estimate - Engagement summary - Source link Examples: - "Convert this tweet to a blog post: https://x.com/user/status/123" - "Make a blog from tweet 123456789"
| Name | Type | Req | Description |
|---|---|---|---|
| include_engagement | boolean | – | Include engagement metrics (likes, retweets, etc.) |
| response_format | string | – | Output format: 'markdown' for blog post or 'json' for structured data |
| url | string | yes | Tweet URL or tweet ID to convert |
No output schema declared.
No examples provided.
What is the io.github.zezeron/tweetsave-mcp server?
io.github.zezeron/tweetsave-mcp is listed in the public MCP registry as io.github.zezeron/tweetsave-mcp. Twitter/X analysis without token waste. Fetch tweets, download media. No API key. This page covers its npm package (tweetsave-mcp).
Is the io.github.zezeron/tweetsave-mcp server safe to use?
io.github.zezeron/tweetsave-mcp scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.zezeron/tweetsave-mcp server expose?
io.github.zezeron/tweetsave-mcp exposes 5 tools: tweetsave_get_tweet, tweetsave_get_thread, tweetsave_to_blog, tweetsave_batch, tweetsave_extract_media. Their descriptions and schemas cost roughly 1,023 tokens of context every time the server is loaded.
Is the io.github.zezeron/tweetsave-mcp server still maintained?
io.github.zezeron/tweetsave-mcp 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.
What licence is the io.github.zezeron/tweetsave-mcp server under?
io.github.zezeron/tweetsave-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.