Remote MCP · Endpoint
YourAITools MCP Hub MCP server
No. YourAITools MCP Hub answered an MCP handshake 4 hours ago.
UpLast checked 4 hours ago
Server URL
https://api.youraitools.co/mcp/hub
The last check completed an MCP handshake.
- Registry name
- co.youraitools/hub
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 78 ms
- Tools exposed
- 45 tools
- Uptime, last 30 days
- 100% from 12 checks
- Described by its publisher as
- All 22 YourAITools agent APIs in one MCP server. Most tools free; pay with credits or x402.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 4 hours ago | Handshake completed | 78 ms |
| 3 days ago | Handshake completed | 155 ms |
| 12 days ago | Handshake completed | 107 ms |
| 13 days ago | Handshake completed | 113 ms |
| 14 days ago | Handshake completed | 92 ms |
| 15 days ago | Handshake completed | 233 ms |
| 16 days ago | Handshake completed | 130 ms |
| 17 days ago | Handshake completed | 74 ms |
| 18 days ago | Handshake completed | 90 ms |
| 20 days ago | Handshake completed | 119 ms |
| 22 days ago | Handshake completed | 200 ms |
| 25 days ago | Handshake completed | 94 ms |
The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 12.
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 YourAITools MCP Hub and makes no claim about it beyond what these checks measured.