Trace · registry probe · T1 reproducible run

Registry probe of ag-ui's discovery endpoints

ag-ui · 2026-10-11 · AgentDossier refresh · harness probe-1.0

Scenario. Fetch and validate the ARD manifest, A2A agent card and MCP server card at the publisher's well-known paths

Observed. A2A invalid (unsigned; 1 validation error); MCP invalid

Entry	GET on the publisher's well-known discovery paths
Actions	served Agent2Agent (A2A) document; served Model Context Protocol (MCP) document
Egress	no
Human approval	—
Secrets touched	no
Bundle	`bundles/tr_st_af03e1411fa93db4_084b2560` · `sha256:401bd28df4c6dd9f9b172a8d65a5ff9431d6a430117bb24ec75baada24d7efee` · download (JSON)
Chain	`sha256:0760111317e6b90f2dc7acd8966f805f1b8cbcc616a0820e154c89e504ac9503` prev sha256:9eb0cf1f4edfcdc17295abb5e48e020fa552d6a85c1039dd8b7d6f169b672342

Transcript

# Probe transcript — ag-ui

Agent `res_af03e1411fa93db4` · publisher domain `ag-ui.com` · 2026-10-11 · harness probe-1.0

## Agent2Agent (A2A)

- requested `https://docs.ag-ui.com/.well-known/agent-card.json`
- result: **invalid**
- declared version: 0.3 (card 1.0.0)
- signed: no
- skills advertised: tawkitai
- validation error: missing 'description'

## Model Context Protocol (MCP)

- requested `https://docs.ag-ui.com/.well-known/mcp.json`
- result: **invalid**

---
Observation only: the registry fetched public well-known paths and validated the documents against the protocol specifications. No credentials, no message exchange beyond discovery, nothing written.

Produced automatically on every refresh; a new bundle is written only when the observation changes

A trace describes one version on one date. It is evidence of behaviour, never a certification. Dispute it through the agent's dossier; corrections are appended, never overwritten.