A
licenseNot graded
qualityD
maintenanceEnables AI agents to scrape Twitter/X profiles, tweets, and search results without an API key, returning structured JSON with bios, stats, and engagement metrics via x402 micropayments.
1
MIT
x-twitter
by io.veezee
Server Details
X (formerly Twitter) posts, profiles, and search for AI agents. Free key, self-minted, no signup.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Unhealthy
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- veezeehq/veezee-mcp
- GitHub Stars
- 0
- Server Listing
- Veezee
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
5 tool updates
- Changed
get_usage2 fields changed- added
Output schema / properties / common / properties / free_tierAdded value: +{ + "anyOf": [ + { + "additionalProperties": false, + "properties": { + "credits_per_ip_day": { + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "remaining_today": { + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "resets": { + "description": "UTC midnight when the day budget resets. ISO 8601.", + "type": "string" + }, + "used_today": { + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + } + }, + "required": [ + "credits_per_ip_day", + "used_today", + "remaining_today", + "resets" + ], + "type": "object" + }, + { + "type": "null" + } + ], + "description": "Present on trial keys: the shared per-IP day budget this key actually spends (balance_remaining stays 0 on the free tier; other callers on the same IP draw from the same pool). Null on paid plans." +} - changed
Output schema / properties / common / requiredPrevious value: -[ - "plan", - "platforms", - "balance_remaining", - "realtime_ops_used", - "realtime_ops_limit", - "concurrent_limit", - "recent_receipts", - "claim_url", - "upgrade_url", - "manage_url" -]New value: +[ + "plan", + "platforms", + "balance_remaining", + "free_tier", + "realtime_ops_used", + "realtime_ops_limit", + "concurrent_limit", + "recent_receipts", + "claim_url", + "upgrade_url", + "manage_url" +]
- Changed
x_get_profile9 fields changed- added
Input schema / properties / by / descriptionAdded value: +"Force how identifier is interpreted; auto-detected when omitted." - added
Input schema / properties / by / enumAdded value: +[ + "screen_name", + "id" +] - added
Input schema / properties / freshness / defaultAdded value: +"recent" - added
Input schema / properties / freshness / descriptionAdded value: +"recent (default) serves cached data from the last few hours when available; realtime forces a live fetch for +2 credits (refunded if we fall back to cached data). Trial keys are cached-only and reject realtime with TRIAL_CAP_EXCEEDED; paying upgrades this same key to unlock it." - added
Input schema / properties / freshness / enumAdded value: +[ + "recent", + "realtime" +] - added
Input schema / properties / max_credits / descriptionAdded value: +"Spend ceiling for this one call. The call is rejected (nothing charged) if its quote exceeds this. Only the quote is ever reserved, never this ceiling." - added
Input schema / properties / max_credits / maximumAdded value: +9007199254740991 - added
Input schema / properties / max_credits / minimumAdded value: +0 - changed
Input schema / properties / max_credits / typePrevious value: -"number"New value: +"integer"
- Changed
x_get_tweet7 fields changed- added
Input schema / properties / freshness / defaultAdded value: +"recent" - added
Input schema / properties / freshness / descriptionAdded value: +"recent (default) serves cached data from the last few hours when available; realtime forces a live fetch for +2 credits (refunded if we fall back to cached data). Trial keys are cached-only and reject realtime with TRIAL_CAP_EXCEEDED; paying upgrades this same key to unlock it." - added
Input schema / properties / freshness / enumAdded value: +[ + "recent", + "realtime" +] - added
Input schema / properties / max_credits / descriptionAdded value: +"Spend ceiling for this one call. The call is rejected (nothing charged) if its quote exceeds this. Only the quote is ever reserved, never this ceiling." - added
Input schema / properties / max_credits / maximumAdded value: +9007199254740991 - added
Input schema / properties / max_credits / minimumAdded value: +0 - changed
Input schema / properties / max_credits / typePrevious value: -"number"New value: +"integer"
- Changed
x_get_tweets13 fields changed- added
Input schema / properties / cursor / descriptionAdded value: +"Cursor from a previous page for older tweets." - added
Input schema / properties / freshness / defaultAdded value: +"recent" - added
Input schema / properties / freshness / descriptionAdded value: +"recent (default) serves cached data from the last few hours when available; realtime forces a live fetch for +2 credits (refunded if we fall back to cached data). Trial keys are cached-only and reject realtime with TRIAL_CAP_EXCEEDED; paying upgrades this same key to unlock it." - added
Input schema / properties / freshness / enumAdded value: +[ + "recent", + "realtime" +] - added
Input schema / properties / include_retweets / defaultAdded value: +true - added
Input schema / properties / include_retweets / descriptionAdded value: +"Set false to drop retweets from the page." - added
Input schema / properties / max_credits / descriptionAdded value: +"Spend ceiling for this one call. The call is rejected (nothing charged) if its quote exceeds this. Only the quote is ever reserved, never this ceiling." - added
Input schema / properties / max_credits / maximumAdded value: +9007199254740991 - added
Input schema / properties / max_credits / minimumAdded value: +0 - changed
Input schema / properties / max_credits / typePrevious value: -"number"New value: +"integer" - added
Input schema / properties / mode / defaultAdded value: +"posts" - added
Input schema / properties / mode / descriptionAdded value: +"Which timeline view to read." - added
Input schema / properties / mode / enumAdded value: +[ + "posts", + "posts_and_replies", + "highlights" +]
- Changed
x_search11 fields changed- added
Input schema / properties / cursor / descriptionAdded value: +"Cursor from a previous page. Not valid with type 'people'." - added
Input schema / properties / freshness / defaultAdded value: +"recent" - added
Input schema / properties / freshness / descriptionAdded value: +"recent (default) serves cached data from the last few hours when available; realtime forces a live fetch for +2 credits (refunded if we fall back to cached data). Trial keys are cached-only and reject realtime with TRIAL_CAP_EXCEEDED; paying upgrades this same key to unlock it." - added
Input schema / properties / freshness / enumAdded value: +[ + "recent", + "realtime" +] - added
Input schema / properties / max_credits / descriptionAdded value: +"Spend ceiling for this one call. The call is rejected (nothing charged) if its quote exceeds this. Only the quote is ever reserved, never this ceiling." - added
Input schema / properties / max_credits / maximumAdded value: +9007199254740991 - added
Input schema / properties / max_credits / minimumAdded value: +0 - changed
Input schema / properties / max_credits / typePrevious value: -"number"New value: +"integer" - added
Input schema / properties / type / defaultAdded value: +"recent" - added
Input schema / properties / type / descriptionAdded value: +"recent = chronological deep sweep; popular = top engagement; people = account search (single page)." - added
Input schema / properties / type / enumAdded value: +[ + "recent", + "popular", + "people" +]
7 tool updates
- Changed
get_usage2 fields changed- added
Output schema / properties / usage / properties / free_tier_hintAdded value: +{ + "description": "Present on free-tier trial-key calls: what budget the call drew from and that paying upgrades this same key.", + "type": "string" +} - removed
Output schema / properties / usage / properties / keyless_hintRemoved value: -{ - "description": "Present on keyless calls: what budget the call drew from and how to get a key with its own balance.", - "type": "string" -}
- Added
mint_key - Changed
x_get_profile2 fields changed- added
Output schema / properties / usage / properties / free_tier_hintAdded value: +{ + "description": "Present on free-tier trial-key calls: what budget the call drew from and that paying upgrades this same key.", + "type": "string" +} - removed
Output schema / properties / usage / properties / keyless_hintRemoved value: -{ - "description": "Present on keyless calls: what budget the call drew from and how to get a key with its own balance.", - "type": "string" -}
- Changed
x_get_tweet2 fields changed- added
Output schema / properties / usage / properties / free_tier_hintAdded value: +{ + "description": "Present on free-tier trial-key calls: what budget the call drew from and that paying upgrades this same key.", + "type": "string" +} - removed
Output schema / properties / usage / properties / keyless_hintRemoved value: -{ - "description": "Present on keyless calls: what budget the call drew from and how to get a key with its own balance.", - "type": "string" -}
- Changed
x_get_tweets2 fields changed- added
Output schema / properties / usage / properties / free_tier_hintAdded value: +{ + "description": "Present on free-tier trial-key calls: what budget the call drew from and that paying upgrades this same key.", + "type": "string" +} - removed
Output schema / properties / usage / properties / keyless_hintRemoved value: -{ - "description": "Present on keyless calls: what budget the call drew from and how to get a key with its own balance.", - "type": "string" -}
- Changed
x_resolve_url2 fields changed- added
Output schema / properties / usage / properties / free_tier_hintAdded value: +{ + "description": "Present on free-tier trial-key calls: what budget the call drew from and that paying upgrades this same key.", + "type": "string" +} - removed
Output schema / properties / usage / properties / keyless_hintRemoved value: -{ - "description": "Present on keyless calls: what budget the call drew from and how to get a key with its own balance.", - "type": "string" -}
- Changed
x_search2 fields changed- added
Output schema / properties / usage / properties / free_tier_hintAdded value: +{ + "description": "Present on free-tier trial-key calls: what budget the call drew from and that paying upgrades this same key.", + "type": "string" +} - removed
Output schema / properties / usage / properties / keyless_hintRemoved value: -{ - "description": "Present on keyless calls: what budget the call drew from and how to get a key with its own balance.", - "type": "string" -}
6 tool updates
- First observed
get_usage - First observed
x_get_profile - First observed
x_get_tweet - First observed
x_get_tweets - First observed
x_resolve_url - First observed
x_search
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Real-time LinkedIn, X (Twitter) and Reddit data for AI agents. Free key, self-minted, no signup.
X/Twitter reads, search, monitors and posting. Pay-per-call in USDC — no signup, no API keys.
Twitter (X) API alternative for AI agents: tweet search, profiles, followers. $0.0002 per result.
Reddit posts, comments, subreddits, and search for AI agents. Free key, self-minted, no signup.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to fully automate X/Twitter interactions including searching, posting, engaging, and managing multiple accounts without paid API keys.MIT
- AlicenseBqualityAmaintenanceEnables AI agents to search, read user profiles, timelines, media, follow threads, track trends, and manage accounts on X/Twitter via GraphQL, without browser automation or paid API keys.10010MIT
- AlicenseNot gradedqualityDmaintenanceProvides AI agents and coding assistants with Twitter data access including tweets, user profiles, followers, and search functionality.MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.6/5.0
Disambiguation5/5
All seven tools have distinct purposes: get_usage for account limits, mint_key for API key creation, x_get_profile for user profile, x_get_tweet for a single tweet, x_get_tweets for timeline, x_resolve_url for URL resolution, and x_search for keyword search. Descriptions clearly differentiate overlapping areas like profile vs search/people and single tweet vs timeline.
Naming Consistency3/5
Most tools use snake_case and a verb_noun pattern, but there is inconsistency in the prefix: get_usage and mint_key lack the 'x_' prefix present on other tools (e.g., x_get_profile, x_search). Verbs also vary (get, mint, resolve, search), though all are imperative and generally clear.
Tool Count5/5
With 7 tools, the server is well-scoped for a Twitter data retrieval server. It includes essential admin tools (get_usage, mint_key) and core data tools (profile, tweet, timeline, search, URL resolution), neither too few nor too many for its purpose.
Completeness4/5
The tool surface covers key read operations for Twitter: profile data, tweets, timelines, search, and URL resolution. Minor gaps exist, such as missing tools for retrieving followers, likes, or trends, but the set is sufficient for many common tasks and avoids critical dead-ends.