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

AirShelf Catalog · 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_2b87a4f5a1d08a91_55189d41 · sha256:acd782f4b58a8b733c97a9a002c9a0bfda08a9e97c1bd06e51cc24439212e14d · download (JSON)
Chainsha256:9dfbca363aa278312f13fb1fce86b9ba893c817633a35aca0e4d58c070ff13f3
prev sha256:b499bbaf5d31c3cb3982d2a3001f67241f4c8bf40edf28ee52361d11e93e322a

Transcript

# Probe transcript — AirShelf Catalog

Agent `res_2b87a4f5a1d08a91` · publisher domain `mcp.airshelf.ai` · 2026-10-11 · harness probe-1.0

## Agentic Resource Discovery (ARD)

- requested `https://mcp.airshelf.ai/.well-known/ai-catalog.json`
- result: **verified**
- manifest entries: 1

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