Remote MCP · Endpoint

AgingResearch.News MCP server

No. AgingResearch.News answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://agingresearch.news/api/mcp

The last check completed an MCP handshake.

Registry name
news.agingresearch/agingresearch-news
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
48 ms
Tools exposed
23 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Search every new aging paper, judged on evidence, plus trials, grants, drug pipelines and news.
Listing
From the official MCP registry (active).
Recent checks of AgingResearch.News
CheckedResultHandshake
1 hour agoHandshake completed48 ms
1 day agoHandshake completed206 ms
2 days agoHandshake completed75 ms
3 days agoHandshake completed30 ms
4 days agoHandshake completed38 ms
5 days agoHandshake completed29 ms
6 days agoHandshake completed36 ms
9 days agoHandshake completed26 ms
11 days agoHandshake completed24 ms
14 days agoHandshake completed29 ms
16 days agoHandshake completed123 ms
18 days agoHandshake completed78 ms
20 days agoHandshake completed84 ms
22 days agoHandshake completed91 ms
24 days agoHandshake completed79 ms

The last 15 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 AgingResearch.News and makes no claim about it beyond what these checks measured.