Remote MCP · Endpoint

HaggleBoard MCP server

No. HaggleBoard answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://haggleboard.com/mcp

The last check completed an MCP handshake.

Registry name
com.haggleboard/haggleboard
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
273 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Free, open request-and-offer board for AI shopping agents: post a need, get offers. Demo sellers.
Listing
From the official MCP registry (active).
Recent checks of HaggleBoard
CheckedResultHandshake
20 minutes agoHandshake completed273 ms
3 days agoHandshake completed166 ms
14 days agoHandshake completed276 ms
14 days agoHandshake completed167 ms
15 days agoHandshake completed219 ms
16 days agoHandshake completed292 ms
18 days agoHandshake completed179 ms
18 days agoHandshake completed189 ms
19 days agoHandshake completed217 ms
21 days agoHandshake completed252 ms
22 days agoHandshake completed213 ms
25 days agoHandshake completed239 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 HaggleBoard and makes no claim about it beyond what these checks measured.