← Case index
Case file No.470 · pypi · stdio
io.github.FlayedOne/plesk-mcp
io.github.FlayedOne/plesk-mcp · v0.1.1
Manage your Plesk hosting server using AI assistants.
Security score
86/100
Strong
Normalized over 100 points of available evidence.
Score breakdown
Known advisories
source: OSV.devNo advisories found in OSV for this package name. (Not proof of safety.)
Metadata change timeline
rug-pull detection- First snapshot (v0.1.1)Oct 16, 2026
No changes observed yet across 1 snapshot(s).
Tool lists: not published by the registry — unknown.
FAQ
auto-generated from the data aboveIs io.github.FlayedOne/plesk-mcp safe?
MCPWatch gives io.github.FlayedOne/plesk-mcp a heuristic security score of 86/100 (strong), based on 100 points of available evidence. This is an automated heuristic, not an audit.
Does io.github.FlayedOne/plesk-mcp have known CVEs or vulnerabilities?
No advisories were found in OSV.dev for the pypi package plesk-mcp. That is not proof of safety.
When was io.github.FlayedOne/plesk-mcp last updated?
The latest registry version is 0.1.1, published May 4, 2026. The last push to FlayedOne/plesk-mcp was on May 17, 2026. MCPWatch last checked it on Oct 20, 2026.
What license does io.github.FlayedOne/plesk-mcp use?
GitHub reports the license of FlayedOne/plesk-mcp as MIT.