Loading the registry…
MCP server for WP HealthKit — audit WordPress plugins and access developer reference guides from any AI tool
The publisher performed an authenticated act of publication — proving control of a namespace in the official MCP registry, or appearing in a first-party catalogue an operator curates. That establishes WHO published it. It is not a security finding, and attested artifacts carry Flagged verdicts too.
2 critical findings reported by agent-audit-kit. The composite score alone does not reflect this — read the per-scanner reports below.
github: https://github.com/BuiltByGo/wphealthkit-mcp, 30 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- @wphealthkit/mcp-server
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
5 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v1.4.0
0 findings · 0.7s
v2.0.11
12 findings · 7.7s
v0.3.26
6 findings · 1.0s
v0.1.0
5 findings · 28.1s
v0.1.0
0 findings · 28.1s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image, nerlo-multi-source.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 10, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicable | rejected |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 23 findings across every scanner that examined this package. None of the 2 findings rated critical by their scanner were dismissed.
These findings are in files this artifact installs and are not placeholder values. No false-positive basis can be corroborated for such a finding, so this review never dismisses one; they were not sent to the model and stand at their scanner's severity.
5 DATA_EXFIL_JS_NETWORK
Files: /repo/src/index.ts · reported by cisco-skill-scanner
5 opt.nerlo-rules.nerlo-js-secret-to-network-egress
Files: /repo/src/index.ts · reported by nerlo-behavioral
2 DATA_EXFIL_JS_FS_ACCESS
Files: /repo/src/index.ts · reported by cisco-skill-scanner
2 HIDDEN_DATA_FILE
Files: /repo/.memory/cursor.json, /repo/.memory/state.json · reported by cisco-skill-scanner
1 AAK-ANTHROPIC-SDK-001
Files: src/index.ts · reported by agent-audit-kit
1 AAK-DNS-REBIND-002
Files: package.json · reported by agent-audit-kit
1 AAK-MCP-MARKETPLACE-CONFIG-FETCH-001
Files: src/index.ts · reported by agent-audit-kit
1 AAK-MCP-STDIO-CMD-INJ-002
Files: src/index.ts · reported by agent-audit-kit
1 AAK-OAUTH-3P-001
Files: package.json · reported by agent-audit-kit
1 AAK-SEC-MD-001
Files: SECURITY.md · reported by agent-audit-kit
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
1 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · reported by cisco-skill-scanner
Critical risks: shell execution, network egress, and credential exposure.
The artifact exhibits critical command injection capabilities via standard I/O in `src/index.ts`, allowing for shell execution. It also has multiple instances of high-severity network egress of secrets from `src/index.ts`. Further, the artifact can fetch marketplace configuration and has potential for DNS rebinding, which could lead to credential access or internal network exposure.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.