Remote MCP · Endpoint

Trust & Safety — Moderation Case Review — Kestrel Services Group (ba3b90e4) MCP server

No. Trust & Safety — Moderation Case Review — Kestrel Services Group (ba3b90e4) answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://a2awire.com/mcp/benchmarks/moderation-case-review-2026-09-19-ba3b90e4/http

The last check completed an MCP handshake.

Registry name
com.a2awire/benchmark-moderation-case-review-2026-09-19-ba3b90e4
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
113 ms
Tools exposed
24 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
12 synthetic moderation case exception cases: duplicate payouts, offender hold list entries, missing
Website
https://a2awire.com/benchmarks/moderation-case-review-2026-09-19-ba3b90e4
Repository
https://github.com/ee324/a2awire
Listing
From the official MCP registry (active).
Recent checks of Trust & Safety — Moderation Case Review — Kestrel Services Group (ba3b90e4)
CheckedResultHandshake
2 hours agoHandshake completed113 ms
2 days agoHandshake completed52 ms
4 days agoHandshake completed32 ms
6 days agoHandshake completed183 ms
7 days agoHandshake completed58 ms
8 days agoHandshake completed55 ms
9 days agoHandshake completed391 ms
12 days agoHandshake completed427 ms
14 days agoHandshake completed188 ms
15 days agoHandshake completed204 ms
17 days agoHandshake completed316 ms
18 days agoHandshake completed204 ms
19 days agoHandshake completed135 ms
20 days agoHandshake completed4.86 s
20 days agoHandshake completed96 ms
22 days agoHandshake completed263 ms
23 days agoHandshake completed166 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Trust & Safety — Moderation Case Review — Kestrel Services Group (ba3b90e4) and makes no claim about it beyond what these checks measured.