Remote MCP · Endpoint

Xtracticle MCP server

No. Xtracticle answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://xtracticle.com/mcp

The last check completed an MCP handshake.

Registry name
com.xtracticle/xtracticle
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
97 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read public X (Twitter) posts, threads and X Articles as clean Markdown. Read-only, no auth.
Listing
From the official MCP registry (active).
Recent checks of Xtracticle
CheckedResultHandshake
43 minutes agoHandshake completed97 ms
3 days agoHandshake completed75 ms
13 days agoHandshake completed77 ms
13 days agoHandshake completed166 ms
15 days agoHandshake completed89 ms
15 days agoHandshake completed60 ms
17 days agoHandshake completed88 ms
18 days agoHandshake completed69 ms
18 days agoHandshake completed80 ms
20 days agoHandshake completed89 ms
22 days agoHandshake completed60 ms
25 days agoHandshake completed166 ms
27 days agoHandshake completed69 ms
29 days agoHandshake completed91 ms

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

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 Xtracticle and makes no claim about it beyond what these checks measured.