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 BeeAI Framework's discovery endpoints

BeeAI Framework · 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; 1 validation error); MCP invalid

EntryGET on the publisher's well-known discovery paths
Actionsserved Agent2Agent (A2A) document; served Model Context Protocol (MCP) document
Egressno
Human approval—
Secrets touchedno
Bundlebundles/tr_st_0dc6c6cac3c377b0_8e1c601e · sha256:a3c763751729f99a46455f830355cf3341d83ced1a5397ef93364a319f8bb4bd · download (JSON)
Chainsha256:a3f53442446fa6dd719f4c3dcba81cc4a86203f35cd24af70f7b869bc707aa96
prev sha256:5170c1589e8d62b28bfb01db1ab6bbeb77a87a918de2309126dac498a68a590c

Transcript

# Probe transcript — BeeAI Framework

Agent `res_0dc6c6cac3c377b0` · publisher domain `framework.beeai.dev` · 2026-10-11 · harness probe-1.0

## Agent2Agent (A2A)

- requested `https://framework.beeai.dev/.well-known/agent-card.json`
- result: **invalid**
- declared version: 0.3 (card 1.0.0)
- signed: no
- skills advertised: beeai
- validation error: missing 'description'

## Model Context Protocol (MCP)

- requested `https://framework.beeai.dev/.well-known/mcp.json`
- result: **invalid**

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