mcpbeat Sign in

A2A Artifact Handoff MCP Server

by imagiever-ar Your server? Claim it
not responding

A2A Artifact Handoff is listed as active in the registry but did not answer our last check. It exposes 3 tools.

Compiles source-agent outputs into validated, receiver-ready handoff packages.

Uptime history 51 days of history · worst day 0%
51 days agonow
1.1%
Uptime 24h
1 of 88 checks
3
Tools
read from the server
42 ms
Response time
average over 24h
open, no key
Access
streamable-http

A2A Artifact Handoff does not always answer

Over the last week it answered 44.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add a2a-artifact-handoff --transport http https://a2a-artifact-handoff.onrender.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "a2a-artifact-handoff": {
      "url": "https://a2a-artifact-handoff.onrender.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.a2a-artifact-handoff]
url = "https://a2a-artifact-handoff.onrender.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "a2a-artifact-handoff": {
      "url": "https://a2a-artifact-handoff.onrender.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "a2a-artifact-handoff": {
      "url": "https://a2a-artifact-handoff.onrender.com/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

compile
compile_handoff
Compile source-agent outputs into a receiver-ready handoff package. The input schema declares the exact source-output, receiver-contract, and handoff-context fields. The tool selects and validates required deliverables and returns either a portable package or actionable unmet requirements.
inspect
inspect_handoff
Inspect a handoff package and return an acceptance decision. The tool recalculates deliverable hashes, checks expiry and contract satisfaction, and returns the receiving agent's next action.
prepare
prepare_artifact
Prepare content for transfer to another agent or a human reviewer. `target_modes` accepts either a JSON list or an actual list of MIME types. The result includes expiring artifact URLs, SHA-256 hashes, a manifest, and a downloadable ZIP package.

Endpoints

URLTransportStateLatencyChecked
https://a2a-artifact-handoff.onrender.com/mcp streamable-http answering 190 ms 7 min ago

Alternatives to A2A Artifact Handoff

same job, measured the same way
JSON Contracts
by json-contracts

JSON contract registry and validator for structured LLM and agent outputs.

51 installs/wk local only
Doc Extract MCP
by koraynar

Document tooling for AI agents: PDF/text reading, chunking, schema-validated JSON output.

local only
D
SOURCE/80 Discovery
by workers-source-80-source-80

Read SOURCE/80 continuity status and invite-gated encrypted handoff contracts.

5 tools answering
VouchSpec Agent Skill Evidence
by mordiaky

Read-only discovery for exact-commit Agent Skill validation, x402 payment, and signed receipts.

answering
Handoff — publish agent results as shareable pages
by workers-notdown-app-handoff

Give your agent one stable URL to publish a result or keep a page updated every run. One call.

7 tools answering
Coalent
by nisarg-pujara-vectorlink

Fresh, attributed facts from your sources — cached, and invalidated the moment a source changes.

137 installs/wk local only
SCORM Packager (HTML → SCORM 2004)
by giacomomaria81

Turn HTML or mobile-learning exports into SCORM 2004/1.2 packages, and validate any SCORM zip.

60 installs/wk local only
Oxcode
by snowmead

PageRank-curated code intelligence for coding agents over an indexed source repository.

48 installs/wk local only

A2A Artifact Handoff — questions

Answers built from our own checks of this server.

What can A2A Artifact Handoff do?
It exposes 3 tools, read directly from the server on our last check. Among them: compile_handoff, inspect_handoff, prepare_artifact. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is A2A Artifact Handoff working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 1 of 88 checks got a reply (1.1%), average response time 42 ms. The bar chart above shows every period we have measured.
The registry lists A2A Artifact Handoff as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect A2A Artifact Handoff?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does A2A Artifact Handoff need an API key?
No. A2A Artifact Handoff completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is A2A Artifact Handoff?
It answers our handshake in 42 ms on average, which is faster than 94% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.