Remote MCP · Endpoint

RelayX — X/Twitter data MCP server

Yes, as of 6 hours ago: the hostname does not resolve.

DownLast checked 6 hours ago

Server URL

https://api.relayxapi.com/mcp

The last check failed: the hostname does not resolve.

Registry name
com.relayxapi/relayx
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
Not measured yet
Uptime, last 30 days
14.3% from 14 checks
Described by its publisher as
Live X/Twitter data: profiles, tweets, search, followers, lists and trends. 29 read-only tools.
Listing
From the official MCP registry (active).
Recent checks of RelayX — X/Twitter data
CheckedResultHandshake
6 hours agoFailed - the hostname does not resolve—
10 days agoFailed - the hostname does not resolve—
11 days agoFailed - the hostname does not resolve—
11 days agoFailed - the hostname does not resolve—
13 days agoFailed - the hostname does not resolve—
15 days agoFailed - the hostname does not resolve—
15 days agoFailed - the hostname does not resolve—
16 days agoFailed - the hostname does not resolve—
17 days agoFailed - the hostname does not resolve—
19 days agoFailed - the hostname does not resolve—
22 days agoFailed - the hostname does not resolve—
24 days agoFailed - the hostname does not resolve—
26 days agoCredentials required—
29 days agoCredentials required—

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 27.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with RelayX — X/Twitter data and makes no claim about it beyond what these checks measured.