generated: '2026-09-19'
method: probed
hosts:
- host: https://audd.io
  documents:
  - path: /.well-known/api-catalog
    status: 200
    type: application/linkset+json; profile="https://www.rfc-editor.org/info/rfc9727"
    file: audd-api-catalog.json
    bytes: 3986
    fetched: '2026-10-08'
    note: 'RFC 9727 linkset, anchor https://api.audd.io/; service-desc https://audd.io/openapi.json (OpenAPI 3.1 for api.audd.io
      and enterprise.audd.io); service-doc for the standard endpoint, streams and custom catalog. Added 2026-10-08 on AudD''s
      correction request; an invented path on audd.io returns a real 404.'
- host: https://mcp.audd.io
  documents:
  - path: /.well-known/oauth-protected-resource
    status: 200
    file: audd-mcp-oauth-protected-resource.json
    bytes: 373
  path_echo_control: passed
- host: https://dashboard-api.audd.io
  documents:
  - path: /.well-known/oauth-authorization-server
    status: 200
    file: audd-dashboard-api-oauth-authorization-server.json
    bytes: 1203
  path_echo_control: passed
x-mcp-probe:
  probed: '2026-09-19'
  issue: roadmap#321, roadmap#337
  documents:
  - host: https://mcp.audd.io
    path: /.well-known/oauth-protected-resource
    file: audd-mcp-oauth-protected-resource.json
  - host: https://dashboard-api.audd.io
    path: /.well-known/oauth-authorization-server
    file: audd-dashboard-api-oauth-authorization-server.json
  validated_on: resource (RFC 9728) / issuer (RFC 8414, OIDC)
  negative_control: one per host; a 2xx JSON object at an impossible path discards the host
note: 'MCP-host OAuth discovery added 2026-09-19 (roadmap#321/#337): the harvest visits a provider''s
  primary hosts, and RFC 9728 protected-resource metadata lives on the MCP host, so these documents existed
  and were invisible to the scorer. Fetched live and validated on `resource`/`issuer`; one negative control
  per host.'