mcp-registry/io.github.br0ski777/twitter-scraper · v1.0.0
Also listed as glama/br0ski777/twitter-scraper
As of 2026-10-23 19:43 UTC, the Br0ski777 Twitter Scraper MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 0% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 6 minutes.
Scrape Twitter/X profiles, tweets, search. No API key. Structured JSON. x402 pay-per-call.
Point your MCP client at this streamable-http endpoint: https://twitter-scraper.api.klymax402.com/mcp
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →
3 of 3 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.br0ski777%2Ftwitter-scraper/fixes
{
"name": "twitter_get_user_tweets",
"description": "Use this when you need to see what a specific Twitter/X user has been posting recently. Returns their latest tweets with full text, engagement metrics, and timestamps.\n\n1. username: the @handle queried\n2. tweets: array of tweet objects with id, text, createdAt, likes, retweets, replies, views, isRetweet, isReply\n3. tweetCount: number of tweets returned\n\nExample output: { \"username\": \"VitalikButerin\", \"tweetCount\": 10, \"tweets\": [{ \"id\": \"...\", \"text\": \"Excited about the new EIP proposal...\", \"li",
"inputSchema": {
"type": "object",
"required": [
"username"
],
"properties": {
"count": {
"type": "number",
"description": "Number of tweets to return (1-20, default 10)"
},
"username": {
"type": "string",
"description": "Twitter/X username without @ (e.g. 'VitalikButerin')"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "twitter_search_tweets",
"description": "Use this when you need to find tweets about a topic, brand, event, or keyword. Returns up to 20 recent tweets matching the query with full text, engagement metrics, author info, and timestamps.\n\n1. query: the search term used\n2. results: array of tweet objects\n3. Each tweet contains: id, text, author (username + displayName), createdAt, likes, retweets, replies, views, url\n4. resultCount: number of tweets found\n\nExample output: { \"query\": \"x402 protocol\", \"resultCount\": 15, \"results\": [{ \"id\": \"",
"inputSchema": {
"type": "object",
"required": [
"query"
],
"properties": {
"count": {
"type": "number",
"description": "Number of tweets to return (1-20, default 10)"
},
"query": {
"type": "string",
"description": "Search query -- supports keywords, phrases, hashtags (#), mentions (@), and operators (from:user, since:2026-01-01)"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.br0ski777/twitter-scraper"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.br0ski777/twitter-scraper"}) over MCP.
twitter_search_tweets ~245 tokenstwitter_get_user_tweets ~231 tokenstwitter_scrape_profile ~214 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.br0ski777%2Ftwitter-scraper?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.br0ski777%2Ftwitter-scraper?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.br0ski777%2Ftwitter-scraper.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.br0ski777%2Ftwitter-scraper.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.br0ski777%2Ftwitter-scraper?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:26c62f3fbe9c15ec…, first seen 2026-10-17, included at leaf 12240 of 55,119. Version history · verify what your client received.
Compare: most reliable communication servers · most reliable web servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-23 19:43 UTC, the Br0ski777 Twitter Scraper MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 0% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 6 minutes.
Br0ski777 Twitter Scraper MCP server advertises 3 tools, including twitter_get_user_tweets, twitter_scrape_profile, twitter_search_tweets.
Point your MCP client at this streamable-http endpoint: https://twitter-scraper.api.klymax402.com/mcp
Glimind scanned all 3 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.