Remote MCP · Endpoint
1lev1 MCP server
No. 1lev1 answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.1lev1.com/api/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.Avi-ADAM/1lev1
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 468 ms
- Tools exposed
- 46 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Track partnership work, log mission hours, and see what needs your approval on 1lev1.com.
- Website
- https://1lev1.com/
- Repository
- https://github.com/Avi-ADAM/1lev1-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 468 ms |
| 2 days ago | Handshake completed | 292 ms |
| 4 days ago | Handshake completed | 325 ms |
| 5 days ago | Handshake completed | 298 ms |
| 7 days ago | Handshake completed | 322 ms |
| 8 days ago | Handshake completed | 313 ms |
| 9 days ago | Handshake completed | 291 ms |
| 12 days ago | Handshake completed | 315 ms |
| 13 days ago | Handshake completed | 302 ms |
| 15 days ago | Handshake completed | 352 ms |
| 16 days ago | Handshake completed | 298 ms |
| 18 days ago | Credentials required | — |
| 19 days ago | Credentials required | — |
| 20 days ago | Credentials required | — |
| 20 days ago | Credentials required | — |
| 21 days ago | Credentials required | — |
| 22 days ago | Credentials required | — |
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 1lev1 and makes no claim about it beyond what these checks measured.