Remote MCP · Endpoint

Twitter / X data for agents MCP server

No. Twitter / X data for agents answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://twitter.fetcher.sh/mcp

The last check completed an MCP handshake.

Registry name
sh.fetcher.twitter/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
85 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
15 Twitter / X endpoints. Pay per call in USDC via x402.
Website
https://twitter.fetcher.sh/
Listing
From the official MCP registry (active).
Recent checks of Twitter / X data for agents
CheckedResultHandshake
1 hour agoHandshake completed85 ms
2 days agoHandshake completed139 ms
4 days agoHandshake completed173 ms
5 days agoHandshake completed107 ms
7 days agoHandshake completed101 ms
8 days agoHandshake completed80 ms
9 days agoHandshake completed182 ms
12 days agoHandshake completed104 ms
13 days agoHandshake completed113 ms
15 days agoHandshake completed91 ms
16 days agoHandshake completed57 ms
18 days agoHandshake completed81 ms
19 days agoHandshake completed82 ms
20 days agoHandshake completed98 ms
21 days agoHandshake completed82 ms
21 days agoHandshake completed96 ms
23 days agoHandshake completed77 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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