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
- T0-01Document existsserved at https://www.townhousecartagena.com/.well-known/poppy.json
- T0-02Redirects safe1 redirect(s), all HTTPS
- T0-03Valid JSON objecta JSON object
- T0-04Version a 1.0 agent can use
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 noteHide the full note
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 November 2026 Ora graded each file by the draft it declares; Ora now grades every file by 1.0. - T0-05Organization names its own host
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 noteHide the full note
organization.domain www.townhousecartagena.com; the file was requested from townhousecartagena.com and served by www.townhousecartagena.com, so it speaks for www.townhousecartagena.com - T0-06Has an interfaceinterfaces: apis, web
- T0-07Issuer identified
https://www.townhousecartagena.com/.well-known/oauth-protected-resource: its resource is "https://www.townhousecartagena.com/", not https://www.townhousecartage…Show the full noteHide the full note
https://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 - T0-08All URLs HTTPSevery URL is https
- T0-SIBPublished on the requested hostpublished on townhousecartagena.com
- T0-27Other version documents consistentan agent stops at poppy.json (T0-07)
- T0-09Issuer metadata reachablepoppy.json fails T0-07 (see pap-discovery)
- T0-10Issuer matchpoppy.json fails T0-07 (see pap-discovery)
- T0-11Domain bindingpoppy.json fails T0-07 (see pap-discovery)
- T0-36Issuer metadata URLs well formedpoppy.json fails T0-07 (see pap-discovery)
- T0-12Required endpointspoppy.json fails T0-07 (see pap-discovery)
- T0-38Pushed authorization requests usablepoppy.json fails T0-07 (see pap-discovery)
- T0-22Signing algorithms validpoppy.json fails T0-07 (see pap-discovery)
- T0-34Signing algorithm list advertisedpoppy.json fails T0-07 (see pap-discovery)
- T0-23Same sign-in on every domainpoppy.json fails T0-07 (see pap-discovery)
- ADV-PKCENo plain PKCEpoppy.json fails T0-07 (see pap-discovery)
- T0-13Scopes definedpoppy.json fails T0-07 (see pap-discovery)
- T0-14Mediated sign-in well formedpoppy.json fails T0-07 (see pap-discovery)
- T0-19Extensions named correctlypoppy.json fails T0-07 (see pap-discovery)
- T0-20Extensions advertised fullypoppy.json fails T0-07 (see pap-discovery)
- T0-24Switched off consistentlypoppy.json fails T0-07 (see pap-discovery)
- T0-26Offered scopes describedpoppy.json fails T0-07 (see pap-discovery)
- T0-28Browser sign-in scope listedpoppy.json fails T0-07 (see pap-discovery)
- T0-35Requestable scopes listedpoppy.json fails T0-07 (see pap-discovery)
- T0-15Conversation entriespoppy.json fails T0-07 (see pap-discovery)
- T0-16API entriespoppy.json fails T0-07 (see pap-discovery)
- T0-17OpenAPI parsespoppy.json fails T0-07 (see pap-discovery)
- T0-18MCP resource metadatapoppy.json fails T0-07 (see pap-discovery)
- T0-37Tasks endpoint usablepoppy.json fails T0-07 (see pap-discovery)
- T0-39UCP entry lists the UCP extensionpoppy.json fails T0-07 (see pap-discovery)
- T0-40UCP profile offers Askpoppy.json fails T0-07 (see pap-discovery)
- X-01Same MCP server everywherepoppy.json fails T0-07 (see pap-discovery)
- X-02Same organizationpoppy.json fails T0-07 (see pap-discovery)
- X-04Domains coveredpoppy.json fails T0-07 (see pap-discovery)
- X-10Shared token endpoint lists both protocols' grantspoppy.json fails T0-07 (see pap-discovery)
- X-12Consistent 401spoppy.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
- T1-01Token endpoint rejects a junk grantpoppy.json fails T0-07 (see pap-discovery)
- T1-02Error bodies leak nothingpoppy.json fails T0-07 (see pap-discovery)
- T1-03Conversation endpoint refuses a request with no credentialspoppy.json fails T0-07 (see pap-discovery)
- T1-05MCP server challenges unauthenticated initializepoppy.json fails T0-07 (see pap-discovery)
- T1-15Browser join page is safe to loadpoppy.json fails T0-07 (see pap-discovery)
- T1-07Browser endpoint rejects a junk joinpoppy.json fails T0-07 (see pap-discovery)
- T1-16Browser join authorization requires a Sessionpoppy.json fails T0-07 (see pap-discovery)
- T1-17Website operations endpoint requires a Sessionpoppy.json fails T0-07 (see pap-discovery)
- T1-14Protocol endpoints answer without a redirectpoppy.json fails T0-07 (see pap-discovery)
- T1-18Rate limits say when to retrypoppy.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.