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 Pydantic Logfire MCP Server's discovery endpoints

Pydantic Logfire 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

EntryGET on the publisher's well-known discovery paths
Actionsserved Agentic Resource Discovery (ARD) document
Egressno
Human approval—
Secrets touchedno
Bundlebundles/tr_st_9688dea3f9480b7a_d17a024f · sha256:5408fa2e8c78dac5168f2f56aada44436f1bf218a410978abc41df36b573fad9 · download (JSON)
Chainsha256:e751d9729f503afe9066ccd8447033c4779b93fc24f84bd0da1e7942e9b848e4
prev sha256:ebff729cda44f00839e4ca20bfb328296d5f1647e3671780e48290c488b70058

Transcript

# Probe transcript — Pydantic Logfire MCP Server

Agent `res_9688dea3f9480b7a` · publisher domain `pydantic.dev` · 2026-10-11 · harness probe-1.0

## Agentic Resource Discovery (ARD)

- requested `https://pydantic.dev/.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.