Remote MCP · Endpoint
Knowra MCP server
No. Knowra answered an MCP handshake 7 hours ago.
UpLast checked 7 hours ago
Server URL
https://mcp.knowra.app/mcp
The last check completed an MCP handshake.
- Registry name
- app.knowra/knowra
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 372 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 12 checks
- Described by its publisher as
- Search arXiv papers and read Scout reports with methods, evidence and verification points.
- Website
- https://knowra.app/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 7 hours ago | Handshake completed | 372 ms |
| 4 days ago | Handshake completed | 934 ms |
| 14 days ago | Handshake completed | 366 ms |
| 15 days ago | Handshake completed | 379 ms |
| 15 days ago | Handshake completed | 354 ms |
| 17 days ago | Handshake completed | 263 ms |
| 18 days ago | Handshake completed | 268 ms |
| 19 days ago | Handshake completed | 277 ms |
| 20 days ago | Handshake completed | 267 ms |
| 21 days ago | Handshake completed | 345 ms |
| 23 days ago | Handshake completed | 281 ms |
| 26 days ago | Handshake completed | 267 ms |
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 Knowra and makes no claim about it beyond what these checks measured.