Site Doctor — WordPress diagnosis
RemoteAbout Site Doctor — WordPress diagnosis
Site Doctor is a read-only WordPress diagnosis service for site maintainers, letting AI inspect security, performance, forms, logs, and downtime with evidence. A one-file connector reads site data and redacts credentials and sensitive details before model output.
Key features
- 01Diagnose security, performance, and downtime
- 02Inspect forms, leads, and scheduled tasks
- 03Return evidence-backed findings
- 04Monitor externally and send alerts
- 05Redact credentials and sensitive data
Use cases
- 01Find the cause of a WordPress outage
- 02Assess whether a file contains an injection
- 03Investigate slow pages or faulty forms
- 04Track changes and issues across client sites
MCP support
The MCP server uses OAuth 2.1 / PKCE to let AI clients access WordPress diagnostic evidence gathered through the connector. The connector has no write operations, and credentials are redacted before data reaches a model.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://sitedoctor.syswp.pro/mcpclaude mcp add --transport http pro-syswp-sitedoctor-diagnosis https://sitedoctor.syswp.pro/mcp{"mcpServers":{"pro-syswp-sitedoctor-diagnosis":{"type":"http","url":"https://sitedoctor.syswp.pro/mcp"}}}Open in Cursor{"servers":{"pro-syswp-sitedoctor-diagnosis":{"type":"http","url":"https://sitedoctor.syswp.pro/mcp"}}}Open in VS Code{"mcpServers":{"pro-syswp-sitedoctor-diagnosis":{"type":"http","url":"https://sitedoctor.syswp.pro/mcp"}}}{"mcpServers":{"pro-syswp-sitedoctor-diagnosis":{"serverUrl":"https://sitedoctor.syswp.pro/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMESite Doctor — read-only WordPress diagnosis for your AI
Connect your own AI (Claude, ChatGPT, Cursor, Codex…) to any WordPress site through a 100% read-only MCP connector and ask what's wrong — security, performance, forms, logs, downtime — with evidence. The connector never writes to the site, and your AI never sees the site's credentials.
Website: https://sitedoctor.syswp.pro · Docs: https://sitedoctor.syswp.pro/docs
What it is
Site Doctor is the neutral, read-only diagnosis layer for WordPress. Ask your AI why a site is broken and get the root cause with evidence — without giving any AI permission to write to the site. Built for agencies and freelancers maintaining 5–100 client WordPress sites.
Three parts:
- SaaS dashboard — six monitors, alerts, findings and a durable intervention timeline per site.
- One-file WordPress connector — read-only, HMAC-signed.
- MCP server (OAuth 2.1) — so your own AI can reach it.
Connect your AI to WordPress (MCP)
- Create a free account at https://sitedoctor.syswp.pro and add a site.
- Install the one-file read-only connector plugin (upload it, paste the connection key from the panel). It exposes no write operations.
- Add Site Doctor as an MCP server in your AI client using OAuth 2.1 / PKCE. Tested with Claude, Claude Code, ChatGPT, Codex, Cursor, Trae and VS Code — or use the built-in "Doc" chat in the dashboard.
- Ask about any site you manage in plain language. The AI reads only the evidence needed to answer; secrets are redacted before anything reaches the model.
Why read-only (the trust model)
- The connector exposes no write operations — it physically cannot modify, clean or break a site.
- Your AI never receives credentials — wp-config constants (DB password, salts), password hashes and the connector's own key are redacted before any output reaches a model.
- Every request is HMAC-SHA256 signed with a nonce and ±5-minute skew; SQL is read-only; the MCP uses OAuth 2.1 (PKCE); tenants are isolated per organization.
- On the Agency plan and above, a fix is prepared as a one-click activatable mu-plugin — a logged-in admin turns it on from wp-admin. Never a silent write.
What it diagnoses (read-only, on real client sites)
- Security & compromise — skimmers, backdoors, tampered core, ghost admins; the cleanup prepared.
- False-positive triage — tells a real injection from a harmless file.
- Performance — real coverage, render-blocking scripts, the cause of slow loads.
- Downtime — root cause found from outside the site, because the uptime check and auto-investigation run externally.
- Cron / scheduled posts, lost ad attribution, forms & leads, change tracking, and managed-host blind spots (WP Engine / Pantheon / Kinsta, where you usually can't read debug.log).
- Offline CVE matching against a mirror of the Wordfence vulnerability database.
Pricing
| Plan | Price | Sites |
|---|---|---|
| Free | $0 | 1 |
| Personal | $9/mo | 3 |
| Solo | $19/mo | 10 |
| Agency | $79/mo | 50 · one-click activatable fixes |
| Fleet | $119/mo | 100 |
Self-serve at https://sitedoctor.syswp.pro/#precios
Links
- Home: https://sitedoctor.syswp.pro
- Docs: https://sitedoctor.syswp.pro/docs
- Use-case library: https://sitedoctor.syswp.pro/casos
- Free outside-in scan (no account): https://sitedoctor.syswp.pro/scan
Built by SysWP. Questions and trials: [email protected]
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.