@adi.lib/wp-mcp
npm
v0.0.4
Published by @adi.lib — 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.
WordPress MCP Server - Connect WordPress to AI agents via Model Context Protocol
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:
| Points | Adoption-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.
Untrusted-input tools ([get_pages, get_page, get_page_by_slug, get_page_children]) co-exist with external-action tools ([create_comment]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [get_pages, get_page, get_page_by_slug, get_page_children] → sinks [create_comment]
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow get_pages → create_comment
Each tool and what it can reach — statically extracted from the published source.
create_commentnetwork egressget_pageingests untrusted inputget_page_by_slugingests untrusted inputget_page_childreningests untrusted inputget_pagesingests untrusted inputcreate_application_passwordno sensitive capabilitycreate_categoryno sensitive capabilitycreate_pageno sensitive capabilitycreate_postno sensitive capabilitycreate_tagno sensitive capabilitycreate_userno sensitive capabilitydelete_application_passwordno sensitive capabilitydelete_categoryno sensitive capabilitydelete_commentno sensitive capabilitydelete_mediano sensitive capabilitydelete_pageno sensitive capabilitydelete_postno sensitive capabilitydelete_tagno sensitive capabilitydelete_userno sensitive capabilityget_application_passwordsno sensitive capabilityget_block_typeno sensitive capabilityget_block_typesno sensitive capabilityget_categoriesno sensitive capabilityget_categoryno sensitive capabilityget_commentno sensitive capabilityget_commentsno sensitive capabilityget_comments_by_postno sensitive capabilityget_current_userno sensitive capabilityget_mediano sensitive capabilityget_media_by_postno sensitive capabilityget_media_itemno sensitive capabilityget_postno sensitive capabilityget_post_by_slugno sensitive capabilityget_post_revisionsno sensitive capabilityget_post_statusno sensitive capabilityget_post_statusesno sensitive capabilityget_post_typeno sensitive capabilityget_post_typesno sensitive capabilityget_postsno sensitive capabilityget_settingsno sensitive capabilityget_tagno sensitive capabilityget_tagsno sensitive capabilityget_taxonomiesno sensitive capabilityget_taxonomyno sensitive capabilityget_userno sensitive capabilityget_usersno sensitive capabilitysearch_wordpressno sensitive capabilityupdate_categoryno sensitive capabilityupdate_commentno sensitive capabilityupdate_mediano sensitive capabilityupdate_pageno sensitive capabilityupdate_postno sensitive capabilityupdate_settingsno sensitive capabilityupdate_tagno sensitive capabilityupdate_userno sensitive capabilityupload_mediano sensitive capabilityCross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
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.0.4 latest |
A 96/100 | 1 | 1.13.0 | 2026-09-07 |
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.
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 @adi.lib/wp-mcp --online
Independent packages implementing the same tool, scanned with the same engine. Compare all 7 side by side →
The WordPress MCP server enables AI assistants to interact with WordPress sites through a standardized interface. It handles authentication and provides a secure way to discover and interact with WordPress REST API endpoints.
Wordpress MCP Server
A Model Context Protocol server for interacting with WordPress.
Universal installer for SEOMI MCP Abilities — wires WordPress projects to AI agents in one command (mu-plugin, MCP servers, Abilities API, MCP Adapter, ai-factory skill).
WordPress Model Context Protocol (MCP) implementation
Security scan results for the Wp (npm) MCP server.
Adapters for the FrontMCP framework
Transcend MCP Server — Admin tools.
Transcend MCP Server — Assessments tools.
MCP Server for Bling
MCP Server for Blogger API
Official MCP server for Brilliant Directories — manage members, posts, leads, reviews, and more.