Mainwp (cvsloane) MCP Server

mainwp-mcp npm v1.0.0

Published by cvsloane — 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 MainWP Dashboard WordPress site management

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 43

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

  • mainwp_clients_addno sensitive capability
  • mainwp_clients_deleteno sensitive capability
  • mainwp_clients_editno sensitive capability
  • mainwp_clients_getno sensitive capability
  • mainwp_clients_listno sensitive capability
  • mainwp_costs_addno sensitive capability
  • mainwp_costs_deleteno sensitive capability
  • mainwp_costs_editno sensitive capability
  • mainwp_costs_getno sensitive capability
  • mainwp_costs_listno sensitive capability
Show 33 more tools ↓
  • mainwp_plugins_activateno sensitive capability
  • mainwp_plugins_deactivateno sensitive capability
  • mainwp_plugins_deleteno sensitive capability
  • mainwp_plugins_installno sensitive capability
  • mainwp_plugins_listno sensitive capability
  • mainwp_sites_addno sensitive capability
  • mainwp_sites_changesno sensitive capability
  • mainwp_sites_checkno sensitive capability
  • mainwp_sites_countno sensitive capability
  • mainwp_sites_disconnectno sensitive capability
  • mainwp_sites_editno sensitive capability
  • mainwp_sites_getno sensitive capability
  • mainwp_sites_listno sensitive capability
  • mainwp_sites_reconnectno sensitive capability
  • mainwp_sites_removeno sensitive capability
  • mainwp_sites_suspendno sensitive capability
  • mainwp_sites_syncno sensitive capability
  • mainwp_sites_unsuspendno sensitive capability
  • mainwp_tags_listno sensitive capability
  • mainwp_tags_sitesno sensitive capability
  • mainwp_themes_activateno sensitive capability
  • mainwp_themes_deleteno sensitive capability
  • mainwp_themes_installno sensitive capability
  • mainwp_themes_listno sensitive capability
  • mainwp_updates_applyno sensitive capability
  • mainwp_updates_ignoreno sensitive capability
  • mainwp_updates_ignoredno sensitive capability
  • mainwp_updates_listno sensitive capability
  • mainwp_updates_pluginsno sensitive capability
  • mainwp_updates_themesno sensitive capability
  • mainwp_updates_translationsno sensitive capability
  • mainwp_updates_unignoreno sensitive capability
  • mainwp_updates_wpno 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
v1.0.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/mainwp-mcp-2/badge.svg)](https://mcptrustchecker.com/registry/mainwp-mcp-2)
HTML
<a href="https://mcptrustchecker.com/registry/mainwp-mcp-2"><img src="https://mcptrustchecker.com/registry/mainwp-mcp-2/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mainwp-mcp-2/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 mainwp-mcp --online

Use the free API → How scoring works

Other implementations of Mainwp 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Business & CRM