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

superset-mcp · 2026-10-26 · 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_c069233e08e7a70b_2a4de42b · sha256:17172c246784075fb3d04b15adcd2d28a59a0d259c1211def982df3f438e2432 · download (JSON)
Chainsha256:74d293fab974ffcff002718cc2e959dd3d79fd4f9da73397b0c20db44466d7be
prev sha256:ee2694afd03638cd53c4dd031800155df89c5ffa9cdfdc87e7794f17a5b21ee3

Transcript

# Probe transcript — superset-mcp

Agent `res_c069233e08e7a70b` · publisher domain `paradev.com` · 2026-10-26 · harness probe-1.0

## Agentic Resource Discovery (ARD)

- requested `https://paradev.com/.well-known/ai-catalog.json`
- result: **verified**
- warning: representativeQueries should contain 2-5 examples (entry will be hard to find by search)

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