io.github.dorukardahan/twitterapi-io-mcp
NPM · TWITTERAPI-IO-MCP
Offline access to TwitterAPI.io docs for AI assistants. 67 endpoints, 32 pages, 24 blog posts.
Available components
Last scanned (14 hours ago)
Scores higher than 96% of npm servers
Category Code Search and Documentation
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
- 30 of 92 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 dorukardahan/twitterapi-io-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability89
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1028 tokens (~44/item across 23 items; 7 tools + 16 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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.
- 4 Nov 26 +7
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
- Stability: pass → 0.70 functional
- 3 Nov 26 −11
- Known CVEs: pass → unverified ▼ security
- Dependency health: 0.85 → unverified ▼ functional
- Package version: 1.6.2 → 1.7.0 functional
- 30 Oct 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
- 29 Oct 26 −10
- Stability: 0.97 → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.97 → pass security
- Capabilities: pass → unverified ▼ functional
- Dependency health: 0.85 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 1.6.1 → 1.6.2 functional
- 28 Oct 26 −1
- Stability: pass → 0.97 functional
- 26 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 25 Oct 26 0
- Malware scan: unverified → pass ▲ security
- Package version: 1.6.0 → 1.6.1 functional
- 24 Oct 26 0
- Malware scan: unverified → pass ▲ security
- Package version: 1.5.31 → 1.6.0 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 5 Nov 2026 · Analysed npm/twitterapi-io-mcp@1.7.0
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 | dorukardahan/twitterapi-io-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/dorukardahan/twitterapi-io-mcp/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 3658214177 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:8bdafe03089f8a0c64c4489dba989000334f76f1f303d770bac7a0b20fc8b3d7c7ae6b8bccea718d7fa5500c0d9c633fbcfb1d7189901d7f77f0c4616 |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
get_twitterapi_auth ~62
Get TwitterAPI.io authentication guide: API key usage, headers, code examples. USE THIS WHEN: You need to set up authentication or see request examples. RETURNS: API key header format, base URL, cURL/Python/JavaScript examples.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| base_url | string | yes | – |
| dashboard_url | string | – | – |
| examples | object | – | – |
| header | string | yes | – |
| markdown | string | yes | – |
No examples provided.
get_twitterapi_endpoint ~132
Get complete documentation for a specific TwitterAPI.io endpoint. USE THIS WHEN: You know the exact endpoint name (e.g., from search results). RETURNS: Full details including path, parameters, cURL example, and code snippets. Common endpoints: - get_user_info, get_user_followers, get_user_following - tweet_advanced_search, get_tweet_by_id - add_webhook_rule, get_webhook_rules
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint_name | string | yes | Exact endpoint name (use underscores). Examples: 'get_user_info', 'tweet_advanced_search', 'add_webhook_rule' |
| Name | Type | Req | Description |
|---|---|---|---|
| cached | boolean | – | – |
| code_snippets | array | – | – |
| curl_example | string | – | – |
| description | string | – | – |
| doc_url | string | – | – |
| endpoint_name | string | yes | – |
| full_url | string | – | – |
| markdown | string | yes | – |
| method | string | – | – |
| parameters | array | – | – |
| path | string | – | – |
| raw_text | string | – | – |
| title | string | – | – |
No examples provided.
get_twitterapi_guide ~112
Get a TwitterAPI.io page from the offline snapshot by page key. USE THIS WHEN: You need the full content of a specific page (guides, docs, policies, contact, etc.). TIP: Use search_twitterapi_docs if you don't know the page key. RETURNS: Full guide content with headers, paragraphs, and code examples.
| Name | Type | Req | Description |
|---|---|---|---|
| guide_name | string | yes | Page key (from data/pages). Examples: pricing, qps_limits, privacy, contact, introduction, authentication. |
| Name | Type | Req | Description |
|---|---|---|---|
| code_snippets | array | – | – |
| description | string | – | – |
| guide_name | string | yes | – |
| headers | array | – | – |
| list_items | array | – | – |
| markdown | string | yes | – |
| paragraphs | array | – | – |
| raw_text | string | – | – |
| title | string | – | – |
| url | string | – | – |
No examples provided.
get_twitterapi_pricing ~65
Get TwitterAPI.io pricing information: credit system, endpoint costs, QPS limits. USE THIS WHEN: You need to know API costs, credit calculations, or rate limits. RETURNS: Pricing tiers, credit costs per endpoint, QPS limits by balance level.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| costs | object | – | – |
| credits_per_usd | number | – | – |
| markdown | string | yes | – |
| minimum_charge | string | – | – |
| notes | array | – | – |
| qps_limits | object | – | – |
No examples provided.
get_twitterapi_url ~127
Fetch a TwitterAPI.io or docs.twitterapi.io URL. USE THIS WHEN: You have a specific link and want its full content. RETURNS: Parsed content from the offline snapshot. If not found, you can set fetch_live=true (restricted to twitterapi.io/docs.twitterapi.io).
| Name | Type | Req | Description |
|---|---|---|---|
| fetch_live | boolean | – | If true and the URL is missing from the offline snapshot, fetch it live over HTTPS (allowed hosts only). |
| url | string | yes | URL to fetch. Examples: https://twitterapi.io/privacy, /pricing, docs.twitterapi.io/introduction |
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| kind | string | yes | – |
| markdown | string | yes | – |
| name | string | yes | – |
| source | string | yes | – |
| title | string | – | – |
| url | string | yes | – |
No examples provided.
list_twitterapi_endpoints ~103
List all TwitterAPI.io API endpoints organized by category. USE THIS WHEN: You need to browse available endpoints or find endpoints by category. CATEGORIES: user, tweet, community, webhook, stream, action, dm, list, trend RETURNS: Endpoint names with HTTP method and path for each category.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional filter: user, tweet, community, webhook, stream, action, dm, list, trend, other |
| Name | Type | Req | Description |
|---|---|---|---|
| category | string|null | – | – |
| endpoints | array | yes | – |
| markdown | string | yes | – |
| total | integer | yes | Number of endpoints returned (after optional category filter). |
| total_all | integer | – | Total endpoints in the snapshot (before filtering). |
No examples provided.
search_twitterapi_docs ~200
Search TwitterAPI.io documentation: API endpoints, guides (pricing, rate limits, filter rules), and blog posts. USE THIS WHEN: You need to find information across the entire documentation. RETURNS: Ranked results with endpoint paths, descriptions, and relevance scores. Examples: - "advanced search" → finds tweet search endpoints - "rate limit" → finds QPS limits and pricing info - "webhook" → finds webhook setup endpoints - "getUserInfo" → finds user info endpoints (supports camelCase)
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | – | Number of results to return. Use higher values (15-20) for comprehensive research, lower values (3-5) for quick lookups. |
| query | string | yes | Search query (1-500 chars). Use English keywords like: 'search', 'user', 'tweet', 'webhook', 'pricing', 'rate limit'. Supports camelCase and underscore formats. |
| Name | Type | Req | Description |
|---|---|---|---|
| cached | boolean | – | Whether this response was served from cache. |
| counts | object | – | – |
| markdown | string | yes | Human-readable markdown rendering of the results. |
| max_results | integer | yes | Applied max results (1-20). |
| query | string | yes | Normalized (trimmed) search query. |
| results | array | yes | – |
No examples provided.
How do I install the io.github.dorukardahan/twitterapi-io-mcp server?
io.github.dorukardahan/twitterapi-io-mcp runs locally as an npm package, launched with npx -y twitterapi-io-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 · twitterapi-io-mcp
claude mcp add dorukardahan-twitterapi-io-mcp -- npx -y twitterapi-io-mcp
What is the io.github.dorukardahan/twitterapi-io-mcp server?
io.github.dorukardahan/twitterapi-io-mcp is listed in the public MCP registry as io.github.dorukardahan/twitterapi-io-mcp. Offline access to TwitterAPI.io docs for AI assistants. 67 endpoints, 32 pages, 24 blog posts. This page covers its npm package (twitterapi-io-mcp).
Is the io.github.dorukardahan/twitterapi-io-mcp server safe to use?
io.github.dorukardahan/twitterapi-io-mcp scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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.dorukardahan/twitterapi-io-mcp server expose?
io.github.dorukardahan/twitterapi-io-mcp exposes 7 tools: search_twitterapi_docs, get_twitterapi_endpoint, list_twitterapi_endpoints, get_twitterapi_guide, get_twitterapi_url, and 2 more. Their descriptions and schemas cost roughly 801 tokens of context every time the server is loaded.
Is the io.github.dorukardahan/twitterapi-io-mcp server still maintained?
io.github.dorukardahan/twitterapi-io-mcp is still listed as active in the MCP registry. We last reached this channel on 5 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.dorukardahan/twitterapi-io-mcp server under?
io.github.dorukardahan/twitterapi-io-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.