v1.0 · public discovery
Check a site for Poppy support
Enter a website. I check its public Poppy discovery and homepage, then show what agents could do next based on what the site says.
poppy-checker / v1.0
What a report shows
A verdict
Compatible with v1.0 on public discovery checks, incomplete or incompatible, or could not verify with the reason.
Required checks
Each check shows a status, the evidence read from the site, a fix and a link to the spec section.
What agents could do next
Suggestions for tasks agents could do on this site, drawn from its public homepage and Poppy files. Each shows the source, a possible Poppy feature and what remains unverified.
The URLs read
The checked URL, the final URL after redirects and each redirect hop.
This independent Kite check reads public discovery documents and homepage text against v1.0. A pass covers public discovery only. It does not run a live OAuth exchange, verify Session JWTs, ask for user consent or test signed-in activity, and it is not an official certification.
Official docs
What Poppy is
Poppy is the Personal Agent Protocol, final version 1.0. A Personal Agent acting for one user works with a company through discovery at /.well-known/poppy.json, sessions, sign-in, APIs, web browsing and conversations. This independent Kite tool checks public discovery against v1.0 and uses homepage text to suggest relevant agent tasks. It is not the protocol’s official validator.
How this check works
Each check reads public files over HTTPS. Nothing is stored.
- 01
Reduce the address to a host
A domain or an https:// URL becomes a host name. Only public domains on port 443 are read.
- 02
Read the discovery file
The server fetches https://{host}/.well-known/poppy.json. It follows up to 5 HTTPS redirects, and the final path must be exactly /.well-known/poppy.json with no query.
- 03
Check the required fields
protocol_version is 1.0 (or a later 1.x), organization.name is present, organization.domain matches the serving host, and at least one of agent, apis or web is present.
- 04
Read sign-in metadata where it is offered
If the site offers sign-in, the protected resource metadata and issuer metadata are checked, including that the issuer lists your domain in protected_resources. A site with no sign-in is not penalized.
- 05
Map optional capabilities
Each optional capability shows whether it is advertised, whether the declaration is well formed, which public documents were read, and what only a real Personal Agent could prove. Leaving one out never changes the verdict; declaring one incorrectly does.
- 06
Report the verdict
Each check links to its spec section. A missing discovery file is a Poppy discovery finding only. It says nothing about MCP or general agent-readiness.
Official docs
Read the spec
The Poppy documents are published by the Personal Agent Protocol. Each check links to the section that covers its fix.
Section map
- #discoveryDiscoveryLinked from the valid JSON and HTTPS redirect checks
- #fieldsFieldsLinked from the organization.name, organization.domain and agent, apis or web checks
- #versionsVersionsLinked from the protocol_version check
- #oauth-serverOAuth serverLinked from the OAuth checks, where sign-in is offered
- #web-browsingWeb browsingLinked from the optional web browser join capability
- #apisAPIsLinked from the optional APIs capability
- #conversationsConversationsLinked from the optional conversations capability
- #scopesScopes and token responsesLinked from the optional scopes_supported check
Poppy checker is an independent tool by Kite. It doesn't certify a site, and it isn't affiliated with or endorsed by the Personal Agent Protocol authors.