mcp-registry/com.jojapi/x-twitter · v1.0.0
As of 2026-10-19 23:12 UTC, the Jojapi X Twitter MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 8 minutes.
X (twitter): x, xapi, Twitter, twitter api, twitters ,tweets, tw, twttr, FollowerIds, friendsIds.
Claude Code
claude mcp add --transport http jojapi-x-twitter-mcp-server https://mcp.jojapi.com/x
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"jojapi-x-twitter-mcp-server": {
"type": "http",
"url": "https://mcp.jojapi.com/x"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
107 of 107 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 →
107 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
560 parameter(s) across 106 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
13 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Loading this server's tool list costs an agent ~16,380 tokens before any work — more than 90% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. 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 →
44 tools share an identical description with another tool on this server.
Make each description say how the tool differs from its siblings, or the model will pick between them at random. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 106 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.jojapi%2Fx-twitter/fixes
{
"name": "get_base_apitools_CommunitiesFetchOneQuery",
"description": "get CommunitiesFetchOneQuery info Group: communities. Billing per call: 1 Credits.",
"inputSchema": {
"type": "object",
"properties": {
"apiKey": {
"type": "string",
"title": "apiKey"
},
"cursor": {
"type": "string",
"title": "cursor"
},
"proxyUrl": {
"type": "string",
"title": "proxyUrl"
},
"resFormat": {
"type": "string",
"title": "resFormat"
},
"communityId": {
"type": "string",
"title": "communityId"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "get CommunitiesFetchOneQuery info"
}{
"name": "get_base_apitools_CommunitiesMemberV2",
"description": "get Communities Member list. Group: communities. Billing per call: 1 Credits.",
"inputSchema": {
"type": "object",
"properties": {
"apiKey": {
"type": "string",
"title": "apiKey"
},
"cursor": {
"type": "string",
"title": "cursor"
},
"proxyUrl": {
"type": "string",
"title": "proxyUrl"
},
"resFormat": {
"type": "string",
"title": "resFormat"
},
"communityId": {
"type": "string",
"title": "communityId"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "get Communities Member list."
}{
"name": "get_base_apitools_CommunitiesSearchV2",
"description": "get Communities Member list. Group: communities. Billing per call: 1 Credits.",
"inputSchema": {
"type": "object",
"properties": {
"word": {
"type": "string",
"title": "word"
},
"apiKey": {
"type": "string",
"title": "apiKey"
},
"cursor": {
"type": "string",
"title": "cursor"
},
"proxyUrl": {
"type": "string",
"title": "proxyUrl"
},
"resFormat": {
"type": "string",
"title": "resFormat"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "get Communities Member list."
}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/com.jojapi/x-twitter"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.jojapi/x-twitter"}) over MCP.
get_base_apitools_search ~610 tokensget_base_apitools_mentionsTimeline ~308 tokenspost_base_apitools_sendDMSMedia ~296 tokensget_base_apitools_sendDMSMedia ~295 tokensget_base_apitools_favoritesList ~275 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%2Fcom.jojapi%2Fx-twitter?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.jojapi%2Fx-twitter?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.jojapi%2Fx-twitter.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.jojapi%2Fx-twitter.svg :target: https://glimind.com/server/mcp-registry%2Fcom.jojapi%2Fx-twitter?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:3ea33181822d81b4…, first seen 2026-10-17, included at leaf 2656 of 29,371. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable retrieval servers · most reliable communication servers · most reliable data servers · most reliable other 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-19 23:12 UTC, the Jojapi X Twitter MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 8 minutes.
Jojapi X Twitter MCP server advertises 107 tools, including get_base_apitools_CommunitiesFetchOneQuery, get_base_apitools_CommunitiesMemberV2, get_base_apitools_CommunitiesSearchV2, get_base_apitools_CommunitiesTimelineV2, get_base_apitools_CommunitiesTweetsTimelineV2.
Point your MCP client at this streamable-http endpoint: https://mcp.jojapi.com/x
Glimind scanned all 107 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.