wordpress-security

Audit and harden WordPress security configurations across 6.0+ sites.

2|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/joseconti/mcp-skills --skill wordpress-security
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wordpress-security
Source: https://github.com/joseconti/mcp-skills/tree/main/custom/site-security
Command: npx skills add https://github.com/joseconti/mcp-skills --skill wordpress-security

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

WordPress security is often compromised by misconfigurations and weak hardening practices. This Skill provides a structured approach to audit, enforce, and maintain hardened security settings across WordPress installations, reducing exposure to common threats.

Core Features & Use Cases

  • Auditing and validating WordPress security configurations (wp-config.php constants, .htaccess rules, HTTP headers)
  • Applying safe, reversible hardening measures and policy-driven controls
  • Integrating with MCP Content Manager for automated security operations and reporting

Quick Start

Run an initial security audit with mcm/security-audit, review the results, and apply recommended safe measures using mcm/security-apply-safe, ensuring backups and recovery steps are ready.

Frequently Asked Questions about wordpress-security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit and harden WordPress security configurations?

WordPress security hardening involves auditing and validating wp-config.php constants, .htaccess rules, and HTTP headers, then applying safe, reversible measures to enforce protection. This Skill provides a structured workflow to audit, enforce, and maintain hardened settings across installations.

Does WordPress hardening work with Nginx or does it require Apache?

WordPress hardening works natively with Apache and LiteSpeed servers. For Nginx servers, manual configuration is required to apply the equivalent security rules and HTTP header controls.

What's the best way to protect the WordPress REST API and wp-config.php?

The best way to protect WordPress REST API and wp-config.php is by applying policy-driven controls and specific hardening measures. This includes restricting REST API access and enforcing secure constants within your wp-config.php file.

Why do I need MCP Content Manager Premium for WordPress security audits?

You need MCP Content Manager Premium v2.3+ to enable automated security operations and reporting. It provides the underlying capabilities required to run structured audits and apply safe hardening measures programmatically.

What steps should I take before applying WordPress login protections and HTTP headers?

Before applying WordPress login protections and HTTP headers, you should run an initial security audit to review current configurations. Always ensure backups and recovery steps are ready before applying any safe hardening measures.

Can I use this WordPress hardening approach on sites running version 6.0?

Yes, this WordPress hardening approach is applicable to sites running WordPress 6.0 and above. It enforces auditable controls and permissions tailored for these modern installation versions.