
Site Doctor — WordPress diagnosis
pro.syswp.sitedoctorPublished by sitedoctor.syswp.proOfficial publisherv1.0.0Updated Nov 4, 2026
Read-only WordPress diagnosis for AI: security, performance, forms and downtime, with evidence.
Overview
Site Doctor — WordPress diagnosis's hosted MCP server (sitedoctor.syswp.pro), published by sitedoctor.syswp.pro; OAuth sign-in required; Streamable HTTP.
No AI overview yet: these facts come from the registry entry and the server itself.
- Publisher
- sitedoctor.syswp.pro
- Endpoint
- sitedoctor.syswp.pro
- Last checked
Installation
In SourceWeft
- Open Site Doctor — WordPress diagnosis in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/pro.syswp.sitedoctor%2Fdiagnosis/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"site-doctor-wordpress-diagnosis": {
"type": "http",
"url": "https://sitedoctor.syswp.pro/mcp"
}
}
}README
Site 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
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]
Source: README.md at commit 1b091d1
Tools
0Version history
1- v1.0.0LatestNov 4, 2026
Score
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.
