Reference implementation Data compiled from public sources as of 2026-10-26. Not an assessment, certification or recommendation. Confirm current status with the vendor and the issuing body.
AgentDossier · AI Agent Registry Find agents you can actually trust - public or inside your enterprise.
Trace · registry probe · T1 reproducible run

Registry probe of AgentUtility Agentops's discovery endpoints

AgentUtility Agentops · 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. A2A invalid (unsigned; 3 validation errors)

EntryGET on the publisher's well-known discovery paths
Actionsserved Agent2Agent (A2A) document
Egressno
Human approval—
Secrets touchedno
Bundlebundles/tr_st_f3e91dfe497a4686_d4135101 · sha256:dbae6d269b3c49d91d3da6dc0856998613a66bf82e178c4fcc974329611d48c0 · download (JSON)
Chainsha256:4943f3e34c28854382b8a04cfda0256815cd0a7327303de949c9a922b95a5731
prev sha256:eafb9b89b377001a61670c68b53bd19fabbda42aaf6ed1c00282e4e85e5a6103

Transcript

# Probe transcript — AgentUtility Agentops

Agent `res_f3e91dfe497a4686` · publisher domain `mcp.agentutility.ai` · 2026-10-11 · harness probe-1.0

## Agent2Agent (A2A)

- requested `https://mcp.agentutility.ai/.well-known/agent.json`
- result: **invalid**
- signed: no
- validation error: missing 'name'
- validation error: missing 'description'
- validation error: missing 'version'

---
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.