Personal Agent Protocol report

hetposthuys.nl

Ora found no poppy.json at hetposthuys.nl/.well-known/poppy.json, so every check Ora runs today reads N/A.

Verdict
No PAP file yet
Profile
pap-1.0@2026-11-21PAP 1.0 (published 2026-11-14)
Last run
Tier 1 probed
Not probed

Each row is one check from the PAP spec, with its outcome, its severity (P0 blocks every agent or is a security MUST, P1 is a MUST that breaks one feature, P2 is a SHOULD or one of Ora's own consistency checks, Advisory never counts against a site) and the section it tests. The full list is in the check catalog, and what Ora's scanner sends is on its own page.

Tier 0: the public files

Plain reads of poppy.json and the documents it points to. None of these requests carries a credential.

40 N/A

  1. T0-01Document exists
    Outcome: N/ASeverity: P0§3
    No poppy.json: HTTP 404
  2. T0-02Redirects safe
    Outcome: N/ASeverity: P0§3
  3. T0-03Valid JSON object
    Outcome: N/ASeverity: P0§3
  4. T0-04Version a 1.0 agent can use
    Outcome: N/ASeverity: P0§3.1
  5. T0-05Organization names its own host
    Outcome: N/ASeverity: P0§3.1
  6. T0-06Has an interface
    Outcome: N/ASeverity: P0§3.1
  7. T0-07Issuer identified
    Outcome: N/ASeverity: P0§3.2
  8. T0-08All URLs HTTPS
    Outcome: N/ASeverity: P0§3
  9. T0-SIBPublished on the requested host
    Outcome: N/ASeverity: P2§3.1
  10. T0-27Other version documents consistent
    Outcome: N/ASeverity: P1§3.4
  11. T0-09Issuer metadata reachable
    Outcome: N/ASeverity: P0§3.2
  12. T0-10Issuer match
    Outcome: N/ASeverity: P0§3.2
  13. T0-11Domain binding
    Outcome: N/ASeverity: P0§3.2
  14. T0-36Issuer metadata URLs well formed
    Outcome: N/ASeverity: P1§3.2
  15. T0-12Required endpoints
    Outcome: N/ASeverity: P0§3.2
  16. T0-38Pushed authorization requests usable
    Outcome: N/ASeverity: P2§4.2, §3.2
  17. T0-22Signing algorithms valid
    Outcome: N/ASeverity: P1§4.1
  18. T0-34Signing algorithm list advertised
    Outcome: N/ASeverity: P2§4.1
  19. T0-23Same sign-in on every domain
    Outcome: N/ASeverity: P1§3.2
  20. ADV-PKCENo plain PKCE
    Outcome: N/ASeverity: Advisoryguides#company-consent
  21. T0-13Scopes defined
    Outcome: N/ASeverity: P1§3.1, §4.7
  22. T0-14Mediated sign-in well formed
    Outcome: N/ASeverity: P1Mediated Sign-In §2
  23. T0-19Extensions named correctly
    Outcome: N/ASeverity: P1§3.3
  24. T0-20Extensions advertised fully
    Outcome: N/ASeverity: P1Ops §2
  25. T0-24Switched off consistently
    Outcome: N/ASeverity: P1§3.2, §6
  26. T0-26Offered scopes described
    Outcome: N/ASeverity: P2§4.7
  27. T0-28Browser sign-in scope listed
    Outcome: N/ASeverity: P2§6
  28. T0-35Requestable scopes listed
    Outcome: N/ASeverity: P2§3.2
  29. T0-15Conversation entries
    Outcome: N/ASeverity: P1§3.1
  30. T0-16API entries
    Outcome: N/ASeverity: P1§3.1
  31. T0-17OpenAPI parses
    Outcome: N/ASeverity: P1§7
  32. T0-18MCP resource metadata
    Outcome: N/ASeverity: P1§7
  33. T0-37Tasks endpoint usable
    Outcome: N/ASeverity: P1§9
  34. T0-39UCP entry lists the UCP extension
    Outcome: N/ASeverity: P1UCP §5
  35. T0-40UCP profile offers Ask
    Outcome: N/ASeverity: P1UCP §5
  36. X-01Same MCP server everywhere
    Outcome: N/ASeverity: P2§7
  37. X-02Same organization
    Outcome: N/ASeverity: P2§3.1
  38. X-04Domains covered
    Outcome: N/ASeverity: P2§3.2
  39. X-10Shared token endpoint lists both protocols' grants
    Outcome: N/ASeverity: P2§3.2
  40. X-12Consistent 401s
    Outcome: N/ASeverity: P2§7

Tier 1: junk requests to the listed endpoints

Requests with no valid credential, which a correct site refuses. They run only when the scan asks for them, at most once per domain every 6 hours.

No Tier 1 probe result from the last 30 days.

10 N/A

  1. T1-01Token endpoint rejects a junk grant
    Outcome: N/ASeverity: P1§4.4
  2. T1-02Error bodies leak nothing
    Outcome: N/ASeverity: Advisoryguides#company-errors
  3. T1-03Conversation endpoint refuses a request with no credentials
    Outcome: N/ASeverity: P0§5.3
  4. T1-05MCP server challenges unauthenticated initialize
    Outcome: N/ASeverity: P1§7
  5. T1-15Browser join page is safe to load
    Outcome: N/ASeverity: P1§6
  6. T1-07Browser endpoint rejects a junk join
    Outcome: N/ASeverity: P0§6
  7. T1-16Browser join authorization requires a Session
    Outcome: N/ASeverity: P1§6
  8. T1-17Website operations endpoint requires a Session
    Outcome: N/ASeverity: P1Ops §4
  9. T1-14Protocol endpoints answer without a redirect
    Outcome: N/ASeverity: P1§3
  10. T1-18Rate limits say when to retry
    Outcome: N/ASeverity: P2§5.6

Ora does not yet send requests with a token or from an account that is signed in. For sign in, Session and conversation endpoints, Ora can check only that they refuse requests without one, not that they work.