io.github.pedrot95dev/twitterapi
NPM · @PEDROT95DEV/TWITTERAPI.MCP · SCANNED SEP 20
Read/write X (Twitter) via twitterapi.io: mentions, thread context, create and delete tweets.
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
- 31 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pedrot95dev/twitterapi.mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 78 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 552 tokens (~138/item across 4 items; 4 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_tweet" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 4 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.pedrot95dev/twitterapi MCP server?
io.github.pedrot95dev/twitterapi runs locally as an npm package, launched with npx -y @pedrot95dev/twitterapi.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 · @pedrot95dev/twitterapi.mcp
claude mcp add pedrot95dev-twitterapi -- npx -y @pedrot95dev/twitterapi.mcp
{
"mcpServers": {
"pedrot95dev-twitterapi": {
"command": "npx",
"args": [
"-y",
"@pedrot95dev/twitterapi.mcp"
]
}
}
} {
"servers": {
"pedrot95dev-twitterapi": {
"command": "npx",
"args": [
"-y",
"@pedrot95dev/twitterapi.mcp"
]
}
}
} codex mcp add pedrot95dev-twitterapi -- npx -y @pedrot95dev/twitterapi.mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pedrot95dev-twitterapi": {
"type": "local",
"command": [
"npx",
"-y",
"@pedrot95dev/twitterapi.mcp"
],
"enabled": true
}
}
} openclaw mcp add pedrot95dev-twitterapi --command npx --arg -y --arg @pedrot95dev/twitterapi.mcp
mcp_servers:
pedrot95dev-twitterapi:
command: "npx"
args: ["-y", "@pedrot95dev/twitterapi.mcp"] {
"McpServers": {
"pedrot95dev-twitterapi": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@pedrot95dev/twitterapi.mcp"
]
}
}
} assistant mcp add pedrot95dev-twitterapi -t stdio -c npx -a -y @pedrot95dev/twitterapi.mcp
{
"mcpServers": {
"pedrot95dev-twitterapi": {
"command": "npx",
"args": [
"-y",
"@pedrot95dev/twitterapi.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 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.77 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- 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/@pedrot95dev/twitterapi.mcp@0.1.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pedrot95dev/twitterapi.mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pedrot95dev/twitterapi.mcp/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 2061181968 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:726a88930cd90be5d712e486cfee7473e7981dfcd308050e5e6abb840e7bc685948ed2fa644d135fe9aab34299fb5332a3cf06f51d957b0530237dfca |
Background: How many MCP packages publish verified provenance →
Dependencies 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 31 |
| 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 →
create_tweet Create tweet ~213
Create or reply to a tweet via the v2 endpoint. Uses `login_cookies` built from the account's `auth_token`/`ct0` env vars (requires TWITTERAPI_IO_AUTH_TOKEN, TWITTERAPI_IO_CT0, TWITTERAPI_IO_PROXY).
| Name | Type | Req | Description |
|---|---|---|---|
| attachment_url | string | – | URL for quote (alternative to quote_tweet_id) |
| community_id | string | – | Post inside a specific community |
| is_note_tweet | boolean | – | Allow >280 chars (Premium accounts) |
| media_ids | array | – | Media IDs from prior /twitter/upload_media_v2 |
| quote_tweet_id | string | – | Tweet ID to quote |
| reply_to_tweet_id | string | – | Tweet ID to reply to (makes this a reply) |
| schedule_for | string | – | ISO-8601 future time e.g. 2026-01-20T10:00:00.000Z |
| tweet_text | string | yes | The text content of the tweet |
No output schema declared.
No examples provided.
delete_tweet Delete tweet ~62
Delete a tweet by ID (must be owned by the logged-in account). Uses `login_cookies` built from the account's `auth_token`/`ct0` env vars.
| Name | Type | Req | Description |
|---|---|---|---|
| tweet_id | string | yes | The ID of the tweet to delete |
No output schema declared.
No examples provided.
get_tweet_thread_context Get tweet thread context ~134
Fetch one page of the conversation thread around a tweet (to find links in context). Returns the original tweet, intermediate replies up the chain, the tweet itself, and its direct replies; each tweet includes `entities.urls` with expanded links. Makes exactly one request per call: pages are uneven (a page may be empty while `has_next_page` is true), so pass `next_cursor` back as `cursor` to fetch the next page.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor from a previous response's next_cursor |
| tweet_id | string | yes | The tweet ID to get the thread context for |
No output schema declared.
No examples provided.
get_user_mentions Get user mentions ~143
Fetch tweets mentioning a specific X/Twitter user. Makes a single request per call. The caller handles pagination by passing `cursor` (from a previous `next_cursor`).
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor from a previous response's next_cursor |
| limit | integer | – | Max tweets to return from this single request (default 50) |
| query_type | string | – | Sort mode (default Latest) |
| since_time | string | – | Start time filter (e.g. 2025-06-01 or ISO datetime) |
| until_time | string | – | End time filter |
| user_name | string | yes | X username, with or without @ |
No output schema declared.
No examples provided.
What is the io.github.pedrot95dev/twitterapi MCP server?
io.github.pedrot95dev/twitterapi is an MCP server listed in the public MCP registry as io.github.pedrot95dev/twitterapi. Read/write X (Twitter) via twitterapi.io: mentions, thread context, create and delete tweets. This page covers its npm package (@pedrot95dev/twitterapi.mcp).
Is the io.github.pedrot95dev/twitterapi MCP server safe to use?
io.github.pedrot95dev/twitterapi scores 92 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. Its build provenance is signed and verified. 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.pedrot95dev/twitterapi MCP server expose?
io.github.pedrot95dev/twitterapi exposes 4 tools: get_user_mentions, get_tweet_thread_context, create_tweet, delete_tweet. Their descriptions and schemas cost roughly 552 tokens of context every time the server is loaded.
Is the io.github.pedrot95dev/twitterapi MCP server still maintained?
io.github.pedrot95dev/twitterapi 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.pedrot95dev/twitterapi MCP server under?
io.github.pedrot95dev/twitterapi declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.