Back to MCP Trust Indexm8ven
C
Caution
74/100
11 days ago

wp-mcp

AI-powered bridge between WordPress and MCP (Model Context Protocol). Write, publish, and manage WordPress posts directly from your AI assistant — TypeScript, Node.js, and pure MCP.

→ rnaga/wp-mcp· listed on github_code

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

rnaga

Source: github_code · also listed on Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

GitHubGlama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 1 credential: DB_PASSWORD
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configCONFIG_SQLITE_DB_PATH
configDB_HOST
configDB_NAME
🔐 secretDB_PASSWORD
configDB_PORT
configDB_USER
configDEFAULT_BLOG_ID
configDEFAULT_SITE_ID
configLOCAL_CONFIGfile <path> / -f <path> WordPress config manifest location Used by local start to point the init hook at a custom WP config JSON.
configLOCAL_USERNAME"": "wp-admin"
configLOG_LEVEL
configMULTISITE
configREMOTE_AUTH_TYPE"": "oauth",
configREMOTE_URL"": "https://wp-mcp.example.com/mcp"
configWP_MCP_ENV_BASE_PATH
configWP_MCP_SECRET_DB_PATH
configWP_MCP_SECRET_ENV_FILE
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

1/1 tools missing one or more hints — echo (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool handlers catch errors

Only 0/1 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Dependency freshness

3/13 production deps abandoned (no release in 2+ years): enquirer@2023-07-28 (3y), node-fetch@2023-11-30 (2.7y), reflect-metadata@2024-03-29 (2.4y)

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/rnaga-wp-mcp-1pflzu?variant=verified)](https://m8ven.ai/mcp/rnaga-wp-mcp-1pflzu)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 4953e049fce9dceedb6acda739f4c6c2551c5405
code hash: 603b22b3b737a4e189fa447d91a4b2de2150fc67211326f3cd7b79bf003511a8
verified: 8/8/2026, 7:15:09 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client