@respira/wordpress-mcp-server@8.3.27
WordPress MCP server + companion plugin giving AI native access to page builder content, not just the REST API. 230 tools, 335 with WooCommerce, 17 page builders and the Site Editor. Element-level edits, full page creation, HTML to builder conversion, sna
AI Security Review
scanned 12d ago · by lpm-firewall-aiSource inspection found no npm install lifecycle hook or concrete attack behavior. Agent configuration changes are initiated by explicit commands, and the setup fetch targets the package's Respira service with a supplied token.
Decision evidence
public snapshot- package.json defines no install lifecycle hook; setup is a separate, explicitly invoked command.
- Setup targets named agent configuration files, fetches config from the Respira website using a supplied install token, and writes a single named MCP server entry.
- The skills installer copies bundled skill files only when its command is invoked; existing files are skipped unless force is specified.
- The flagged config location describes configuration precedence; it does not show secret collection or exfiltration.
- The server's process-list command is limited to diagnostic process inspection.
Source & flagged code
6 flagged · loading sourceManifest-trigger-reachable source writes behavior-bearing configuration into a user or project AI-agent control surface.
dist/install-skills.jsView on unpkgFindings
Affected versions and remediation
This report applies to @respira/wordpress-mcp-server@8.3.27.
See all versions of @respira/wordpress-mcp-server for other recorded verdicts.
- Review the evidence and your use of @respira/wordpress-mcp-server@8.3.27 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.