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 Analytics Legends — SAP Analytics Intelligence's discovery endpoints

Analytics Legends — SAP AI & Analytics 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. A2A invalid (unsigned; 1 validation error)

EntryGET on the publisher's well-known discovery paths
Actionsserved Agent2Agent (A2A) document
Egressno
Human approval—
Secrets touchedno
Bundlebundles/tr_st_8c253a3b828faad3_737cf267 · sha256:edafc03c208a736d48e0af2cd3791388d5d2d08c162b1f2963f75cdc5369cc7a · download (JSON)
Chainsha256:ddd5cac91c88b0665d3a72a289db260f4f853c1868d29f9c62c768eef197595f
prev sha256:66209d6d590e2d039b96063695bf3bdad459d574a61743b61c6567ba719169ad

Transcript

# Probe transcript — Analytics Legends — SAP Analytics Intelligence

Agent `res_8c253a3b828faad3` · publisher domain `analyticslegends.ai` · 2026-10-11 · harness probe-1.0

## Agent2Agent (A2A)

- requested `https://analyticslegends.ai/.well-known/agent.json`
- result: **invalid**
- declared version:  (card 1.84.0)
- signed: no
- validation error: missing service endpoint ('url' or 'supportedInterfaces')

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