Trace · registry probe · T1 reproducible run

Registry probe of mcp's discovery endpoints

mcp · 2026-10-25 · 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 invalid (1 validation error)

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_aa5d78ea012ec466_9ddde4e2` · `sha256:727759139e0c56f531cfdf4a9f8c2e6c7c916133c66154f2961ce3d23122ee5a` · download (JSON)
Chain	`sha256:2bd310188e756f2e398c32e18e8f14db7640763d9bb65ca0c786a1e80a9bb0a1` prev sha256:dcbaa54e39e0ddb4aaef8959d9891dbcf7f1a15af6f842fe244e0fdbd92e1b40

Transcript

# Probe transcript — mcp

Agent `res_aa5d78ea012ec466` · publisher domain `fibalo.de` · 2026-10-25 · harness probe-1.0

## Agentic Resource Discovery (ARD)

- requested `https://fibalo.de/.well-known/ai-catalog.json`
- result: **invalid**
- validation error: missing required term 'displayName'
- 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.