Remote MCP · Endpoint

Compliance Batch Alignment MCP server

No. Compliance Batch Alignment answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://bonissystems.com/api/knox/agents/compliance-batch/mcp

The last check completed an MCP handshake.

Registry name
com.bonissystems/compliance-batch
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
205 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Check whether a NAICS code aligns with a vertical: a routing-for-review signal, not a determination.
Listing
From the official MCP registry (active).
Recent checks of Compliance Batch Alignment
CheckedResultHandshake
2 hours agoHandshake completed205 ms
1 day agoHandshake completed131 ms
3 days agoHandshake completed297 ms
3 days agoHandshake completed135 ms
4 days agoHandshake completed124 ms
5 days agoHandshake completed135 ms
7 days agoHandshake completed351 ms
10 days agoHandshake completed120 ms
12 days agoHandshake completed144 ms
15 days agoHandshake completed158 ms
17 days agoHandshake completed482 ms
19 days agoHandshake completed158 ms
21 days agoHandshake completed170 ms
23 days agoHandshake completed220 ms
25 days agoHandshake completed319 ms
26 days agoHandshake completed150 ms
28 days agoHandshake completed233 ms
29 days agoHandshake completed142 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 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 Compliance Batch Alignment and makes no claim about it beyond what these checks measured.