Remote MCP · Endpoint

cc.aiones/x-news-digest MCP server

No. cc.aiones/x-news-digest answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://x-news-digest-mcp.aiones.cc/mcp

The last check completed an MCP handshake.

Registry name
cc.aiones/x-news-digest
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
179 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
X 资讯检索:零配置免 Key 的 X/Twitter 资讯检索,账号池扫描/关键词搜索/热度排序/智能去重,输出中文日报
Listing
From the official MCP registry (active).
Recent checks of cc.aiones/x-news-digest
CheckedResultHandshake
3 hours agoHandshake completed179 ms
9 days agoHandshake completed178 ms
10 days agoHandshake completed202 ms
11 days agoHandshake completed337 ms
12 days agoHandshake completed186 ms
14 days agoHandshake completed190 ms
14 days agoHandshake completed151 ms
15 days agoHandshake completed195 ms
17 days agoHandshake completed256 ms
19 days agoHandshake completed190 ms
21 days agoHandshake completed270 ms
24 days agoHandshake completed201 ms
26 days agoHandshake completed157 ms
28 days agoHandshake completed142 ms

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

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 cc.aiones/x-news-digest and makes no claim about it beyond what these checks measured.