Registry probe of Paradev's discovery endpoints

Paradev · 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. A2A verified (auth oauth2; unsigned); MCP invalid; ARD verified

Transcript

# Probe transcript — Paradev

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

## Agent2Agent (A2A)

- requested `https://paradev.com/.well-known/agent-card.json`
- result: **verified**
- declared version: 0.3.0 (card 1.0.0)
- auth schemes: oauth2
- signed: no
- skills advertised: Workspace orchestration, Coding-agent sessions, Automations, Task tracking

## Model Context Protocol (MCP)

- requested `https://paradev.com/.well-known/mcp.json`
- result: **invalid**

## Agentic Resource Discovery (ARD)

- requested `https://paradev.com/.well-known/ai-catalog.json`
- result: **verified**
- manifest entries: 13

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