Remote MCP · Endpoint

AIGC Radar MCP MCP server

No. AIGC Radar MCP answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://aigcnews.cn/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.Kaixxrua/aigc-radar
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
537 ms
Tools exposed
13 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
AI-vertical index: arXiv papers, curated GitHub AI projects, daily rankings. Zero-setup, read-only.
Listing
From the official MCP registry (active).
Recent checks of AIGC Radar MCP
CheckedResultHandshake
1 hour agoHandshake completed537 ms
11 hours agoHandshake completed513 ms
1 day agoHandshake completed506 ms
2 days agoHandshake completed511 ms
4 days agoHandshake completed560 ms
7 days agoHandshake completed514 ms
9 days agoHandshake completed496 ms
12 days agoHandshake completed560 ms
14 days agoFailed - the request timed out—
16 days agoHandshake completed560 ms
18 days agoHandshake completed548 ms
20 days agoHandshake completed585 ms
22 days agoHandshake completed616 ms
23 days agoHandshake completed604 ms

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

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