Personal Agent Protocol report

townhousecartagena.com

townhousecartagena.com publishes a poppy.json for Draft 0.3. Agents built for 1.0, the published version, do not read files written for an earlier draft. Every row below grades this file by the 1.0 rules, so each failure is a change to make when you move the file to 1.0.

Verdict
Set up, with problems
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.

7 pass, 2 fail, 31 N/A

  1. T0-01Document exists
    Outcome: PassSeverity: P0§3
    served at https://www.townhousecartagena.com/.well-known/poppy.json
  2. T0-02Redirects safe
    Outcome: PassSeverity: P0§3
    1 redirect(s), all HTTPS
  3. T0-03Valid JSON object
    Outcome: PassSeverity: P0§3
    a JSON object
  4. T0-04Version a 1.0 agent can use
    Outcome: FailSeverity: P0§3.1
    Set protocol_version to "1.0", or list a 1.0 document on this host in supported_versions. No 1.0 agent uses a file that declares "0.3" (spec 3.4). Until Novembe…Show the full noteSet protocol_version to "1.0", or list a 1.0 document on this host in supported_versions. No 1.0 agent uses a file that declares "0.3" (spec 3.4). Until November 2026 Ora graded each file by the draft it declares; Ora now grades every file by 1.0.
  5. T0-05Organization names its own host
    Outcome: PassSeverity: P0§3.1
    organization.domain www.townhousecartagena.com; the file was requested from townhousecartagena.com and served by www.townhousecartagena.com, so it speaks for ww…Show the full noteorganization.domain www.townhousecartagena.com; the file was requested from townhousecartagena.com and served by www.townhousecartagena.com, so it speaks for www.townhousecartagena.com
  6. T0-06Has an interface
    Outcome: PassSeverity: P0§3.1
    interfaces: apis, web
  7. T0-07Issuer identified
    Outcome: FailSeverity: P0§3.2
    https://www.townhousecartagena.com/.well-known/oauth-protected-resource: its resource is "https://www.townhousecartagena.com/", not https://www.townhousecartage…Show the full notehttps://www.townhousecartagena.com/.well-known/oauth-protected-resource: its resource is "https://www.townhousecartagena.com/", not https://www.townhousecartagena.com; an agent reads only a 404 or valid metadata as "no issuer", and never falls back to the domain after any other answer
  8. T0-08All URLs HTTPS
    Outcome: PassSeverity: P0§3
    every URL is https
  9. T0-SIBPublished on the requested host
    Outcome: PassSeverity: P2§3.1
    published on townhousecartagena.com
  10. T0-27Other version documents consistent
    Outcome: N/ASeverity: P1§3.4
    an agent stops at poppy.json (T0-07)
  11. T0-09Issuer metadata reachable
    Outcome: N/ASeverity: P0§3.2
    poppy.json fails T0-07 (see pap-discovery)
  12. T0-10Issuer match
    Outcome: N/ASeverity: P0§3.2
    poppy.json fails T0-07 (see pap-discovery)
  13. T0-11Domain binding
    Outcome: N/ASeverity: P0§3.2
    poppy.json fails T0-07 (see pap-discovery)
  14. T0-36Issuer metadata URLs well formed
    Outcome: N/ASeverity: P1§3.2
    poppy.json fails T0-07 (see pap-discovery)
  15. T0-12Required endpoints
    Outcome: N/ASeverity: P0§3.2
    poppy.json fails T0-07 (see pap-discovery)
  16. T0-38Pushed authorization requests usable
    Outcome: N/ASeverity: P2§4.2, §3.2
    poppy.json fails T0-07 (see pap-discovery)
  17. T0-22Signing algorithms valid
    Outcome: N/ASeverity: P1§4.1
    poppy.json fails T0-07 (see pap-discovery)
  18. T0-34Signing algorithm list advertised
    Outcome: N/ASeverity: P2§4.1
    poppy.json fails T0-07 (see pap-discovery)
  19. T0-23Same sign-in on every domain
    Outcome: N/ASeverity: P1§3.2
    poppy.json fails T0-07 (see pap-discovery)
  20. ADV-PKCENo plain PKCE
    Outcome: N/ASeverity: Advisoryguides#company-consent
    poppy.json fails T0-07 (see pap-discovery)
  21. T0-13Scopes defined
    Outcome: N/ASeverity: P1§3.1, §4.7
    poppy.json fails T0-07 (see pap-discovery)
  22. T0-14Mediated sign-in well formed
    Outcome: N/ASeverity: P1Mediated Sign-In §2
    poppy.json fails T0-07 (see pap-discovery)
  23. T0-19Extensions named correctly
    Outcome: N/ASeverity: P1§3.3
    poppy.json fails T0-07 (see pap-discovery)
  24. T0-20Extensions advertised fully
    Outcome: N/ASeverity: P1Ops §2
    poppy.json fails T0-07 (see pap-discovery)
  25. T0-24Switched off consistently
    Outcome: N/ASeverity: P1§3.2, §6
    poppy.json fails T0-07 (see pap-discovery)
  26. T0-26Offered scopes described
    Outcome: N/ASeverity: P2§4.7
    poppy.json fails T0-07 (see pap-discovery)
  27. T0-28Browser sign-in scope listed
    Outcome: N/ASeverity: P2§6
    poppy.json fails T0-07 (see pap-discovery)
  28. T0-35Requestable scopes listed
    Outcome: N/ASeverity: P2§3.2
    poppy.json fails T0-07 (see pap-discovery)
  29. T0-15Conversation entries
    Outcome: N/ASeverity: P1§3.1
    poppy.json fails T0-07 (see pap-discovery)
  30. T0-16API entries
    Outcome: N/ASeverity: P1§3.1
    poppy.json fails T0-07 (see pap-discovery)
  31. T0-17OpenAPI parses
    Outcome: N/ASeverity: P1§7
    poppy.json fails T0-07 (see pap-discovery)
  32. T0-18MCP resource metadata
    Outcome: N/ASeverity: P1§7
    poppy.json fails T0-07 (see pap-discovery)
  33. T0-37Tasks endpoint usable
    Outcome: N/ASeverity: P1§9
    poppy.json fails T0-07 (see pap-discovery)
  34. T0-39UCP entry lists the UCP extension
    Outcome: N/ASeverity: P1UCP §5
    poppy.json fails T0-07 (see pap-discovery)
  35. T0-40UCP profile offers Ask
    Outcome: N/ASeverity: P1UCP §5
    poppy.json fails T0-07 (see pap-discovery)
  36. X-01Same MCP server everywhere
    Outcome: N/ASeverity: P2§7
    poppy.json fails T0-07 (see pap-discovery)
  37. X-02Same organization
    Outcome: N/ASeverity: P2§3.1
    poppy.json fails T0-07 (see pap-discovery)
  38. X-04Domains covered
    Outcome: N/ASeverity: P2§3.2
    poppy.json fails T0-07 (see pap-discovery)
  39. X-10Shared token endpoint lists both protocols' grants
    Outcome: N/ASeverity: P2§3.2
    poppy.json fails T0-07 (see pap-discovery)
  40. X-12Consistent 401s
    Outcome: N/ASeverity: P2§7
    poppy.json fails T0-07 (see pap-discovery)

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 not measured

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

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.