Remote MCP · Endpoint

cc.aiones/x-news-monitor MCP server

No. cc.aiones/x-news-monitor answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

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

The last check completed an MCP handshake.

Registry name
cc.aiones/x-news-monitor
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
243 ms
Tools exposed
6 tools
Uptime, last 30 days
2 checks from 2 checks
Described by its publisher as
X 资讯监控:盯账号自动巡检,新帖去重中文日报,每 30 分钟自动巡查,支持飞书/Slack/Discord 推送
Listing
From the official MCP registry (active).
Recent checks of cc.aiones/x-news-monitor
CheckedResultHandshake
1 day agoHandshake completed243 ms
3 days agoHandshake completed150 ms

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

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