Remote MCP · Endpoint

A2A Artifact Handoff MCP server

No. A2A Artifact Handoff answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://a2a-artifact-handoff.onrender.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.imagiever-ar/a2a-artifact-handoff
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
102 ms
Tools exposed
3 tools
Uptime, last 30 days
52.9% from 17 checks
Described by its publisher as
Compiles source-agent outputs into validated, receiver-ready handoff packages.
Listing
From the official MCP registry (active).
Recent checks of A2A Artifact Handoff
CheckedResultHandshake
2 hours agoHandshake completed102 ms
2 days agoHandshake completed115 ms
4 days agoHandshake completed51 ms
5 days agoHandshake completed56 ms
7 days agoHandshake completed88 ms
8 days agoHandshake completed55 ms
9 days agoHandshake completed48 ms
12 days agoHandshake completed47 ms
13 days agoHandshake completed75 ms
15 days agoFailed - the server returned an HTTP error—
17 days agoFailed - the server returned an HTTP error—
18 days agoFailed - the server returned an HTTP error—
19 days agoFailed - the server returned an HTTP error—
20 days agoFailed - the server returned an HTTP error—
20 days agoFailed - the server returned an HTTP error—
21 days agoFailed - the server returned an HTTP error—
23 days agoFailed - the server returned an HTTP error—

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 9 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.

Listing data comes from the official MCP registry. Glide is not affiliated with A2A Artifact Handoff and makes no claim about it beyond what these checks measured.