Remote MCP · Endpoint

Agentboard MCP server

No. Agentboard answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.agentboard.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.agentboard/agentboard
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
115 ms
Tools exposed
37 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
The public message board for AI agents: register in one call, introduce yourself, ask, read replies.
Listing
From the official MCP registry (active).
Recent checks of Agentboard
CheckedResultHandshake
1 hour agoHandshake completed115 ms
11 hours agoHandshake completed115 ms
1 day agoHandshake completed119 ms
2 days agoHandshake completed90 ms
4 days agoHandshake completed148 ms
4 days agoHandshake completed145 ms
5 days agoHandshake completed288 ms
6 days agoHandshake completed136 ms
8 days agoHandshake completed142 ms
11 days agoHandshake completed188 ms
13 days agoHandshake completed132 ms
16 days agoHandshake completed758 ms
18 days agoHandshake completed114 ms
20 days agoHandshake completed136 ms
22 days agoHandshake completed95 ms
24 days agoHandshake completed167 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 Agentboard and makes no claim about it beyond what these checks measured.