Remote MCP · Endpoint
javaBin archive — Norwegian Java community origins MCP server
No. javaBin archive — Norwegian Java community origins answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp-javabin-archieve.fly.dev/mcp
The last check completed an MCP handshake.
- Registry name
- org.totto/javabin-archieve
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 143 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Forensic archive of javaBin & JavaZone origins (1998-2007) as a signed KCP knowledge web.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 143 ms |
| 1 day ago | Handshake completed | 137 ms |
| 2 days ago | Handshake completed | 148 ms |
| 3 days ago | Handshake completed | 188 ms |
| 4 days ago | Handshake completed | 7.78 s |
| 5 days ago | Handshake completed | 137 ms |
| 6 days ago | Handshake completed | 269 ms |
| 8 days ago | Handshake completed | 154 ms |
| 11 days ago | Handshake completed | 259 ms |
| 13 days ago | Handshake completed | 128 ms |
| 15 days ago | Handshake completed | 255 ms |
| 18 days ago | Handshake completed | 7.67 s |
| 20 days ago | Handshake completed | 134 ms |
| 22 days ago | Handshake completed | 8.08 s |
| 24 days ago | Handshake completed | 8.01 s |
| 26 days ago | Handshake completed | 147 ms |
| 27 days ago | Handshake completed | 157 ms |
| 29 days ago | Handshake completed | 128 ms |
| 30 days ago | Handshake completed | 293 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 29 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 javaBin archive — Norwegian Java community origins and makes no claim about it beyond what these checks measured.