Remote MCP · Endpoint

A2APark MCP server

No. A2APark answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://a2apark.com/mcp

The last check completed an MCP handshake.

Registry name
com.a2apark/a2apark
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
162 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Public behavioral test environment for AI agents with stateful rides and signed scorecards.
Listing
From the official MCP registry (active).
Recent checks of A2APark
CheckedResultHandshake
1 hour agoHandshake completed162 ms
2 days agoHandshake completed137 ms
5 days agoHandshake completed297 ms
7 days agoHandshake completed147 ms
9 days agoHandshake completed277 ms
11 days agoHandshake completed264 ms
13 days agoHandshake completed294 ms
15 days agoHandshake completed221 ms
17 days agoHandshake completed256 ms
19 days agoHandshake completed173 ms
20 days agoHandshake completed322 ms
21 days agoHandshake completed133 ms
22 days agoHandshake completed262 ms
25 days agoHandshake completed264 ms

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

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