Trace · registry probe · T1 reproducible run
Registry probe of Paradev docs MCP server's discovery endpoints
Paradev docs MCP server · 2026-10-26 · 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_973128e87ca18c77_04fb39f8 · sha256:bbae569d458500568ce804cd4d53b3b6fd630787234590fd749dcbc0cb2f8dce · download (JSON) |
| Chain | sha256:0ae8aa5910f027f7bba76d3f0ca7131a84785d7b2012c0bb0769d5d6508ce6a6prev sha256:97cbfbe63e4860fce499435ceee8e23268a29834d91a6804eddc38fae8f9b011 |
Transcript
# Probe transcript — Paradev docs MCP server Agent `res_973128e87ca18c77` · publisher domain `paradev.com` · 2026-10-26 · harness probe-1.0 ## Agentic Resource Discovery (ARD) - requested `https://paradev.com/.well-known/ai-catalog.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.