mcp-registry/io.veezee/x-twitter · v2.0.0
Verdict. Veezee X Twitter MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 345 ms median handshake and 0 outages in 90 days. Its agent-readiness grade is A (97/100) across 7 tools, costing an agent about 2,344 tokens to load. Checked every few minutes; no tool is ever called.
Data as of .
| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 345 ms | 59% of MCP servers |
| p95 handshake latency | 608 ms | — |
| Checks in 30 days | 213 | — |
| Outages, 90 days | 0 | — |
| Median recovery | — | — |
| Agent-readiness score | 97/100 (A) | 91% of MCP servers |
| Tools | 7 | — |
| Tool-list size for an agent | ~2,344 tokens | 50% of MCP servers |
| Days observed | 27 | — |
As of 2026-10-26 22:27 UTC, the Veezee X Twitter MCP server is up (it requires sign-in) with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks.
X (formerly Twitter) posts, profiles, and search for AI agents. Free key, self-minted, no signup.
Claude Code
claude mcp add --transport http veezee-x-twitter-mcp-server https://mcp.veezee.io/x
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"veezee-x-twitter-mcp-server": {
"type": "http",
"url": "https://mcp.veezee.io/x"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
1 of 7 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 →
Requires authentication (Bearer); tool definitions could not be read anonymously.
If discovery should be public, allow initialize + tools/list without credentials and gate only tools/call. Directories and routers can then list your tools.
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.veezee/x-twitter"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.veezee/x-twitter"}) over MCP.
x_get_tweets ~480 tokensx_search ~477 tokensx_get_profile ~427 tokensx_get_tweet ~386 tokensx_resolve_url ~220 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.veezee%2Fx-twitter?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.veezee%2Fx-twitter?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.veezee%2Fx-twitter.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.veezee%2Fx-twitter.svg :target: https://glimind.com/server/mcp-registry%2Fio.veezee%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:16f3ad881f3d01d9…, first seen 2026-10-17, included at leaf 9225 of 75,889. Version history · verify what your client received.
Compare: most reliable other servers · most reliable social 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-26 22:27 UTC, the Veezee X Twitter MCP server is up (it requires sign-in) with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks.
Veezee X Twitter MCP server advertises 7 tools, including get_usage, mint_key, x_get_profile, x_get_tweet, x_get_tweets.
Point your MCP client at this streamable-http endpoint: https://mcp.veezee.io/x
Glimind scanned all 7 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.