/ 100

5 days ago

pulsemcp

WordPress Remote

Bridges WordPress websites and WooCommerce data with local clients through REST API calls, enabling content access without direct streaming connections.

→ automattic/mcp-wordpress-remote· npm: @automattic/mcp-wordpress-remote· 78K installs· listed on pulsemcp

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.

Install from

PulseMCP

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

// key findings

⚠️

Known vulnerabilities in dependencies: 4 high

Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.

✅

No credential exfiltration, no sensitive file access, no obfuscation

Static analysis found nothing flowing your secrets to unexpected places.

✅

Open source with a license and README

Anyone can audit the code, the license is declared, and the publisher documents what it does.

🔐

You'll be asked for 7 credentials: JWT_TOKEN, MCP_WP_APP_PASSWORD, MCP_WP_CLIENT_SECRET, WOO_CUSTOMER_KEY, WOO_CUSTOMER_SECRET, WP_API_PASSWORD, WP_OAUTH_CLIENT_SECRET

These are read from process.env at runtime. Make sure you trust where they’ll be sent.

// required environment variables

This server reads these from process.env. You'll be asked to provide them before it can run.

configALL_PROXY

configCUSTOM_HEADERS— You can add custom headers to all API requests using the environment variable. This is useful for API keys, custom authentication, or other header requirements.

configE2E_TEMP_DIR

configHTTPS_PROXY

configHTTP_PROXY

🔐 secretJWT_TOKEN— JWT Token: Set environment variable

configLOG_FILE— Log file path - -

configLOG_LEVEL— Log level (0-3) 2 -

configLOG_TO_STDERR

🔐 secretMCP_WP_APP_PASSWORD

configMCP_WP_CLIENT_ID

🔐 secretMCP_WP_CLIENT_SECRET

configMCP_WP_LOG_LEVEL

configMCP_WP_SITE_URL

configMCP_WP_USERNAME

configNO_PROXY

configOAUTH_AUTHENTICATE_ENDPOINT— OAuth authenticate endpoint - -

configOAUTH_AUTHORIZE_ENDPOINT— OAuth authorization endpoint - ✅ (for custom OAuth)

configOAUTH_CALLBACK_PORT— "": "7665",

configOAUTH_DYNAMIC_REGISTRATION— Enable dynamic client registration true -

configOAUTH_ENABLED— "": "true"

configOAUTH_FLOW_TYPE— OAuth flow type (authorization_code or implicit) authorization_code -

configOAUTH_HOST— "": "127.0.0.1",

configOAUTH_RESOURCE_INDICATOR— Use resource indicators (RFC 8707) true -

configOAUTH_SCOPES

configOAUTH_TOKEN_ENDPOINT— OAuth token endpoint - ✅ (for custom OAuth)

configOAUTH_USE_PKCE— Use PKCE (required for OAuth 2.1) true -

configSOCKS_PROXY

configUSE_SYSTEM_PROXY

🔐 secretWOO_CUSTOMER_KEY— "": "ck_your-consumer-key",

🔐 secretWOO_CUSTOMER_SECRET— "": "cs_your-consumer-secret"

🔐 secretWP_API_PASSWORD— Application Password: Set WP_API_USERNAME and

configWP_API_URL— "": "https://your-wordpress-site.com/wp-json/mcp/mcp-adapter-default-server"

configWP_API_USERNAME— Application Password: Set and WP_API_PASSWORD

configWP_MCP_CONFIG_DIR— Config directory override ~/.mcp-auth -

configWP_OAUTH_CLIENT_ID— "": "your-custom-client-id"

🔐 secretWP_OAUTH_CLIENT_SECRET

configall_proxy

confighttp_proxy

confighttps_proxy

configno_proxy

configsocks_proxy

// full audit trail

The full breakdown of what we checked, the deductions that landed, the network hosts, the dependency advisories, and concrete fix guidance is available to verified publishers.

// improvement guidance — verified publishers only

We have 2 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 Score](https://m8ven.ai/badge/mcp/automattic-mcp-wordpress-remote-ljebwi)](https://m8ven.ai/mcp/automattic-mcp-wordpress-remote-ljebwi)

commit: 03cf66238aa892b205037a6dd68d6c22c2f4b239

code hash: 43162791984d9d7cdcfa29c0d4ac6040afaddcd2168e5b0ca9ceb64e6bfca978

verified: 5/31/2026, 10:27:51 AM

view raw JSON →