io.github.dorukardahan/twitterapi-io-mcp
NPM · TWITTERAPI-IO-MCP · SCANNED AUG 3
Offline access to TwitterAPI.io docs for AI assistants. 67 endpoints, 32 pages, 24 blog posts.
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 →
Supply Chain Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- 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 97 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability85
- 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · twitterapi-io-mcp
claude mcp add dorukardahan-twitterapi-io-mcp -- npx -y twitterapi-io-mcp
codex mcp add dorukardahan-twitterapi-io-mcp -- npx -y twitterapi-io-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dorukardahan-twitterapi-io-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"twitterapi-io-mcp"
],
"enabled": true
}
}
} openclaw mcp add dorukardahan-twitterapi-io-mcp --command npx --arg -y --arg twitterapi-io-mcp
mcp_servers:
dorukardahan-twitterapi-io-mcp:
command: "npx"
args: ["-y", "twitterapi-io-mcp"] {
"mcpServers": {
"dorukardahan-twitterapi-io-mcp": {
"command": "npx",
"args": [
"-y",
"twitterapi-io-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.
- 2 Aug 26 +41
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Licence: MIT functional
- 31 Jul 26 −9
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 28 Jul 26 +29
- Security disclosure: unverified → fail ▼ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: unverified functional
- First check of Schema quality: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- 27 Jul 26 24
First indexed and scored.
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.