Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.jojapi/twitter

REMOTE · MCP.JOJAPI.COM

X (formerly Twitter): X (formerly Twitter) public and private data API for search, posts (Tweets).

Available components

0 this week 74 Trust /100

Last scanned (6 hours ago)

Scores higher than 61% of remote servers

Reachable. Last reached 5 Nov 2026.

Category News and Social

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 2572 tokens (~80/item across 32 items; 32 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 81% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 32 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 33 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

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.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 18 Sept 26 0
    • Stability: 0.97 → pass security
  • 10 Sept 26 0
    • Tool “get_AutoComplete” rewrote its description, which is the text the model reads security
    • Tool “get_Search” rewrote its description, which is the text the model reads security
    • Tool “get_ShortUrl” rewrote its description, which is the text the model reads security
    • Tool “get_email_search_by_username” rewrote its description, which is the text the model reads security
    • Tool “get_v1_1_Followers” rewrote its description, which is the text the model reads security
    • Tool “get_v1_1_FollowersIds” rewrote its description, which is the text the model reads security
    • Tool “get_v1_1_Following” rewrote its description, which is the text the model reads security
    • Tool “get_v1_1_FollowingIds” rewrote its description, which is the text the model reads security
    • Tool “get_v1_1_Hashflags” rewrote its description, which is the text the model reads security
    • Tool “get_v1_1_Locations” rewrote its description, which is the text the model reads security
    • Tool “get_v1_1_TranslateProfile” rewrote its description, which is the text the model reads security
    • Tool “get_v1_1_TranslateTweet” rewrote its description, which is the text the model reads security
    • Tool “get_v1_1_Trends” rewrote its description, which is the text the model reads security
    • Tool “get_v1_1_Users” rewrote its description, which is the text the model reads security
    • Tool “get_v2_Favoriters” rewrote its description, which is the text the model reads security
    • Tool “get_v2_Followers” rewrote its description, which is the text the model reads security
    • Tool “get_v2_Following” rewrote its description, which is the text the model reads security
    • Tool “get_v2_Likes” rewrote its description, which is the text the model reads security
    • Tool “get_v2_ListTimeline” rewrote its description, which is the text the model reads security
    • Tool “get_v2_Retweeters” rewrote its description, which is the text the model reads security
    • Tool “get_v2_Subscriptions” rewrote its description, which is the text the model reads security
    • Tool “get_v2_Tweet” rewrote its description, which is the text the model reads security
    • Tool “get_v2_TweetDetail” rewrote its description, which is the text the model reads security
    • Tool “get_v2_UserAffiliates” rewrote its description, which is the text the model reads security
    • Tool “get_v2_UserByRestId” rewrote its description, which is the text the model reads security
    • Tool “get_v2_UserByScreenName” rewrote its description, which is the text the model reads security
    • Tool “get_v2_UserHighlights” rewrote its description, which is the text the model reads security
    • Tool “get_v2_UserMedia” rewrote its description, which is the text the model reads security
    • Tool “get_v2_UserTweets” rewrote its description, which is the text the model reads security
    • Tool “get_v2_UserTweetsAndReplies” rewrote its description, which is the text the model reads security
    • Tool “get_v2_UsersByRestIds” rewrote its description, which is the text the model reads security
    • Tool “get_v2_VerifiedFollowers” rewrote its description, which is the text the model reads security
    • Schema quality: 61 → 80 ▼ functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 20 Aug 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 19 Aug 26 0

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Probed https://mcp.jojapi.com/twitter

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.jojapi.com CN=WE1,O=Google Trust Services,C=US 17 Oct 2026 15 Jan 2027 ECDSA 256 ECDSA-SHA256 4fdef8b174aa7f510e6f8de60526c223
SANs: mcp.jojapi.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.jojapi.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
jojapi.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.jojapi.com/twitter Verified 200
http (plaintext) http://mcp.jojapi.com/twitter HTTPS enforced 301 https://mcp.jojapi.com/twitter
MCP tools · 32 exposed · ~2,482 tokens

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 →

Tool Tokens
get_AutoComplete ~50

Auto Complete Group: Explore. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
qstring––

No output schema declared.

No examples provided.

get_email_search_by_username ~55

Email Search (by username) Group: User. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
usernamestring––

No output schema declared.

No examples provided.

get_Search ~111

Search Group: Explore. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
countinteger–Number of Tweet results
cursorstring–Cursor for other results
qstring–You can use advanced search queries. E.g. dogecoin (from:elonmusk) Check out for more information: https://twitter.com/search-advanced
typestring–Default: Top.

No output schema declared.

No examples provided.

get_ShortUrl ~57

Twitter URL shortening service Group: Misc. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
urlstring–The URL you want shortened

No output schema declared.

No examples provided.

get_v1_1_Followers ~105

User Followers / Light Group: User. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
countstring–Number of results. Max: 200
cursorstring––
idstring–Exactly one of User ID or Username must be provided.
usernamestring–Exactly one of User ID or Username must be provided.

No output schema declared.

No examples provided.

get_v1_1_FollowersIds ~106

User Followers IDs Group: User. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
countstring–Number of results. Max: 5000
cursorstring––
idstring–Exactly one of User ID or Username must be provided.
usernamestring–Exactly one of User ID or Username must be provided.

No output schema declared.

No examples provided.

get_v1_1_Following ~105

User Following / Light Group: User. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
countstring–Number of results. Max: 200
cursorstring––
idstring–Exactly one of User ID or Username must be provided.
usernamestring–Exactly one of User ID or Username must be provided.

No output schema declared.

No examples provided.

get_v1_1_FollowingIds ~106

User Following IDs Group: User. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
countstring–Number of results. Max: 5000
cursorstring––
idstring–Exactly one of User ID or Username must be provided.
usernamestring–Exactly one of User ID or Username must be provided.

No output schema declared.

No examples provided.

get_v1_1_Hashflags ~47

Hashflags Group: Misc. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_v1_1_Locations ~57

Locations Group: Explore. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
qstring–Leave blank to get countries

No output schema declared.

No examples provided.

get_v1_1_TranslateProfile ~63

Translate Profile Group: User. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
idstring––
languagestring–Language code

No output schema declared.

No examples provided.

get_v1_1_TranslateTweet ~63

Translate Tweet Group: Tweet. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
idstring––
languagestring–Language code

No output schema declared.

No examples provided.

get_v1_1_Trends ~78

Trends Group: Explore. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
countstring–Number of results
location_idstring–You must use the Locations endpoint to find IDs. Currently only countries are supported.

No output schema declared.

No examples provided.

get_v1_1_Users ~96

Get Users Group: User. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
idsstring–A comma separated list of User IDs. Up to 100 are allowed in a single request.
usernamesstring–A comma separated list of Usernames. Up to 100 are allowed in a single request.

No output schema declared.

No examples provided.

get_v2_Favoriters ~74

Tweet Favoriters Group: Tweet. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
countstring–Number of results
cursorstring–Cursor for other results
idstring––

No output schema declared.

No examples provided.

get_v2_Followers ~87

User Followers Group: User. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
countstring–Number of results
cursorstring–Cursor for other results
idstring–Use the User By Screen Name endpoint to find the ID from a username.

No output schema declared.

No examples provided.

get_v2_Following ~87

User Following Group: User. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
countstring–Number of results
cursorstring–Cursor for other results
idstring–Use the User By Screen Name endpoint to find the ID from a username.

No output schema declared.

No examples provided.

get_v2_Likes ~86

User Likes Group: User. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
countstring–Number of results
cursorstring–Cursor for other results
idstring–Use the User By Screen Name endpoint to find the ID from a username.

No output schema declared.

No examples provided.

get_v2_ListTimeline ~72

List Timeline Group: List. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
countstring–Number of results
cursorstring–Cursor for other results
idstring––

No output schema declared.

No examples provided.

get_v2_Retweeters ~76

Tweet Retweeters Group: Tweet. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
countstring–Number of results
cursorstring–Cursor for other results
idstring––

No output schema declared.

No examples provided.

get_v2_Subscriptions ~87

User Subscriptions Group: User. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
countstring–Number of results
cursorstring–Cursor for other results
idstring–Use the User By Screen Name endpoint to find the ID from a username.

No output schema declared.

No examples provided.

get_v2_Tweet ~53

Tweet Detail / Alternative Group: Tweet. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
idstring––

No output schema declared.

No examples provided.

get_v2_TweetDetail ~65

Tweet Detail & Conversation Group: Tweet. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
cursorstring–Cursor for other results
idstring––

No output schema declared.

No examples provided.

get_v2_UserAffiliates ~89

User Affiliates Group: User. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
countstring–Number of results
cursorstring–Cursor for other results
idstring–Use the User By Screen Name endpoint to find the ID from a username.

No output schema declared.

No examples provided.

get_v2_UserByRestId ~55

User By Rest ID Group: User. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
idstring––

No output schema declared.

No examples provided.

get_v2_UserByScreenName ~55

User By Screen Name Group: User. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
usernamestring––

No output schema declared.

No examples provided.

get_v2_UserHighlights ~86

User Highlights Group: User. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
countstring–Number of results
cursorstring–Cursor for other results
idstring–Use the User By Screen Name endpoint to find the ID from a username.

No output schema declared.

No examples provided.

get_v2_UserMedia ~86

User Media Group: User. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
countstring–Number of results
cursorstring–Cursor for other results
idstring–Use the User By Screen Name endpoint to find the ID from a username.

No output schema declared.

No examples provided.

get_v2_UsersByRestIds ~61

Users By Rest IDs Group: User. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
idsstring–you can separate with commas

No output schema declared.

No examples provided.

get_v2_UserTweets ~86

User Tweets Group: User. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
countstring–Number of results
cursorstring–Cursor for other results
idstring–Use the User By Screen Name endpoint to find the ID from a username.

No output schema declared.

No examples provided.

get_v2_UserTweetsAndReplies ~90

User Tweets & Replies Group: User. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
countstring–Number of results
cursorstring–Cursor for other results
idstring–Use the User By Screen Name endpoint to find the ID from a username.

No output schema declared.

No examples provided.

get_v2_VerifiedFollowers ~88

User Verified Followers Group: User. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

NameTypeReqDescription
countstring–Number of results
cursorstring–Cursor for other results
idstring–Use the User By Screen Name endpoint to find the ID from a username.

No output schema declared.

No examples provided.

Install

How do I install the com.jojapi/twitter MCP server?

com.jojapi/twitter is a hosted endpoint at https://mcp.jojapi.com/twitter, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.jojapi.com

# add to Claude Code
claude mcp add --transport http com-jojapi-twitter 'https://mcp.jojapi.com/twitter'
Common questions

What is the com.jojapi/twitter MCP server?

com.jojapi/twitter is an MCP server listed in the public MCP registry as com.jojapi/twitter. X (formerly Twitter): X (formerly Twitter) public and private data API for search, posts (Tweets). This page covers its hosted endpoint (https://mcp.jojapi.com/twitter).

Is the com.jojapi/twitter MCP server safe to use?

com.jojapi/twitter scores 74 out of 100 on VerifyMCP. 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 com.jojapi/twitter MCP server expose?

com.jojapi/twitter exposes 32 tools: get_AutoComplete, get_Search, get_v1_1_Trends, get_v1_1_Locations, get_v2_TweetDetail, and 27 more. Their descriptions and schemas cost roughly 2,482 tokens of context every time the server is loaded.

Does the com.jojapi/twitter MCP server require authentication?

No. We connected to com.jojapi/twitter without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.jojapi/twitter MCP server still maintained?

com.jojapi/twitter is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.