A2areplayreceipt Mcp

com.clauxel.a2areplayreceiptPublished by a2areplayreceipt.clauxel.comOfficial publisherv1.0.0Updated Oct 24, 2026

Remote MCP for A2A failure replay MCP, structured receipts, audit logs, and reviewer-ready evidence.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Hosted remote MCP for replaying A2A agent failures, classifying errors, suggesting retry plans, and issuing structured replay receipts and audit evidence.

What you can do
Replay A2A failures and classify agent errors to identify what went wrong in an agent-to-agent run. Suggest retry plans based on the failure and error classification. Issue replay receipts and export failure logs as structured, reviewer-ready evidence for audits. Access is through a streamable HTTP endpoint with structured tool-call output.
When to use it
Useful for developer platform teams, release owners, AI engineering leads, and delivery reviewers who need to reproduce agent-to-agent failures and keep documented evidence of what happened and how it was retried.
Requirements
A remote MCP endpoint; no local package or runtime is needed. An Authorization header carrying a Bearer token obtained from the product website is required for production calls. Network access to the hosted endpoint.
Before you install
Access requires a Bearer token in the Authorization header, so keep it secret. The README links to pricing and checkout pages, so paid plans may apply. Replay, receipt issuance, and log export produce records that may contain failure details; review what is sent to the hosted service before use.

Installation

In SourceWeft

  1. Open A2areplayreceipt Mcp in the dashboard and add it to a workspace.
  2. 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/com.clauxel.a2areplayreceipt%2Fa2areplayreceipt-mcp/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "a2areplayreceipt": {
      "type": "http",
      "url": "https://a2areplayreceipt.clauxel.com/mcp"
    }
  }
}

README

A2A Replay Receipt

A2A Replay Receipt is a hosted remote MCP for A2A failure replay MCP.

This repository is a public documentation project for A2A Replay Receipt. Its structure follows the public documentation pattern used by MiroFish: a short front door, a clear reading order, practical guides, reference pages, and a public-safe boundary.

Start Here

Remote MCP

Reading Order

  1. Quickstart
  2. Evaluation guide
  3. Checkout and pricing
  4. Workflow notes
  5. Security model
  6. Public link reference

Audience

developer platform teams, release owners, AI engineering leads, and delivery reviewers.

Capabilities

  • Streamable HTTP MCP endpoint
  • Bearer-token access for production calls
  • Structured tool-call output
  • Receipt-oriented evidence export
  • Public server card and registry metadata
  • MCP tool: replay_a2a_failure
  • MCP tool: classify_agent_error
  • MCP tool: suggest_retry_plan
  • MCP tool: issue_replay_receipt
  • MCP tool: export_failure_log

Public-Safe Boundary

This repository contains documentation only. It does not contain production source code, credentials, payment configuration, Cloudflare configuration, customer records, private analytics, or local machine paths.

Source: README.md at commit f5c978f

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts