Trace · registry probe · T1 reproducible run
Registry probe of AIvikings Domain Registrar MCP Server's discovery endpoints
AIvikings Domain Registrar 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_e94f862833335606_4c4836b9 · sha256:3572725eac0b34a0a21d1225cc01865b6ee9716f05d4023e62316f22c0d9f44b · download (JSON) |
| Chain | sha256:f56b1e4089abca1f30dedbcea22a7126755acc9308f435926a7930efbf5971f3prev sha256:9064f8166bfe270beda37bb4826a1c23f2c4230c60c18f9d6ce623599a38ac37 |
Transcript
# Probe transcript — AIvikings Domain Registrar MCP Server Agent `res_e94f862833335606` · publisher domain `aivikings.ai` · 2026-10-11 · harness probe-1.0 ## Agentic Resource Discovery (ARD) - requested `https://aivikings.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.