Evidence & methodology
We document a client variant performing an operation through a specific tool. A search backend, page fetcher and browser may have different behavior. A provider identity does not necessarily identify the client using it.
What the labels mean
- Documented: an official document or source establishes the claim.
- Observed: a real run establishes behavior under the recorded conditions, with a sanitized trace and reproduction steps.
- Unknown: not established by the reviewed evidence. It does not mean unsupported.
- Unsupported: evidence establishes lack of support.
- Disputed: sources disagree; consult the evidence and conditions.
- Needs review: verification is more than 90 days old. Age alone does not prove a claim wrong.
What a request can tell you
Accept expresses response preferences. HTML converted to Markdown after retrieval does not prove Markdown was requested. Cached search may never contact the destination website. User-Agent and custom headers are self-reported and can be overridden; they are not authentication. MCP identity belongs to the relevant protocol exchange and is not ordinarily visible to website requests.
Reproducing behavior
Record client and tool versions, mode, permissions, and local or cloud environment. Exercise search, explicit fetch, and browsing separately. Use controlled HTML, Markdown, JSON, redirect and JavaScript pages. Repeat observations, preserve divergent conditions, and retain only allowlisted metadata. Do not collect cookies, credentials, IP addresses or private query text.
Coverage and updates
Configuration coverage indicates how many of the six config surfaces have records. It does not imply complete behavior research. New claims require evidence; older configuration entries may have less precise sourcing. Weekly checks flag inaccessible sources. Source changes still need editorial review.
Schema version: 1.0. Data versions are content hashes; unchanged builds keep the same version and timestamp. Code is MIT; catalog data is CC0.