Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.pedrot95dev/twitterapi

NPM · @PEDROT95DEV/TWITTERAPI.MCP

Read/write X (Twitter) via twitterapi.io: mentions, thread context, create and delete tweets.

0 this week 88 Trust /100

Last scanned (21 hours ago)

Scores higher than 92% of npm servers

Category News and Social

Trust breakdown (7 categories)

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 94 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 123 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Changelog

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.

  • 3 Nov 26 +1
    • Stability: 0.97 → pass security
  • 2 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 27 Oct 26 +1
    • Stability: 0.97 → pass security
  • 26 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 17 Oct 26 +2
    • Stability: 0.87 → pass security
  • 15 Oct 26 −2
    • Stability: pass → 0.83 functional
  • 14 Oct 26 0
    • Stability: 0.97 → pass security
Diagnostics

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 4 Nov 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 SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:726a88930cd90be5d712e486cfee7473e7981dfcd308050e5e6abb840e7bc685948ed2fa644d135fe9aab34299fb5332a3cf06f51d957b0530237dfca

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 94 packages
Packages resolved 94
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~552 tokens

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 →

Tool Tokens
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).

NameTypeReqDescription
attachment_urlstring–URL for quote (alternative to quote_tweet_id)
community_idstring–Post inside a specific community
is_note_tweetboolean–Allow >280 chars (Premium accounts)
media_idsarray–Media IDs from prior /twitter/upload_media_v2
quote_tweet_idstring–Tweet ID to quote
reply_to_tweet_idstring–Tweet ID to reply to (makes this a reply)
schedule_forstring–ISO-8601 future time e.g. 2026-01-20T10:00:00.000Z
tweet_textstringyesThe text content of the tweet

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
tweet_idstringyesThe ID of the tweet to delete

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
cursorstring–Pagination cursor from a previous response's next_cursor
tweet_idstringyesThe tweet ID to get the thread context for

No output schema declared.

No examples provided.

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`).

NameTypeReqDescription
cursorstring–Pagination cursor from a previous response's next_cursor
limitinteger–Max tweets to return from this single request (default 50)
query_typestring–Sort mode (default Latest)
since_timestring–Start time filter (e.g. 2025-06-01 or ISO datetime)
until_timestring–End time filter
user_namestringyesX username, with or without @

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add pedrot95dev-twitterapi -- npx -y @pedrot95dev/twitterapi.mcp
Common questions

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 88 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 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 4 November 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.