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

Bindu · 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. MCP invalid

EntryGET on the publisher's well-known discovery paths
Actionsserved Model Context Protocol (MCP) document
Egressno
Human approval—
Secrets touchedno
Bundlebundles/tr_st_b2094707a8266dc7_713ee666 · sha256:281bae8d517c0b21907930d983f529b36b00c6373f64384a040cc1ff6d415f33 · download (JSON)
Chainsha256:1859d273224fd8c3cc9fae3e49d3372ddf14f436a7a44673e1aebcc4c8a58717
prev sha256:78dd05534fb129f4015fa6c503e6cc86ffc03bdc9e01616cf3805a99ab1fd346

Transcript

# Probe transcript — Bindu

Agent `res_b2094707a8266dc7` · publisher domain `docs.getbindu.com` · 2026-10-11 · harness probe-1.0

## Model Context Protocol (MCP)

- requested `https://docs.getbindu.com/.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.