MCP Connection Diagnostic

Claude won't connect to your WordPress site? Most failures happen at the hosting, CDN, cache, or security layer — not in the plugin. This check reproduces what Claude's backend does and tells you exactly which layer is blocking it.

We probe only public discovery endpoints from our server. Nothing is stored. ~10 seconds.

What this diagnostic checks

Reachability & DNS

Confirms your site resolves on the public internet — local-only installs (.test, .local, LocalWP) can't be reached by Claude.

Plugin & MCP endpoint

Verifies easymcpai is active and that /wp-json/easy-mcp-ai/v1/mcp answers with the expected OAuth challenge.

OAuth discovery

Tests both /.well-known/ URL shapes to catch hosts (SiteGround & co.) that block the well-known prefix before WordPress runs.

WAF & environment

Detects WP Engine's User-Agent block, plus caching/security plugins and CDNs that commonly interfere with the OAuth flow.