Remote MCP · Endpoint
com.nobleblocks/nobleblocks-mcp MCP server
No. com.nobleblocks/nobleblocks-mcp answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.nobleblocks.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.nobleblocks/nobleblocks-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 695 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 35.3% from 17 checks
- Described by its publisher as
- Search 340M+ academic papers — citation graphs, semantic similarity, and AI literature reviews.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 695 ms |
| 2 days ago | Handshake completed | 692 ms |
| 4 days ago | Handshake completed | 699 ms |
| 5 days ago | Handshake completed | 706 ms |
| 7 days ago | Handshake completed | 695 ms |
| 8 days ago | Handshake completed | 1.34 s |
| 9 days ago | Failed - the request timed out | — |
| 12 days ago | Failed - the request timed out | — |
| 13 days ago | Failed - the request timed out | — |
| 15 days ago | Failed - the request timed out | — |
| 16 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 request timed out | — |
| 22 days ago | Failed - the request timed out | — |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 6 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 com.nobleblocks/nobleblocks-mcp and makes no claim about it beyond what these checks measured.