Personal Agent Protocol report
getaroom.dev
getaroom.dev publishes a poppy.json, and no P0 or P1 check fails.
- Verdict
- Working
- 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.
10 pass, 30 N/A
- T0-01Document existsserved at https://getaroom.dev/.well-known/poppy.json
- T0-02Redirects safeno redirects
- T0-03Valid JSON objecta JSON object
- T0-04Version a 1.0 agent can useprotocol_version 1.0
- T0-05Organization names its own hostorganization.domain getaroom.dev
- T0-06Has an interfaceinterfaces: web
- T0-07Issuer identifiedno issuer (https://getaroom.dev/.well-known/oauth-protected-resource lists no authorization_servers): the Company offers signed-out Sessions only
- T0-08All URLs HTTPSevery URL is https
- T0-SIBPublished on the requested hostpublished on getaroom.dev
- T0-27Other version documents consistentsupported_versions lists no other version
- T0-09Issuer metadata reachableThe Company has no issuer, so it offers signed-out Sessions only
- T0-10Issuer matchThe Company has no issuer, so it offers signed-out Sessions only
- T0-11Domain bindingThe Company has no issuer, so it offers signed-out Sessions only
- T0-36Issuer metadata URLs well formedThe Company has no issuer, so it offers signed-out Sessions only
- T0-12Required endpointsThe Company has no issuer, so it offers signed-out Sessions only
- T0-38Pushed authorization requests usableThe Company has no issuer, so it offers signed-out Sessions only
- T0-22Signing algorithms validThe Company has no issuer, so it offers signed-out Sessions only
- T0-34Signing algorithm list advertisedThe Company has no issuer, so it offers signed-out Sessions only
- T0-23Same sign-in on every domainThe Company has no issuer, so it offers signed-out Sessions only
- ADV-PKCENo plain PKCEThe Company has no issuer, so it offers signed-out Sessions only
- T0-13Scopes definedno auth.scopes or auth.scope_hints
- T0-14Mediated sign-in well formedno Mediated Sign-In extension
- T0-19Extensions named correctlyno extensions
- T0-20Extensions advertised fullyoperations extension not advertised
- T0-24Switched off consistentlyneither auth.disabled nor web.disabled is set
- T0-26Offered scopes describedno issuer, so no offered scopes
- T0-28Browser sign-in scope listedno browser join (web.browser_session_endpoint)
- T0-35Requestable scopes listedno issuer, so the Company offers no sign-in
- T0-15Conversation entriesno agent block
- T0-16API entriesno apis
- T0-17OpenAPI parsesno openapi entries
- T0-18MCP resource metadatano mcp entries
- T0-37Tasks endpoint usableno tasks block
- T0-39UCP entry lists the UCP extensionagent.protocols lists no ucp entry
- T0-40UCP profile offers Askagent.protocols lists no ucp entry
- X-01Same MCP server everywherepoppy.json lists no MCP server
- X-02Same organizationthe ARD catalog host names the same organization
- X-04Domains coveredprotected_resources lists no other domain
- X-10Shared token endpoint lists both protocols' grantsno other protocol shares the PAP issuer's token endpoint
- X-12Consistent 401sno 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.
10 N/A
- T1-01Token endpoint rejects a junk grantthe Company has no issuer
- T1-02Error bodies leak nothingno probe answered
- T1-03Conversation endpoint refuses a request with no credentialsno poppy conversation endpoint
- T1-05MCP server challenges unauthenticated initializeno MCP server listed
- T1-15Browser join page is safe to loadno web.browser_session_endpoint
- T1-07Browser endpoint rejects a junk joinno web.browser_session_endpoint
- T1-16Browser join authorization requires a Sessionno web.browser_session_endpoint
- T1-17Website operations endpoint requires a Sessionno operations version 3 entry with an endpoint
- T1-14Protocol endpoints answer without a redirectno probe sent
- T1-18Rate limits say when to retryno 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.