Personal Agent Protocol report

tethrd.com

tethrd.com publishes a poppy.json for Draft 0.4. 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.

20 pass, 3 fail, 16 N/A, 1 not measured

  1. T0-01Document exists
    Outcome: PassSeverity: P0§3
    served at https://tethrd.com/.well-known/poppy.json
  2. T0-02Redirects safe
    Outcome: PassSeverity: P0§3
    no redirects
  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.4" (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.4" (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 tethrd.com
  6. T0-06Has an interface
    Outcome: PassSeverity: P0§3.1
    interfaces: agent, web
  7. T0-07Issuer identified
    Outcome: PassSeverity: P0§3.2
    issuer https://shopify.com/authentication/85881946393, from https://tethrd.com/.well-known/oauth-protected-resource
  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 tethrd.com
  10. T0-27Other version documents consistent
    Outcome: N/ASeverity: P1§3.4
    supported_versions lists no other version
  11. T0-09Issuer metadata reachable
    Outcome: PassSeverity: P0§3.2
    https://shopify.com/.well-known/oauth-authorization-server/authentication/85881946393
  12. T0-10Issuer match
    Outcome: PassSeverity: P0§3.2
    issuer https://shopify.com/authentication/85881946393
  13. T0-11Domain binding
    Outcome: PassSeverity: P0§3.2
    protected_resources includes https://tethrd.com
  14. T0-36Issuer metadata URLs well formed
    Outcome: PassSeverity: P1§3.2
    every protected_resources entry (4) is an https URL with no fragment
  15. T0-12Required endpoints
    Outcome: PassSeverity: P0§3.2
    token_endpoint, revocation_endpoint, authorization_endpoint; grant_types_supported includes refresh_token
  16. T0-38Pushed authorization requests usable
    Outcome: N/ASeverity: P2§4.2, §3.2
    the issuer metadata lists no pushed_authorization_request_endpoint and does not require Pushed Authorization Requests
  17. T0-22Signing algorithms valid
    Outcome: N/ASeverity: P1§4.1
    the metadata lists no token_endpoint_auth_signing_alg_values_supported (optional; ES256 and PS384 client assertions are accepted by rule)
  18. T0-34Signing algorithm list advertised
    Outcome: N/ASeverity: P2§4.1
    token_endpoint_auth_methods_supported lists neither private_key_jwt nor client_secret_jwt
  19. T0-23Same sign-in on every domain
    Outcome: PassSeverity: P1§3.2
    tethrd-store.myshopify.com (through its protected resource metadata), www.tethrd.com (through its protected resource metadata) select the same issuer
  20. ADV-PKCENo plain PKCE
    Outcome: PassSeverity: Advisoryguides#company-consent
    PKCE methods: S256
  21. T0-13Scopes defined
    Outcome: PassSeverity: P1§3.1, §4.7
    auth.scopes describes 1 scope
  22. T0-14Mediated sign-in well formed
    Outcome: N/ASeverity: P1Mediated Sign-In §2
    no Mediated Sign-In extension
  23. T0-19Extensions named correctly
    Outcome: PassSeverity: P1§3.3
    extensions: ucp
  24. T0-20Extensions advertised fully
    Outcome: N/ASeverity: P1Ops §2
    operations extension not advertised
  25. T0-24Switched off consistently
    Outcome: N/ASeverity: P1§3.2, §6
    neither auth.disabled nor web.disabled is set
  26. T0-26Offered scopes described
    Outcome: Not measuredSeverity: P2out of scope§4.7
    3 offered scopes not described in auth.scopes or a listed OpenAPI document; the file lists the UCP extension, whose profile may describe them, and Ora does not…Show the full note3 offered scopes not described in auth.scopes or a listed OpenAPI document; the file lists the UCP extension, whose profile may describe them, and Ora does not read it for this row
  27. T0-28Browser sign-in scope listed
    Outcome: N/ASeverity: P2§6
    no browser join (web.browser_session_endpoint)
  28. T0-35Requestable scopes listed
    Outcome: PassSeverity: P2§3.2
    the issuer's scopes_supported lists 6 scopes
  29. T0-15Conversation entries
    Outcome: FailSeverity: P1§3.1
    agent.protocols[0] has no description of what the agent there can help with (required from 1.0, spec 8.1)
  30. T0-16API entries
    Outcome: N/ASeverity: P1§3.1
    no apis
  31. T0-17OpenAPI parses
    Outcome: N/ASeverity: P1§7
    no openapi entries
  32. T0-18MCP resource metadata
    Outcome: N/ASeverity: P1§7
    no mcp entries
  33. T0-37Tasks endpoint usable
    Outcome: N/ASeverity: P1§9
    no tasks block
  34. T0-39UCP entry lists the UCP extension
    Outcome: PassSeverity: P1UCP §5
    the ucp entry comes with the UCP extension at version "1"
  35. T0-40UCP profile offers Ask
    Outcome: PassSeverity: P1UCP §5
    the UCP profile offers dev.ucp.common.ask
  36. X-01Same MCP server everywhere
    Outcome: N/ASeverity: P2§7
    poppy.json lists no MCP server
  37. X-02Same organization
    Outcome: N/ASeverity: P2§3.1
    no ARD catalog host to compare
  38. X-04Domains covered
    Outcome: FailSeverity: P2§3.2
    tethrd-store.account.myshopify.com serves no poppy.json (HTTP 404). tethrd-store.myshopify.com's poppy.json declares "0.4", and a 1.0 agent does not use a file…Show the full notetethrd-store.account.myshopify.com serves no poppy.json (HTTP 404). tethrd-store.myshopify.com's poppy.json declares "0.4", and a 1.0 agent does not use a file that declares a 0.x draft (spec 3.4). www.tethrd.com's poppy.json declares "0.4", and a 1.0 agent does not use a file that declares a 0.x draft (spec 3.4).
  39. X-10Shared token endpoint lists both protocols' grants
    Outcome: N/ASeverity: P2§3.2
    no other protocol shares the PAP issuer's token endpoint
  40. X-12Consistent 401s
    Outcome: N/ASeverity: P2§7
    no recorded 401 challenge from a PAP MCP server

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.

9 N/A, 1 not measured

  1. T1-01Token endpoint rejects a junk grant
    Outcome: Not measuredSeverity: P1out of scope§4.4
    https://shopify.com/authentication/85881946393/oauth/token: off-domain: not on tethrd.com or a bound issuer's domain
  2. T1-02Error bodies leak nothing
    Outcome: N/ASeverity: Advisoryguides#company-errors
    no probe answered
  3. T1-03Conversation endpoint refuses a request with no credentials
    Outcome: N/ASeverity: P0§5.3
    no poppy conversation endpoint
  4. T1-05MCP server challenges unauthenticated initialize
    Outcome: N/ASeverity: P1§7
    no MCP server listed
  5. T1-15Browser join page is safe to load
    Outcome: N/ASeverity: P1§6
    no web.browser_session_endpoint
  6. T1-07Browser endpoint rejects a junk join
    Outcome: N/ASeverity: P0§6
    no web.browser_session_endpoint
  7. T1-16Browser join authorization requires a Session
    Outcome: N/ASeverity: P1§6
    no web.browser_session_endpoint
  8. T1-17Website operations endpoint requires a Session
    Outcome: N/ASeverity: P1Ops §4
    no operations version 3 entry with an endpoint
  9. T1-14Protocol endpoints answer without a redirect
    Outcome: N/ASeverity: P1§3
    no probe sent
  10. T1-18Rate limits say when to retry
    Outcome: N/ASeverity: P2§5.6
    no probe was answered with 429

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.