Remote MCP · Endpoint
mcpnav directory MCP server
No. mcpnav directory answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://mcp.mcpnav.dev/mcp
The last check completed an MCP handshake.
- Registry name
- dev.mcpnav/directory
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 182 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 16 checks
- Described by its publisher as
- Search a directory of MCP servers and get connect configs. Data is CC0/MIT-licensed.
- Website
- https://mcpnav.dev/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 182 ms |
| 2 days ago | Handshake completed | 183 ms |
| 4 days ago | Handshake completed | 271 ms |
| 5 days ago | Handshake completed | 179 ms |
| 7 days ago | Handshake completed | 219 ms |
| 8 days ago | Handshake completed | 403 ms |
| 9 days ago | Handshake completed | 135 ms |
| 12 days ago | Handshake completed | 141 ms |
| 14 days ago | Handshake completed | 183 ms |
| 15 days ago | Handshake completed | 291 ms |
| 17 days ago | Handshake completed | 140 ms |
| 18 days ago | Handshake completed | 138 ms |
| 19 days ago | Handshake completed | 151 ms |
| 20 days ago | Handshake completed | 177 ms |
| 20 days ago | Handshake completed | 156 ms |
| 21 days ago | Handshake completed | 270 ms |
The last 16 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.
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 mcpnav directory and makes no claim about it beyond what these checks measured.