Skip to content
MCPSTAMP
MCP server report

Twitter API MCP server

com.jojapi/twitter-x-aio

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 86 of 100 (grade B), higher than 58.3% of the 33,003 registry servers that responded over HTTPS that day. Ready for Gemini and MCP Registry. Not ready for Claude and ChatGPT.

Measured facts

Score
86B
Sign-in
No sign-in
Tools listed
23
Protocol version
2025-06-18
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Not ready Blocked by readOnlyHint or destructiveHint on every tool.
ChatGPT app directory Not ready Blocked by readOnlyHint or destructiveHint on every tool and Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT).
Gemini Connected Apps Ready No blocking check failed.
Official MCP Registry Ready No blocking check failed.

MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.

Fixes

2 checks to fix

  1. Fails

    readOnlyHint or destructiveHint on every tool

    tool_annotations

    Blocks Claude and ChatGPT.

    Measured 23/23 tools set neither readOnlyHint nor destructiveHint: get_search_searchTerm, get_trends_locationId, get_user_userId, get_user_by_username_username, get_user

    Set annotations.readOnlyHint: true on read-only tools and destructiveHint: true on tools that modify or delete data (Claude needs one of them on every tool; ChatGPT needs all three hints, see tool_open_world).

  2. Fails

    Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT)

    tool_open_world

    Blocks ChatGPT.

    Measured 23/23 tools miss an explicit hint: get_search_searchTerm, get_trends_locationId, get_user_userId, get_user_by_username_username, get_user_userId_tweets and 18 m

    Set readOnlyHint, destructiveHint and openWorldHint to explicit true/false on every tool (OpenAI app review requires all three).

15 checks passed, 10 did not run

Passed. Served over HTTPS, initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, JSON-RPC error for unknown method, GET answers SSE or 405, initialize latency, serverInfo name and version, Server instructions, tools capability declared, tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable, Human-readable title on every tool, Tool descriptions.

Not run. Sign-in method the store supports (OAuth or none), 401 carries WWW-Authenticate resource_metadata, Protected resource metadata (RFC 9728), Resource metadata "resource" equals the server URL, Authorization server metadata (RFC 8414 / OIDC), First metadata URL Gemini tries answers 200 with the required fields, issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT), PKCE S256 advertised, Client registration (DCR or Client ID Metadata Documents), refresh_token grant advertised. The server asks for no sign-in, so the OAuth checks do not apply.

Run a fresh check

This page is the 2 November 2026 snapshot. If you maintain this server and have shipped fixes since then, re-check it. The live check and the badge show the current result, and the next snapshot will pick up the change.

Re-check now

Badge

README badge

The badge shows the latest score for this URL and links to this report.

McpStamp score for Twitter API

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Fmcp.jojapi.com%2Ftwitter-x-aio)](https://www.mcpstamp.com/r/com-jojapi-twitter-x-aio/)

HTML

<a href="https://www.mcpstamp.com/r/com-jojapi-twitter-x-aio/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Fmcp.jojapi.com%2Ftwitter-x-aio" alt="McpStamp score" height="20"></a>
Registry entry

About this server

Twitter: Access real-time Twitter/X data as soon as it's posted! With the Twitter/X AIO API, you.
Registry name
com.jojapi/twitter-x-aio
Remote URL
https://mcp.jojapi.com/twitter-x-aio
Version
1.0.0
Website
jojapi.com/hub/api/twitter-x-aio
Checked
2 November 2026, engine 1.2.0, no credentials

The description above is the server's own text from the official MCP Registry. If a result looks wrong, run a fresh check and email support@zovo.one with the report link.

More grade B servers

All grade B servers · All server reports · State of MCP readiness, November 2026