generated: '2026-09-19'
method: probed
hosts:
- host: https://api.memo.bank
  documents:
  - path: /.well-known/oauth-protected-resource
    status: 200
    file: memo-bank-api-oauth-protected-resource.json
    bytes: 164
  - path: /.well-known/oauth-authorization-server/api/apps/mcp/server
    status: 200
    file: memo-bank-api-oauth-authorization-server.json
    bytes: 506
  path_echo_control: passed
x-mcp-probe:
  probed: '2026-09-19'
  issue: roadmap#321, roadmap#337
  documents:
  - host: https://api.memo.bank
    path: /.well-known/oauth-protected-resource
    file: memo-bank-api-oauth-protected-resource.json
  - host: https://api.memo.bank
    path: /.well-known/oauth-authorization-server/api/apps/mcp/server
    file: memo-bank-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.'