Trace · registry probe · T1 reproducible run
Registry probe of Aard MCP's discovery endpoints
Aard MCP · 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. ARD verified
| Entry | GET on the publisher's well-known discovery paths |
| Actions | served Agentic Resource Discovery (ARD) document |
| Egress | no |
| Human approval | — |
| Secrets touched | no |
| Bundle | bundles/tr_st_d2972fd5877c3493_34d2beae · sha256:ac83a3b5383e2db7404208bad76eeeb51dd1b877047a201faa90160f7991da94 · download (JSON) |
| Chain | sha256:4a792c1d2985eea9dd0173dbc8b5a3bce3ad2c25d716c8ed1c09b97ff29981d1prev sha256:d9e74efde9426f4de985237aa0fe201f6394225597fc5ae8f62b7abb0539e3f4 |
Transcript
# Probe transcript — Aard MCP Agent `res_d2972fd5877c3493` · publisher domain `aard.ai` · 2026-10-11 · harness probe-1.0 ## Agentic Resource Discovery (ARD) - requested `https://aard.ai/.well-known/ard.json` - result: **verified** --- 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.