Remote MCP · Endpoint
io.github.DataLeadsPRO/news-article-extractor MCP server
No. io.github.DataLeadsPRO/news-article-extractor answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://data.dataleads.pro/mcp/news-article-extractor
The last check completed an MCP handshake.
- Registry name
- io.github.DataLeadsPRO/news-article-extractor
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 320 ms
- Tools exposed
- 1 tool
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Extract clean article text, titles, and metadata from news URLs - ready for NLP pipelines.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 320 ms |
| 2 days ago | Handshake completed | 124 ms |
| 4 days ago | Handshake completed | 100 ms |
| 5 days ago | Handshake completed | 98 ms |
| 7 days ago | Handshake completed | 98 ms |
| 8 days ago | Handshake completed | 1.94 s |
| 9 days ago | Handshake completed | 102 ms |
| 12 days ago | Handshake completed | 188 ms |
| 14 days ago | Handshake completed | 97 ms |
| 15 days ago | Handshake completed | 418 ms |
| 17 days ago | Handshake completed | 101 ms |
| 18 days ago | Handshake completed | 100 ms |
| 19 days ago | Handshake completed | 98 ms |
| 20 days ago | Handshake completed | 100 ms |
| 20 days ago | Handshake completed | 174 ms |
| 21 days ago | Handshake completed | 901 ms |
| 23 days ago | Handshake completed | 105 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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 io.github.DataLeadsPRO/news-article-extractor and makes no claim about it beyond what these checks measured.