A remote MCP endpoint that compiles source-agent outputs into validated, receiver-ready handoff packages.
What you can do
The server is described as compiling outputs produced by a source agent into handoff packages that are validated and ready for a receiving agent. No tool list is published, so the exact operations are not documented. It is reached as a remote streamable HTTP endpoint rather than a local process.
When to use it
Consider it when an assistant needs to pass work between agents and wants the handoff assembled and validated rather than sent as raw output. Because the tool list is not published, verify the available operations before relying on it.
Requirements
A remote streamable HTTP connection to the provider's endpoint. No packages, environment variables, headers, or authentication are declared.
Before you install
No authentication is declared, so anything sent to the endpoint may be handled without an access check; avoid sending secrets or private data. The tool list is not published, so what the server does with submitted content cannot be confirmed from the listing.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.imagiever-ar%2Fa2a-artifact-handoff/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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.
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 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.
Parametersrun_idrequired
Version history
1
v0.6.0LatestSep 16, 2026
Score
83%
83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.