Localwp MCP Server
localwp-mcp
npm
v0.1.11
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
A LocalWP-aware MCP server for WordPress developers with simple safe and full-access profiles, logs, doctor diagnostics, SQL access, backups, restore flows, MCP resources/prompts, and site-aware WP-CLI.
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 − 8 = 92. 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:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
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 5
high Sensitive-source and external-sink co-existMTC-FLOW-004
Tools that read sensitive data ([db_import, mysql_execute, mysql_query]) and tools that can send data out ([execute_wp_cli]) are exposed together. An agent can move private data to the sink.
Evidence: sources [db_import, mysql_execute, mysql_query] → sinks [execute_wp_cli]
Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.
Location: flow db_import → execute_wp_cli
high Tool "execute_wp_cli" exposes command/code executionMTC-CAP-001
Tool "execute_wp_cli" appears to run shell commands or evaluate code (parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool execute_wp_cli
high Shell/command execution in server code (dist/process-utils.js)MTC-SRC-002
In the server's implementation (`dist/process-utils.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import { spawn } from "child_process"; import { constants as fsConstants, createReadStream } from "fs"; import { access
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/process-utils.js
medium Unconstrained command parameter "command" on "execute_wp_cli"MTC-CAP-006
Tool "execute_wp_cli" takes a command-shaped parameter "command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.
Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.
Location: tool execute_wp_cli · inputSchema.properties.command
low Mutating tool "execute_wp_cli" declares no destructiveHintMTC-CAP-005
Tool "execute_wp_cli" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool execute_wp_cli
Tools 29
Each tool and what it can reach — statically extracted from the published source.
db_importreads sensitive dataexecute_wp_cliruns code / shellmysql_executereads sensitive datamysql_queryreads sensitive databackup_siteno sensitive capabilitycleanup_backupsno sensitive capabilitydb_exportno sensitive capabilitydelete_backupno sensitive capabilitydelete_site_fileno sensitive capabilityexecute_wp_phpno sensitive capability
Show 19 more tools ↓
execute_wp_php_readonlyno sensitive capabilitylist_backupsno sensitive capabilitylist_local_sitesno sensitive capabilitylist_site_filesno sensitive capabilitylocal_doctorno sensitive capabilitylocal_environment_checkno sensitive capabilitylocal_logsno sensitive capabilitylocal_site_infono sensitive capabilitymysql_schemano sensitive capabilitypreview_restore_backupno sensitive capabilityread_site_fileno sensitive capabilityrestart_local_siteno sensitive capabilityrestore_backupno sensitive capabilitysearch_site_filesno sensitive capabilitystart_local_siteno sensitive capabilitystop_local_siteno sensitive capabilitywp_call_functionno sensitive capabilitywp_call_static_methodno sensitive capabilitywrite_site_fileno sensitive capability
Toxic flows 1
Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
What this scan could not see
- Tools were statically extracted from the published source (29 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.11 latest |
A 92/100 | 5 | 1.13.0 | 2026-09-08 |
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.
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 localwp-mcp --onlineMore in Developer Tools
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.