Remote MCP · Endpoint
AI Agent Board verified MCP hub MCP server
Yes, as of 1 hour ago: the hostname does not resolve.
DownLast checked 1 hour ago
Server URL
https://aiagentboard.org/mcp/server
The last check failed: the hostname does not resolve.
- Registry name
- org.aiagentboard/hub
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 57.9% from 19 checks
- Described by its publisher as
- Search every registry MCP tool with a live probe verdict per server; get a server record; report it.
- Website
- https://aiagentboard.org/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the hostname does not resolve | — |
| 1 day ago | Failed - the hostname does not resolve | — |
| 2 days ago | Failed - the hostname does not resolve | — |
| 3 days ago | Failed - the hostname does not resolve | — |
| 4 days ago | Failed - the hostname does not resolve | — |
| 5 days ago | Failed - the hostname does not resolve | — |
| 6 days ago | Failed - the hostname does not resolve | — |
| 8 days ago | Failed - the hostname does not resolve | — |
| 11 days ago | Handshake completed | 165 ms |
| 13 days ago | Handshake completed | 211 ms |
| 16 days ago | Handshake completed | 195 ms |
| 18 days ago | Handshake completed | 150 ms |
| 20 days ago | Handshake completed | 142 ms |
| 22 days ago | Handshake completed | 279 ms |
| 24 days ago | Handshake completed | 135 ms |
| 26 days ago | Handshake completed | 129 ms |
| 27 days ago | Handshake completed | 152 ms |
| 29 days ago | Handshake completed | 119 ms |
| 29 days ago | Handshake completed | 187 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 21 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 AI Agent Board verified MCP hub and makes no claim about it beyond what these checks measured.