@respira/wordpress-mcp-server@8.2.11
WordPress MCP server with MCP 2026-07-28 and legacy-client support. 198 tools, 303 with WooCommerce, across 17 page builders and the Site Editor.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is an explicit-user-command AI-agent configuration installer backed by a remote vendor payload, so it warrants a warning. Source inspection found no lifecycle hook or unconsented install-time mutation that would justify a block.
Decision evidence
public snapshot- Explicit --install-config fetches a remote configuration payload for an AI client.
- The setup command merges and writes a named MCP-server entry into client configuration, including ~/.codex/config.toml.
- Runtime telemetry sends bearer-authenticated usage batches to Respira.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- Client-config mutation is gated behind explicit --install-config plus client and token arguments.
- Config merge targets only the supplied server name; no arbitrary file path is accepted.
Source & flagged code
4 flagged · loading sourceManifest-reachable source overwrites another installed package with package-defined remote behavior.
dist/server.jsView on unpkgThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/server.jsView on unpkgFindings
Affected versions and remediation
This report applies to @respira/wordpress-mcp-server@8.2.11.
See all versions of @respira/wordpress-mcp-server for other recorded verdicts.
- Review the evidence and your use of @respira/wordpress-mcp-server@8.2.11 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.