Ploi MCP Server

ploi-mcp npm v0.2.0

Published by sudanese — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for Ploi.io API - manage servers, sites, and databases with Claude

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 99/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 46

Each tool and what it can reach — statically extracted from the published source.

  • create_cronno sensitive capability
  • create_daemonno sensitive capability
  • create_databaseno sensitive capability
  • create_database_backupno sensitive capability
  • create_queueno sensitive capability
  • create_siteno sensitive capability
  • delete_certificateno sensitive capability
  • delete_cronno sensitive capability
  • delete_daemonno sensitive capability
  • delete_databaseno sensitive capability
Show 36 more tools ↓
  • delete_database_backupno sensitive capability
  • delete_queueno sensitive capability
  • delete_siteno sensitive capability
  • deploy_projectno sensitive capability
  • deploy_siteno sensitive capability
  • find_site_by_domainno sensitive capability
  • get_database_backupno sensitive capability
  • get_deploy_scriptno sensitive capability
  • get_project_deploy_statusno sensitive capability
  • get_queueno sensitive capability
  • get_serverno sensitive capability
  • get_server_logsno sensitive capability
  • get_siteno sensitive capability
  • get_site_envno sensitive capability
  • get_site_logsno sensitive capability
  • init_projectno sensitive capability
  • list_certificatesno sensitive capability
  • list_cronsno sensitive capability
  • list_daemonsno sensitive capability
  • list_database_backupsno sensitive capability
  • list_databasesno sensitive capability
  • list_queuesno sensitive capability
  • list_serversno sensitive capability
  • list_sitesno sensitive capability
  • request_certificateno sensitive capability
  • restart_daemonno sensitive capability
  • restart_queueno sensitive capability
  • restart_serverno sensitive capability
  • restart_serviceno sensitive capability
  • resume_siteno sensitive capability
  • run_database_backupno sensitive capability
  • suspend_siteno sensitive capability
  • toggle_daemonno sensitive capability
  • toggle_queueno sensitive capability
  • update_deploy_scriptno sensitive capability
  • update_site_envno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.2.0 latest A 99/100 0 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/ploi-mcp/badge.svg)](https://mcptrustchecker.com/registry/ploi-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/ploi-mcp"><img src="https://mcptrustchecker.com/registry/ploi-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/ploi-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan ploi-mcp --online

Use the free API → How scoring works

More in Cloud & DevOps