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

Firecrawl · 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_f0cc4c95a07b0b53_083acea6 · sha256:ee2550ad863cd43c6cb0dd8a8eb5533f1a8ea798009f002784f246ea25c2278f · download (JSON)
Chainsha256:eafb9b89b377001a61670c68b53bd19fabbda42aaf6ed1c00282e4e85e5a6103
prev sha256:7a60095745baf620828bc71d8119d3efdcac27a233c61299acfd0dab9ed2f6f4

Transcript

# Probe transcript — Firecrawl

Agent `res_f0cc4c95a07b0b53` · publisher domain `firecrawl.dev` · 2026-10-11 · harness probe-1.0

## Model Context Protocol (MCP)

- requested `https://www.firecrawl.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.