WP HealthKit
NPM · @WPHEALTHKIT/MCP-SERVER · 2 COMPONENTS · SCANNED SEP 30
Security audits for WordPress plugins and themes — 62 verification layers, fix plans and SBOMs.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 53 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1327 tokens (~69/item across 19 items; 13 tools + 6 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the WP HealthKit MCP server?
WP HealthKit runs locally as an npm package, launched with npx -y @wphealthkit/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @wphealthkit/mcp-server
claude mcp add com-wphealthkit-mcp-server -- npx -y @wphealthkit/mcp-server
{
"mcpServers": {
"com-wphealthkit-mcp-server": {
"command": "npx",
"args": [
"-y",
"@wphealthkit/mcp-server"
]
}
}
} {
"servers": {
"com-wphealthkit-mcp-server": {
"command": "npx",
"args": [
"-y",
"@wphealthkit/mcp-server"
]
}
}
} codex mcp add com-wphealthkit-mcp-server -- npx -y @wphealthkit/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-wphealthkit-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@wphealthkit/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add com-wphealthkit-mcp-server --command npx --arg -y --arg @wphealthkit/mcp-server
mcp_servers:
com-wphealthkit-mcp-server:
command: "npx"
args: ["-y", "@wphealthkit/mcp-server"] {
"McpServers": {
"com-wphealthkit-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@wphealthkit/mcp-server"
]
}
}
} assistant mcp add com-wphealthkit-mcp-server -t stdio -c npx -a -y @wphealthkit/mcp-server
{
"mcpServers": {
"com-wphealthkit-mcp-server": {
"command": "npx",
"args": [
"-y",
"@wphealthkit/mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 −3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- Stability: 0.97 → pass security
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 30 Sept 2026 · Analysed npm/@wphealthkit/mcp-server@0.6.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_plugin ~103
Trigger a security audit for a WordPress plugin by its wp.org slug. Optionally pass engines: ['performance'] for extended performance analysis (+1 token). Submits to the job queue and polls until complete (up to 20 minutes). Returns the full audit summary.
| Name | Type | Req | Description |
|---|---|---|---|
| engines | array | – | Optional extra engines. ['performance'] adds performance analysis (+1 token). |
| slug | string | yes | The wp.org plugin slug (e.g. 'contact-form-7') |
No output schema declared.
No examples provided.
audit_plugin_zip ~117
Audit a WordPress plugin from a local ZIP file. Provide the absolute or relative path to the .zip file. Submits to the job queue and polls until complete (up to 20 minutes). Returns the full audit summary.
| Name | Type | Req | Description |
|---|---|---|---|
| engines | array | – | Optional extra engines. ['performance'] adds server load, caching, and asset loading analysis (+1 token). |
| file_path | string | yes | Absolute or relative path to the plugin .zip file (e.g. './my-plugin.zip' or '/Users/me/plugins/my-plugin.zip') |
No output schema declared.
No examples provided.
audit_plugins_bulk ~112
Audit all plugin ZIP files in a local directory. Submits in batches of 10 via the job queue, streams results as each audit completes, and prints a summary table. Useful for auditing an entire plugin suite at once.
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | yes | Absolute path to a folder containing plugin .zip files |
| engines | array | – | Optional extra engines. ['performance'] adds performance analysis (+1 token per plugin). |
| pattern | string | – | Extension filter in the form *.ext (default: '*.zip') |
No output schema declared.
No examples provided.
check_plugin ~42
Look up a plugin's latest security grade, risk level, and findings count from the WP HealthKit directory.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The wp.org plugin slug |
No output schema declared.
No examples provided.
flag_finding ~105
Flag a specific finding in an audit as a false positive. The report goes to the WP HealthKit team for review — confirmed patterns result in a scanner rule update preventing this finding in future audits.
| Name | Type | Req | Description |
|---|---|---|---|
| auditId | string | yes | The audit UUID |
| findingId | string | yes | The finding ID (e.g. 'finding-12') |
| findingTitle | string | yes | The title of the finding |
| reason | string | – | Why this finding is a false positive |
No output schema declared.
No examples provided.
generate_sbom ~76
Generate a CycloneDX or SPDX Software Bill of Materials (SBOM) for a completed audit. Required for EU Cyber Resilience Act (CRA) compliance. Returns the SBOM JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| auditId | string | yes | UUID of the completed audit |
| format | string | – | SBOM format (default: cyclonedx) |
No output schema declared.
No examples provided.
get_findings ~87
Get paginated findings from an audit, optionally filtered by severity or category.
| Name | Type | Req | Description |
|---|---|---|---|
| auditId | string | yes | The audit UUID |
| category | string | – | Filter by finding category |
| limit | number | – | Max results (default 50) |
| offset | number | – | Pagination offset |
| severity | string | – | Filter: CRITICAL, HIGH, MEDIUM, or LOW |
No output schema declared.
No examples provided.
get_fix_plan ~106
Get the full Fix Plan for an audit — every finding with impact, remediation guidance, test steps, confidence, and agent-safety flags. Premium-tier audits may include refactorPlan: systemic refactor plans that eliminate a whole class of bug in one coordinated change (do those first). JSON (default) or Markdown.
| Name | Type | Req | Description |
|---|---|---|---|
| auditId | string | yes | The audit UUID |
| format | string | – | Output format: 'json' (default) or 'md' for Markdown |
No output schema declared.
No examples provided.
get_fix_prompt ~36
Get AI-ready fix prompts for an audit's findings, batched by severity.
| Name | Type | Req | Description |
|---|---|---|---|
| auditId | string | yes | The audit UUID |
No output schema declared.
No examples provided.
get_job_status ~63
Check the status of a queued or in-progress audit job. Returns status (queued/processing/complete/failed), queue position, progress, and the audit result when complete.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | The job UUID returned by audit_plugin or audit_plugin_zip |
No output schema declared.
No examples provided.
get_report ~45
Get the status and results of a completed audit by its audit ID. Use get_job_status to check a job's progress instead.
| Name | Type | Req | Description |
|---|---|---|---|
| auditId | string | yes | The audit UUID |
No output schema declared.
No examples provided.
get_telemetry_stats ~96
Get aggregated telemetry statistics for a plugin — active installs, version distribution, WP/PHP version breakdown, locale spread, error rates, and daily trend. Requires that your API key is scoped to the plugin or you have a verified plugin claim.
| Name | Type | Req | Description |
|---|---|---|---|
| period | string | – | Stats period (default: 30d) |
| slug | string | yes | The WordPress plugin slug (e.g. 'my-plugin', 'woocommerce') |
No output schema declared.
No examples provided.
list_usage ~23
Check your current usage — audits used this month, tier, and limits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the WP HealthKit MCP server?
WP HealthKit is an MCP server listed in the public MCP registry as com.wphealthkit/mcp-server. Security audits for WordPress plugins and themes, 62 verification layers, fix plans and SBOMs. This page covers its npm package (@wphealthkit/mcp-server).
Is the WP HealthKit MCP server safe to use?
WP HealthKit scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 30 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the WP HealthKit MCP server expose?
WP HealthKit exposes 13 tools: audit_plugin, audit_plugin_zip, audit_plugins_bulk, get_job_status, get_report, and 8 more. Their descriptions and schemas cost roughly 1,011 tokens of context every time the server is loaded.
Is the WP HealthKit MCP server still maintained?
WP HealthKit is still listed as active in the MCP registry. We last reached this channel on 30 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the WP HealthKit MCP server under?
WP HealthKit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.