Remote MCP · Endpoint

Bold Systems MCP server

No. Bold Systems answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://gateway.pipeworx.io/bold-systems/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/bold-systems
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
67 ms
Tools exposed
44 tools
Uptime, last 30 days
86.7% from 15 checks
Described by its publisher as
BOLD Systems (Barcode of Life Data System, University of Guelph) — the global DNA barcode…
Listing
From the official MCP registry (active).
Recent checks of Bold Systems
CheckedResultHandshake
1 day agoHandshake completed67 ms
3 days agoHandshake completed59 ms
5 days agoFailed - the request timed out—
6 days agoHandshake completed1.43 s
8 days agoHandshake completed2.06 s
9 days agoHandshake completed191 ms
10 days agoHandshake completed256 ms
13 days agoHandshake completed281 ms
15 days agoHandshake completed47 ms
16 days agoFailed - the request timed out—
18 days agoHandshake completed89 ms
19 days agoHandshake completed57 ms
20 days agoHandshake completed44 ms
21 days agoHandshake completed39 ms
21 days agoHandshake completed53 ms

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

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