A2A Artifact Handoff
Server Details
Compiles source-agent outputs into validated, receiver-ready handoff packages.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 3 tools
compile_handoff and prepare_artifact both produce transferable packages, which could cause confusion about which to use for a given handoff. inspect_handoff is clearly distinct, and tool descriptions help clarify the intended lifecycle stages, but the boundary between compiling and preparing remains somewhat fuzzy.
compile_handoff and inspect_handoff follow a consistent verb_handoff pattern, but prepare_artifact breaks the pattern by changing the object and verb style. Overall the naming is readable and predictable despite the one deviation.
Three tools is well-scoped for a focused artifact handoff server, covering compilation, inspection, and preparation without unnecessary bloat. Each tool addresses a distinct lifecycle stage.
The set covers the core handoff workflow: compile, inspect, and prepare artifacts for transfer. There is no explicit delivery or acceptance tool, but inspect_handoff returns an acceptance decision, so the lifecycle is reasonably complete with only minor gaps.
Available Tools
3 toolscompile_handoffCInspect
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.
Inputs: source_outputs (required), handoff_context (required), receiver_contract (required), ttl_hours. Returns: object
inspect_handoffAInspect
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.
Inputs: run_id (required). Returns: object
prepare_artifactBInspect
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.
Inputs: content (required), filename, ttl_hours, media_type, +1 more. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Design, build and run teams of AI agents with checked handoffs between them.
Verifiable agent-to-agent task handoff with signed provenance chain. Initiating agent signs the ...
Agent completion verification with defects, corrections, and evidence receipts.
Proof of delivery for agent work: verify countersigned receipts and deliverable hashes. Free.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables agents and orchestrators to deterministically verify sub-agent outputs inside the loop, catching placeholders, unbacked claims, stale state, count mismatches, and missing components before acting on claimed completion. It also supports failure reports and hash-chained verification receipts.MIT
- FlicenseNot gradedqualityDmaintenanceEnables structured role-to-role handoffs and merge gating for multi-agent collaboration. It persists evidence and computes approval gates without invoking LLMs.-
- AlicenseNot gradedqualityCmaintenanceMCP tools that let a coding agent assemble, validate and store a structured handoff document describing a change just finished, then let a receiving agent read that handoff narrowed to its own repository's required actions.MIT
- AlicenseBqualityDmaintenanceVerifiable agent-to-agent task handoff with signed provenance chain.557 PyPIMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.