Trace · registry probe · T1 reproducible run
Registry probe of Zapier MCP's discovery endpoints
Zapier MCP · 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_a9d3154e70c6aa9f_99bf4703 · sha256:8ab95ce2bb6670e41dcdb4954fe268c731f52843ecad023d2d77360ce79c6026 · download (JSON) |
| Chain | sha256:919bd13aa3a4078a9763fce53d652cab008f9a39ec860137814477f930ce21baprev sha256:530e025cc4bc73f4cd01fadb0af3a8cca11ac7ff12b8c976301fda1bd7630949 |
Transcript
# Probe transcript — Zapier MCP Agent `res_a9d3154e70c6aa9f` · publisher domain `zapier.com` · 2026-10-11 · harness probe-1.0 ## Agentic Resource Discovery (ARD) - requested `https://zapier.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.