Remote MCP · Endpoint
Trending AI Papers — buy per-query in-session (hfpaperwatch) MCP server
No. Trending AI Papers — buy per-query in-session (hfpaperwatch) answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://a2awire.com/mcp/data/hfpaperwatch-trending-ai-research-papers-huggingface-daily-papers-62876a/http
The last check completed an MCP handshake.
- Registry name
- com.a2awire/data-ai-paper-daily-paper-trending-research
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 326 ms
- Tools exposed
- 16 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Trending AI papers daily: ranks, summaries, repos. Register in-session — free testnet funds.
- Website
- https://a2awire.com/data/hfpaperwatch-trending-ai-research-papers-huggingface-daily-papers-62876a
- Repository
- https://github.com/ee324/a2awire
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 326 ms |
| 2 days ago | Handshake completed | 55 ms |
| 4 days ago | Handshake completed | 71 ms |
| 6 days ago | Handshake completed | 61 ms |
| 7 days ago | Handshake completed | 78 ms |
| 8 days ago | Handshake completed | 39 ms |
| 9 days ago | Handshake completed | 338 ms |
| 12 days ago | Handshake completed | 415 ms |
| 14 days ago | Handshake completed | 471 ms |
| 15 days ago | Handshake completed | 132 ms |
| 17 days ago | Handshake completed | 553 ms |
| 18 days ago | Handshake completed | 344 ms |
| 19 days ago | Handshake completed | 446 ms |
| 20 days ago | Handshake completed | 386 ms |
| 20 days ago | Handshake completed | 227 ms |
| 22 days ago | Handshake completed | 253 ms |
| 23 days ago | Handshake completed | 154 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 Trending AI Papers — buy per-query in-session (hfpaperwatch) and makes no claim about it beyond what these checks measured.