Remote MCP · Endpoint
Faceabot Latest news MCP server
No. Faceabot Latest news answered an MCP handshake 21 minutes ago.
UpLast checked 21 minutes ago
Server URL
https://faceabot.com/tools-mcp/news
The last check completed an MCP handshake.
- Registry name
- com.faceabot/news
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 860 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 100% from 12 checks
- Described by its publisher as
- Today's headlines and news search from 17 public sources in 7 languages. Free, no key.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 21 minutes ago | Handshake completed | 860 ms |
| 9 days ago | Handshake completed | 1.09 s |
| 9 days ago | Handshake completed | 338 ms |
| 11 days ago | Handshake completed | 851 ms |
| 12 days ago | Handshake completed | 225 ms |
| 13 days ago | Handshake completed | 30 ms |
| 14 days ago | Handshake completed | 44 ms |
| 15 days ago | Handshake completed | 64 ms |
| 16 days ago | Handshake completed | 212 ms |
| 19 days ago | Handshake completed | 153 ms |
| 21 days ago | Handshake completed | 262 ms |
| 24 days ago | Handshake completed | 1.29 s |
The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 12.
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 Faceabot Latest news and makes no claim about it beyond what these checks measured.