MCP WordPress Server (stuffyoushouldautomate/mcp-wordpress-datapilot) is an MCP server listed on the M8ven Trust Index. It scores 48 out of 100, grade D. It declares 24 tools. No publisher has claimed this listing.

D
Caution
48/100

MCP WordPress Server

Comprehensive MCP server to manage WordPress sites via natural language, enabling content creation, SEO, and multi-site administration through AI tools like Claude Desktop.

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

stuffyoushouldautomate

Source: 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 →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
5 flows detected: WORDPRESS_APP_PASSWORD. We can’t prove the destination matches the brand the credential belongs to.
🚨
Known vulnerabilities in dependencies: 1 critical, 4 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 5 credentials: WORDPRESS_API_KEY, WORDPRESS_APP_PASSWORD, WORDPRESS_JWT_PASSWORD, WORDPRESS_JWT_SECRET, WORDPRESS_PASSWORD
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes24 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

bulk_operations
wp_seo_analyze_content
wp_seo_generate_metadata
wp_seo_bulk_update_metadata
wp_seo_generate_schema
wp_seo_validate_schema
wp_seo_suggest_internal_links
wp_seo_site_audit
wp_seo_track_serp
wp_seo_keyword_research
wp_seo_test_integration
wp_seo_get_live_data
seo
wp_seo_generate_meta
wp_seo_bulk_update
wp_seo_internal_linking
content_analyzer
seo_analyze_content
site_auditor
meta_generator
seo_generate_metadata
schema_generator
internal_linking
seo_client
// known CVEs in dependencies1 critical4 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@3.2.4GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

high@modelcontextprotocol/sdk@1.17.4GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.17.4GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.17.4GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

highform-data@4.0.4GHSA-hmw2-7cc7-3qxx

form-data: CRLF injection in form-data via unescaped multipart field names and filenames

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
configBUILD_NUMBER
configCACHE_DISABLED
configCACHE_MAX_ITEMS
configCACHE_MAX_MEMORY_MB
configCACHE_TTL
configCOVERAGE_TOLERANCE
configDISABLE_CACHE
configGITHUB_ACTIONS
configGIT_COMMIT
configLEGACY_ERROR_LOGS
configLOG_LEVEL
configPERFORMANCE_TEST
configRATE_LIMIT
configRATE_LIMIT_ENABLED
configRATE_LIMIT_REQUESTS
configRATE_LIMIT_WINDOW
configSECURITY_STRICT_MODE
configSEO_BULK_OPERATION_SIZE
configSEO_CACHE_ANALYSIS_TTL
configSEO_CACHE_AUDIT_TTL
configSEO_CACHE_KEYWORDS_TTL
configSEO_CACHE_SCHEMA_TTL
configSEO_DESCRIPTION_MAX_LENGTH
configSEO_DESCRIPTION_MIN_LENGTH
configSEO_ENABLED
configSEO_MAX_CONCURRENT_ANALYSIS
configSEO_MAX_KEYWORD_DENSITY
configSEO_MIN_READABILITY_SCORE
configSEO_MIN_WORD_COUNT
configSEO_PROVIDER_AHREFS
configSEO_PROVIDER_DATAFORSEO
configSEO_PROVIDER_SEARCH_CONSOLE
configSEO_RATE_LIMIT_PER_MINUTE
configSEO_TARGET_KEYWORD_DENSITY
configSEO_TITLE_MAX_LENGTH
configSKIP_PACT_TESTS
configTRAVIS
🔐 secretWORDPRESS_API_KEY
🔐 secretWORDPRESS_APP_PASSWORDxxxx xxxx xxxx xxxx xxxx xxxx
configWORDPRESS_AUTH_METHODapp-password
configWORDPRESS_COOKIE_NONCE
🔐 secretWORDPRESS_JWT_PASSWORD
🔐 secretWORDPRESS_JWT_SECRET
configWORDPRESS_MAX_RETRIES
🔐 secretWORDPRESS_PASSWORD"": "user-password",
configWORDPRESS_SITE_URL"": "https://myblog.com",
configWORDPRESS_TIMEOUT
configWORDPRESS_USERNAME"": "admin",
// 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

24/24 tools missing one or more hints — bulk_operations (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); wp_seo_analyze_content (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); wp_seo_generate_metadata (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +21 more. 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 test coverage

Only 5/24 tools referenced in tests (21%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

2 calls in production code run through a shell (bin/setup.js:153, bin/status.js:248)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Secrets not written to files

1 secret value written to files

Avoid persisting secrets to disk. Keep them in memory or your secret manager.

Secrets not logged

8 secret values sent to console.log

Redact or omit secret values from log output.

Production dependencies are patched

0 critical, 4 high severity in production deps — @modelcontextprotocol/sdk@1.17.4 (high), @modelcontextprotocol/sdk@1.17.4 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

1 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

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 8 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/stuffyoushouldautomate/mcp-wordpress-datapilot?variant=verified)](https://m8ven.ai/mcp/stuffyoushouldautomate/mcp-wordpress-datapilot)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 077b2a535b224c39af618c14eefd9185d9d3e714
code hash: 2bde787d0df60de96c5f991290a87cafad77bb47af04fd0d699fe280d722273b
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