Trace · registry probe · T1 reproducible run
Registry probe of Apify MCP server's discovery endpoints
Apify 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_f57cf5673dda9291_a367558c · sha256:ebe54d30b96b61c7af804494fa946dd9ea1009b1fcf7ed879a3fddeebf628d31 · download (JSON) |
| Chain | sha256:7d1e0d782b043ba0bfc3b7ebc6b24ace922393ab042e05ec12cf26303c3045fcprev sha256:20ee127f4a8eda90294dfa456bd995cb5bea9e87bdbae6953e078160338e900d |
Transcript
# Probe transcript — Apify MCP server Agent `res_f57cf5673dda9291` · publisher domain `apify.com` · 2026-10-11 · harness probe-1.0 ## Agentic Resource Discovery (ARD) - requested `https://apify.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.