Remote MCP · Endpoint

ToolNav AI MCP server

No. ToolNav AI answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://toolnav.ai/api/mcp

The last check completed an MCP handshake.

Registry name
ai.toolnav/directory
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
460 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search AI tools, browse categories and read tool details with source links. Free, read-only access.
Listing
From the official MCP registry (active).
Recent checks of ToolNav AI
CheckedResultHandshake
35 minutes agoHandshake completed460 ms
9 days agoHandshake completed553 ms
10 days agoHandshake completed427 ms
11 days agoHandshake completed438 ms
12 days agoHandshake completed536 ms
14 days agoHandshake completed517 ms
14 days agoHandshake completed70 ms
15 days agoHandshake completed88 ms
17 days agoHandshake completed742 ms
19 days agoHandshake completed512 ms
21 days agoHandshake completed633 ms
24 days agoHandshake completed1.50 s
26 days agoHandshake completed781 ms
28 days agoHandshake completed431 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

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 ToolNav AI and makes no claim about it beyond what these checks measured.