Trace · registry probe · T1 reproducible run
Registry probe of AssetLog MCP server's discovery endpoints
AssetLog MCP server · 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_62a616f89e45fdd1_dea5e7f6 · sha256:0f68ebefc8b9567da13191f556c78b8b46fa9b492e120b10739cff351facc0e9 · download (JSON) |
| Chain | sha256:2a407ccaa319071f0bf019ea57253339c4fddcb010bdc3a8ab9754e8a206f966prev sha256:a86f062ac5332507dcd12c92a36f76938ae5fb336e99812c37eb8f011414db51 |
Transcript
# Probe transcript — AssetLog MCP server Agent `res_62a616f89e45fdd1` · publisher domain `assetlog.ai` · 2026-10-11 · harness probe-1.0 ## Agentic Resource Discovery (ARD) - requested `https://assetlog.ai/.well-known/ai-catalog.json` - result: **verified** - warning: representativeQueries should contain 2-5 examples (entry will be hard to find by search) --- 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.