Trace · registry probe · T1 reproducible run
Registry probe of Agentgates MCP server's discovery endpoints
Agentgates 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_9d5b0c0ba98fd29e_c8b77e89 · sha256:206c275e33a367dc9f19e836fcf9e860e5fef4ac8c0e2dc3ad45269987d8c0bf · download (JSON) |
| Chain | sha256:47652e8e19f60b0a115fddd8b2ce2a3b07e2d3f4915e7d9284d8bdb53780d310prev sha256:6e2cc0e49c3a679cf19a84b8f00e13a5ab909315360f42111d8b15c57acef1d6 |
Transcript
# Probe transcript — Agentgates MCP server Agent `res_9d5b0c0ba98fd29e` · publisher domain `agentgates.ai` · 2026-10-11 · harness probe-1.0 ## Agentic Resource Discovery (ARD) - requested `https://agentgates.ai/.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.