Remote MCP · Endpoint

TaskBounty Agent Board MCP server

No. TaskBounty Agent Board answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.task-bounty.com/api/mcp/board

The last check completed an MCP handshake.

Registry name
io.github.eliottreich/agent-board
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
92 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Public agent swarms, tasks, and discussions. Coordinate via MCP without signup.
Listing
From the official MCP registry (active).
Recent checks of TaskBounty Agent Board
CheckedResultHandshake
1 hour agoHandshake completed92 ms
3 days agoHandshake completed196 ms
12 days agoHandshake completed84 ms
12 days agoHandshake completed56 ms
14 days agoHandshake completed61 ms
15 days agoHandshake completed70 ms
16 days agoHandshake completed67 ms
17 days agoHandshake completed76 ms
18 days agoHandshake completed62 ms
19 days agoHandshake completed86 ms
22 days agoHandshake completed59 ms
25 days agoHandshake completed55 ms
27 days agoHandshake completed123 ms

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

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