generated: '2026-09-19'
method: searched
notes: OAuth/OIDC discovery documents are served by Clerk (issuer clerk.tinyfish.ai) and cover TinyFish
  dashboard/user SSO login, not the programmatic API. The public APIs (Agent, Search, Fetch, Browser)
  authenticate with an X-API-Key header.
hosts:
- host: https://agent.tinyfish.ai
  documents:
  - path: /.well-known/openid-configuration
    status: 200
    file: tinyfish-openid-configuration.json
  - path: /.well-known/oauth-authorization-server
    status: 200
    file: tinyfish-oauth-authorization-server.json
  - path: /.well-known/security.txt
    status: 404
  - path: /.well-known/api-catalog
    status: 404
  - path: /.well-known/ai-plugin.json
    status: 404
  - path: /.well-known/oauth-protected-resource
    status: 200
    file: tinyfish-agent-oauth-protected-resource.json
    bytes: 747
  path_echo_control: passed
- host: https://docs.tinyfish.ai
  documents:
  - path: /.well-known/security.txt
    status: 404
  - path: /.well-known/openid-configuration
    status: 404
- host: https://api.search.tinyfish.ai
  documents:
  - path: /.well-known/security.txt
    status: 404
- host: https://www.tinyfish.ai
  documents:
  - path: /.well-known/security.txt
    status: 404
- host: https://clerk.tinyfish.ai
  documents:
  - path: /.well-known/oauth-authorization-server
    status: 200
    file: tinyfish-clerk-oauth-authorization-server.json
    bytes: 1192
  path_echo_control: passed
x-mcp-probe:
  probed: '2026-09-19'
  issue: roadmap#321, roadmap#337
  documents:
  - host: https://agent.tinyfish.ai
    path: /.well-known/oauth-protected-resource
    file: tinyfish-agent-oauth-protected-resource.json
  - host: https://clerk.tinyfish.ai
    path: /.well-known/oauth-authorization-server
    file: tinyfish-clerk-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.'