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 Build MCP Apps with Skybridge's discovery endpoints

Build MCP Apps with Skybridge · 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_cda9d54e9f789497_e3e706d8 · sha256:d78f0ecda663ed3702046ab7d09af95915e153ca6149f4c65b7a8f30d538e9df · download (JSON)
Chainsha256:c0fb443187cf612f84fe90e8618a9cf970aee7d77a63e744fae2f05cb533e21a
prev sha256:2a365be4f98cab9459163235dd9dd0594344305ca4743b6ec4435560e61daaec

Transcript

# Probe transcript — Build MCP Apps with Skybridge

Agent `res_cda9d54e9f789497` · publisher domain `alpic.ai` · 2026-10-11 · harness probe-1.0

## Agentic Resource Discovery (ARD)

- requested `https://alpic.ai/.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.