Discovery formats have different scopes and levels of maturity. CYBERMAPS labels them separately so administrators can enable the capabilities their clients actually use.
A practical protocol map
| Surface | Role | Maturity and scope |
|---|---|---|
| API Catalog and Linkset | Advertise public APIs and their descriptions | RFC 9727 and RFC 9264 |
| OpenAPI | Describe implemented API operations | Plugin canonical representation is 3.2.0; documented 3.1.2 negotiation is retained |
| MCP | Expose tools to compatible clients | Optional plugin modes and permissions; disabled by default |
| MCP Server Card | Describe a remote MCP service | Experimental metadata, separate from live tool discovery |
| ARD | Describe discoverable resources | Plugin retains its documented predecessor catalog; this website uses the v0.91 proposal |
| Markdown for Agents | Negotiate readable source content | Opt-in vendor convention; normal requests remain HTML |
| llms.txt | Provide a readable map of site content | Community convention for content discovery by compatible clients |
Be precise about ADP
The plugin documentation describes a revision-pinned conformance profile for AI Discovery Protocol 3.0 Level 3, covering a defined set of publications. This is not an unqualified claim about every protocol named ADP. Its manifest, bounded updates, and news publications each remain conditional on their own settings.
Keep authority separate from discovery
Publishing a manifest does not grant access to private WordPress data. Plugin MCP modes and authorization rules govern the operations a client can use. Browser tools add no new server authority.
This website has a separate, public, read-only API over its published pages. It cannot control an installed plugin.
Read the plugin’s exact agent-access contract or use this website’s public API.