Autowp MCP Server

autowp-mcp npm v1.1.0

Published by reblochi — 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.

Serveur MCP pour automatiser WordPress et le suivi SEO - Usage interne Intformalities

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/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
Moderate
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 = 96/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 − 4 = 96. 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
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−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 80

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

  • get-page-analyticsingests untrusted input
  • analyze-salienceno sensitive capability
  • assign-categories-to-postsno sensitive capability
  • assign-tags-to-postsno sensitive capability
  • authenticate-wpno sensitive capability
  • bulk-delete-mediano sensitive capability
  • bulk-request-indexingno sensitive capability
  • bulk-seo-checkno sensitive capability
  • bulk-update-postsno sensitive capability
  • check-indexing-statusno sensitive capability
Show 70 more tools ↓
  • check-url-trackingno sensitive capability
  • clone-postno sensitive capability
  • compare-channelsno sensitive capability
  • compare-periodsno sensitive capability
  • compare-salienceno sensitive capability
  • create-blog-postno sensitive capability
  • create-categoryno sensitive capability
  • create-tagno sensitive capability
  • create-tracking-sheetno sensitive capability
  • create-userno sensitive capability
  • delete-categoryno sensitive capability
  • delete-mediano sensitive capability
  • delete-postno sensitive capability
  • delete-tagno sensitive capability
  • disable-userno sensitive capability
  • edit-media-metadatano sensitive capability
  • format-wp-contentno sensitive capability
  • ga4-compare-periodsno sensitive capability
  • ga4-reportno sensitive capability
  • get-media-detailsno sensitive capability
  • get-pending-checksno sensitive capability
  • get-postno sensitive capability
  • get-post-seono sensitive capability
  • get-section-performanceno sensitive capability
  • get-site-analyticsno sensitive capability
  • get-site-performanceno sensitive capability
  • get-tracking-reportno sensitive capability
  • get-url-performanceno sensitive capability
  • get-url-queriesno sensitive capability
  • get-wp-categoriesno sensitive capability
  • get-wp-tagsno sensitive capability
  • inspect-urlno sensitive capability
  • inspect-url-fullno sensitive capability
  • list-ga4-propertiesno sensitive capability
  • list-mediano sensitive capability
  • list-postsno sensitive capability
  • list-taxonomiesno sensitive capability
  • list-user-rolesno sensitive capability
  • list-usersno sensitive capability
  • load-draftno sensitive capability
  • merge-categoriesno sensitive capability
  • optimize-mediano sensitive capability
  • query-search-analyticsno sensitive capability
  • request-indexingno sensitive capability
  • reset-user-passwordno sensitive capability
  • restore-postno sensitive capability
  • run-all-pending-checksno sensitive capability
  • run-performance-checkno sensitive capability
  • save-draftno sensitive capability
  • schedule-postno sensitive capability
  • search-mediano sensitive capability
  • search-postsno sensitive capability
  • set-featured-imageno sensitive capability
  • set-user-roleno sensitive capability
  • setup-googleno sensitive capability
  • setup-tracking-sheetno sensitive capability
  • sitemap-health-reportno sensitive capability
  • striking-distanceno sensitive capability
  • test-google-connectionno sensitive capability
  • test-wp-connectionno sensitive capability
  • top-moversno sensitive capability
  • track-post-updateno sensitive capability
  • track-urlno sensitive capability
  • trash-postno sensitive capability
  • update-categoryno sensitive capability
  • update-postno sensitive capability
  • update-post-seono sensitive capability
  • update-tagno sensitive capability
  • update-userno sensitive capability
  • upload-mediano 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.1.0 latest A 96/100 0 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.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/autowp-mcp/badge.svg)](https://mcptrustchecker.com/registry/autowp-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/autowp-mcp"><img src="https://mcptrustchecker.com/registry/autowp-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/autowp-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 autowp-mcp --online

Use the free API → How scoring works

More in Productivity & Workflow