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 AnomalyArmor's discovery endpoints

AnomalyArmor · 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 verified (unsigned)

EntryGET on the publisher's well-known discovery paths
Actionsserved Agent2Agent (A2A) document
Egressno
Human approval—
Secrets touchedno
Bundlebundles/tr_st_2a740dc49cfa94c7_1ce65f98 · sha256:d65cfb45fd28efcb263ec8d6bfb681b6897b391689c74e8763c4caba587c28a2 · download (JSON)
Chainsha256:b499bbaf5d31c3cb3982d2a3001f67241f4c8bf40edf28ee52361d11e93e322a
prev sha256:f946ac8b75fb4233ae5832fbf623c4d8acd8fc408f2309819cd59b5f419d1e36

Transcript

# Probe transcript — AnomalyArmor

Agent `res_2a740dc49cfa94c7` · publisher domain `anomalyarmor.ai` · 2026-10-11 · harness probe-1.0

## Agent2Agent (A2A)

- requested `https://www.anomalyarmor.ai/.well-known/agent-card.json`
- result: **verified**
- declared version:  (card 1.0.0)
- signed: no
- skills advertised: Monitor data health, Investigate an incident, Set up monitoring, Manage alerts and destinations

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