Wordfence support in MCP Abilities has a clearer path
This release note keeps the Wordfence update compact and gives readers one clear Devenia-owned product path for understanding how MCP abilities are exposed, with Wordfence kept as supporting security context.
Use MCP Expose Abilities for the maintained Devenia product context. Wordfence remains a secondary destination for security-plugin context.
What this release note should clarify
Wordfence focus
The release is about Wordfence-related MCP ability support, not a broad Devenia download directory.
Specific product path
The primary action now points to MCP Expose Abilities, the Devenia-owned page that best matches the reader job for this update.
Secondary context
Wordfence is kept as a distinct external context link, separate from the Devenia product path.
Using Wordfence through an MCP workflow? Leave a comment with the specific action boundary or security check you want documented next.