Trace · registry probe · T1 reproducible run
Registry probe of Infisical MCP server's discovery endpoints
Infisical 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_2eed6a633897764e_9a435070 · sha256:7a14a1e36f45b4ff558573e5a15be02ed18055ce64d580753abfecfa36092550 · download (JSON) |
| Chain | sha256:c1455ddd32d974458c84fda7181a3ef6b3bbd00b5bfb5e6534f31e7471b683d6prev sha256:605e84819522b7672c6a6d23e4759d70805c2c04f8fa6b09457c703731790e29 |
Transcript
# Probe transcript — Infisical MCP server Agent `res_2eed6a633897764e` · publisher domain `infisical.com` · 2026-10-11 · harness probe-1.0 ## Agentic Resource Discovery (ARD) - requested `https://infisical.com/.well-known/ard.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.