Remote MCP · Endpoint
Real-Time News MCP server
No. Real-Time News answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://news.memoryapi.org/mcp
The last check completed an MCP handshake.
- Registry name
- org.memoryapi/news
- Transport
- Streamable HTTP
- Protocol negotiated
- 2024-11-05
- Handshake latency
- 113 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 27.8% from 18 checks
- Described by its publisher as
- Real-time news and trending topics from major sources
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 113 ms |
| 2 days ago | Handshake completed | 95 ms |
| 4 days ago | Handshake completed | 338 ms |
| 6 days ago | Handshake completed | 92 ms |
| 7 days ago | Handshake completed | 341 ms |
| 9 days ago | Failed - the server returned an HTTP error | — |
| 10 days ago | Failed - the server returned an HTTP error | — |
| 11 days ago | Failed - the server returned an HTTP error | — |
| 14 days ago | Failed - the server returned an HTTP error | — |
| 15 days ago | Failed - the server returned an HTTP error | — |
| 17 days ago | Failed - the server returned an HTTP error | — |
| 18 days ago | Failed - the server returned an HTTP error | — |
| 19 days ago | Failed - the server returned an HTTP error | — |
| 20 days ago | Failed - the server returned an HTTP error | — |
| 21 days ago | Failed - the server returned an HTTP error | — |
| 22 days ago | Failed - the server returned an HTTP error | — |
| 23 days ago | Failed - the server returned an HTTP error | — |
| 24 days ago | Failed - the server returned an HTTP error | — |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 5 responding of 18.
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 Real-Time News and makes no claim about it beyond what these checks measured.