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.
Trace · registry probe · T1 reproducible run

Registry probe of LobeChat's discovery endpoints

LobeChat · 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; 4 validation errors)

EntryGET on the publisher's well-known discovery paths
Actionsserved Agent2Agent (A2A) document
Egressno
Human approval—
Secrets touchedno
Bundlebundles/tr_st_e27b317e0e601da0_79ecd0dc · sha256:f0848ad74e4eb2ebd164a0fce49acf86eb07c26ba7329e3bdac533fdbee19874 · download (JSON)
Chainsha256:ac57da0eb80b12a21456da4ea1c9f94716139f25585969cdf8c2b4a73d6eb519
prev sha256:04fe85ba0b474af68186cb17d38bca2db7564563290688ba66ae39351130bfd5

Transcript

# Probe transcript — LobeChat

Agent `res_e27b317e0e601da0` · publisher domain `lobehub.com` · 2026-10-11 · harness probe-1.0

## Agent2Agent (A2A)

- requested `https://lobehub.com/.well-known/agent-card.json`
- result: **invalid**
- declared version:  (card 1.0.0)
- signed: no
- validation error: missing service endpoint ('url' or 'supportedInterfaces')
- validation error: skills[0] missing id/name
- validation error: skills[1] missing id/name
- validation error: skills[2] missing id/name

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