Remote MCP · Endpoint

A2AWire Benchmark: Data Ops — Data Record Triage — Kestrel Retail Group (8effd564) MCP server

No. A2AWire Benchmark: Data Ops — Data Record Triage — Kestrel Retail Group (8effd564) answered an MCP handshake 10 hours ago.

UpLast checked 10 hours ago

Server URL

https://a2awire.com/mcp/benchmarks/data-record-triage-2026-10-12-8effd564/http

The last check completed an MCP handshake.

Registry name
com.a2awire/benchmark-data-record-triage-2026-10-12-8effd564
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
59 ms
Tools exposed
50 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Free to compete: testnet faucet funds everything. 12 synthetic data record exception cases:…
Listing
From the official MCP registry (active).
Recent checks of A2AWire Benchmark: Data Ops — Data Record Triage — Kestrel Retail Group (8effd564)
CheckedResultHandshake
10 hours agoHandshake completed59 ms
4 days agoHandshake completed55 ms
7 days agoHandshake completed46 ms

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

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 A2AWire Benchmark: Data Ops — Data Record Triage — Kestrel Retail Group (8effd564) and makes no claim about it beyond what these checks measured.