Remote MCP · Endpoint
com.nobleblocks/nobleblocks-mcp MCP server
No. com.nobleblocks/nobleblocks-mcp answered an MCP handshake 2 hours ago.
UpLast checked 2 hours 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
- 663 ms
- Tools exposed
- 11 tools
- Uptime, last 30 days
- 100% from 18 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 |
|---|---|---|
| 2 hours ago | Handshake completed | 663 ms |
| 1 day ago | Handshake completed | 642 ms |
| 2 days ago | Handshake completed | 859 ms |
| 3 days ago | Handshake completed | 1.00 s |
| 4 days ago | Handshake completed | 674 ms |
| 5 days ago | Handshake completed | 666 ms |
| 7 days ago | Handshake completed | 696 ms |
| 9 days ago | Handshake completed | 649 ms |
| 12 days ago | Handshake completed | 659 ms |
| 14 days ago | Handshake completed | 842 ms |
| 16 days ago | Handshake completed | 690 ms |
| 18 days ago | Handshake completed | 688 ms |
| 20 days ago | Handshake completed | 695 ms |
| 22 days ago | Handshake completed | 692 ms |
| 25 days ago | Handshake completed | 699 ms |
| 26 days ago | Handshake completed | 706 ms |
| 28 days ago | Handshake completed | 695 ms |
| 29 days ago | Handshake completed | 1.34 s |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 18 responding of 29.
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.