io.github.dorukardahan/twitterapi-docs-mcp
NPM · TWITTERAPI-DOCS-MCP · SCANNED SEP 20
Offline access to TwitterAPI.io docs for AI assistants. 52 endpoints, guides, pricing.
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 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency71
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to dorukardahan/twitterapi-docs-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 15 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability88
- 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 796 tokens (~53/item across 15 items; 6 tools + 9 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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.dorukardahan/twitterapi-docs-mcp server?
io.github.dorukardahan/twitterapi-docs-mcp runs locally as an npm package, launched with npx -y twitterapi-docs-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-docs-mcp
claude mcp add dorukardahan-twitterapi-docs-mcp -- npx -y twitterapi-docs-mcp
{
"mcpServers": {
"dorukardahan-twitterapi-docs-mcp": {
"command": "npx",
"args": [
"-y",
"twitterapi-docs-mcp"
]
}
}
} {
"servers": {
"dorukardahan-twitterapi-docs-mcp": {
"command": "npx",
"args": [
"-y",
"twitterapi-docs-mcp"
]
}
}
} codex mcp add dorukardahan-twitterapi-docs-mcp -- npx -y twitterapi-docs-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dorukardahan-twitterapi-docs-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"twitterapi-docs-mcp"
],
"enabled": true
}
}
} openclaw mcp add dorukardahan-twitterapi-docs-mcp --command npx --arg -y --arg twitterapi-docs-mcp
mcp_servers:
dorukardahan-twitterapi-docs-mcp:
command: "npx"
args: ["-y", "twitterapi-docs-mcp"] {
"McpServers": {
"dorukardahan-twitterapi-docs-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"twitterapi-docs-mcp"
]
}
}
} assistant mcp add dorukardahan-twitterapi-docs-mcp -t stdio -c npx -a -y twitterapi-docs-mcp
{
"mcpServers": {
"dorukardahan-twitterapi-docs-mcp": {
"command": "npx",
"args": [
"-y",
"twitterapi-docs-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.
- 18 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.
- 17 Sept 26 −2
- Stability: pass → 0.83 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 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 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.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.77 functional
- 8 Sept 26 0
- Stability: 0.97 → pass security
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/twitterapi-docs-mcp@1.0.3
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-docs-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/dorukardahan/twitterapi-docs-mcp/.github/workflows/publish.yml@refs/tags/v1.0.3 |
| Rekor log index | 743006051 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:8a654fdd47d68031bb48809461954f4165370e8fc27882b4de474bbd02962455d2f0f550d39a40d43c38c069e031e19868706de6a6d49b39f1c2c4687 |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| 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 →
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 |
|---|---|---|---|
| content | array | – | – |
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 |
|---|---|---|---|
| content | array | – | – |
No examples provided.
get_twitterapi_guide ~110
Get TwitterAPI.io guide pages for conceptual topics. USE THIS WHEN: You need information about pricing, rate limits, authentication, or filter rules. AVAILABLE GUIDES: pricing, qps_limits, tweet_filter_rules, changelog, introduction, authentication, readme RETURNS: Full guide content with headers, paragraphs, and code examples.
| Name | Type | Req | Description |
|---|---|---|---|
| guide_name | string | yes | Guide name: pricing, qps_limits, tweet_filter_rules, changelog, introduction, authentication, readme |
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | – | – |
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 |
|---|---|---|---|
| content | array | – | – |
No examples provided.
list_twitterapi_endpoints ~101
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 |
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | – | – |
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 |
|---|---|---|---|
| content | array | – | – |
No examples provided.
What is the io.github.dorukardahan/twitterapi-docs-mcp server?
io.github.dorukardahan/twitterapi-docs-mcp is listed in the public MCP registry as io.github.dorukardahan/twitterapi-docs-mcp. Offline access to TwitterAPI.io docs for AI assistants. 52 endpoints, guides, pricing. This page covers its npm package (twitterapi-docs-mcp).
Is the io.github.dorukardahan/twitterapi-docs-mcp server safe to use?
io.github.dorukardahan/twitterapi-docs-mcp scores 90 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.dorukardahan/twitterapi-docs-mcp server expose?
io.github.dorukardahan/twitterapi-docs-mcp exposes 6 tools: search_twitterapi_docs, get_twitterapi_endpoint, list_twitterapi_endpoints, get_twitterapi_guide, get_twitterapi_pricing, get_twitterapi_auth. Their descriptions and schemas cost roughly 670 tokens of context every time the server is loaded.
Is the io.github.dorukardahan/twitterapi-docs-mcp server still maintained?
io.github.dorukardahan/twitterapi-docs-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.dorukardahan/twitterapi-docs-mcp server under?
io.github.dorukardahan/twitterapi-docs-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.