Trace · registry probe · T1 reproducible run
Registry probe of Paradev MCP server's discovery endpoints
Paradev 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_b628606a6ef423ec_75d6a87c · sha256:2823dc662f4dae9225b55da87a081fd6ede7fc3f3ac4049cba6afa3593f18553 · download (JSON) |
| Chain | sha256:97cbfbe63e4860fce499435ceee8e23268a29834d91a6804eddc38fae8f9b011prev sha256:82765bc8a3c621e5a1785bb703c6ff24e1f9ee3dca5bd576f3a1d48eb72b8777 |
Transcript
# Probe transcript — Paradev MCP server Agent `res_b628606a6ef423ec` · 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.